It'd be
easy enough to do this as an interface, though. So the message receiver
could check if the service class implements the pingable interface, and
if so it calls the method defined by that interface. Otherwise, it just
checks that it can create an instance of the service class.
That seems like a reasonable approach - no impact on users who just use
the default behavior, but easy for anyone who wants to support the added
value to do so. Does anyone object to implementing it this way?
+1 from me. This will be really useful - we can improve the failover
that we do in Synapse to use this.
Paul
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
