axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicholas L Gallardo <>
Subject Re: [axis2] Pinging capability to services deployed in Axs2
Date Fri, 09 Feb 2007 15:47:58 GMT
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.


Nicholas Gallardo
WebSphere  -  WebServices Development
Phone: 512-838-1182
Building: 901 / 5G-016

"Thilina Gunarathne" <> 
02/09/2007 07:16 AM
Please respond to


Re: [axis2] Pinging capability to services deployed in Axs2

> > easy enough to do this as an interface, though. So the message 
> > could check if the service class implements the pingable interface, 
> > if so it calls the method defined by that interface. Otherwise, it 
> > 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..

> >
> > That seems like a reasonable approach - no impact on users who just 
> > the default behavior, but easy for anyone who wants to support the 
> > 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
> "Oxygenating the Web Service Platform",
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Thilina Gunarathne
WSO2, Inc.;
Home page:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message