[I'm a little late to the conversation but anyways...] I vote against extending the MessageReceiver interface -- unless you go to the service itself (i.e. actually invoke part of its logic,) you're going to end up with responses whose meanings you can't interpret (e.g. "This service said that it was up, but it's using the Axis2 programming model so that means ..., and this service said that it was up, but it's using the JAX-WS programming model so that means ..., and this service said that it was up, but I have no idea what it's using so....) If you want true service status, then implement that as part of your exposed interface.
On the other hand, I think that implementing 'ping' as a module that exposes a 'ping' operation is a fine idea; what you would get is a consistent answer -- whether or not the service is 'available' from the runtime's perspective. That's what the pinging a machine's network interface gives you -- the answer to whether or not the pinged interface is active. -Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
