> 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.
Seems like we are agreeing on having service classes implement the pingable interface.But in order to do that we need to add a (ping) method to the message receiver interface, since message receiver needs to have some method to check the service class (if the message receiver has a associated service class).. I'm +1 for having both of the above.. ~Thilina
> > 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]
-- Thilina Gunarathne WSO2, Inc.; http://www.wso2.com/ Home page: http://webservices.apache.org/~thilina/ Blog: http://thilinag.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
