Hi Dims, I don't see any possibility to implement what's mentioned in the following mail without changing the MR interface... Any clues??
http://marc.theaimsgroup.com/?l=axis-dev&m=117101637929286&w=2
Thanks, Thilina
thanks, dims On 2/9/07, Nicholas L Gallardo <[EMAIL PROTECTED]> wrote: > > I'm -1 on a change to the actual MessageReceiver interface. That would require that we implement these semantics for JAX-WS services that may not implement the Pingable interface. > > I would prefer this be an additional interface that the MessageReceiver impl could choose to implement, but is not required. > > That's just my opinion though. > > Regards, > > Nicholas Gallardo > WebSphere - WebServices Development > [EMAIL PROTECTED] > Phone: 512-838-1182 > Building: 901 / 5G-016 > > > > "Thilina Gunarathne" <[EMAIL PROTECTED]> > > 02/09/2007 07:16 AM > > Please respond to > axis-dev@ws.apache.org > > > To axis-dev@ws.apache.org > > cc > > > Subject Re: [axis2] Pinging capability to services deployed in Axs2 > > > > > > > > > > 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] > > > -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers --------------------------------------------------------------------- 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]
