Sameera, We've implemented ws-trust/ws-secconv/ws-rm w/o needing to extend the API. So please take it out of the equation.
thanks, dims On 2/7/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> Hi Dims, Deepal > > Actually the idea is to develop a custom ping module with appropriate > handlers. One of the ping handlers should be added to the dispatch > phase before the 'InstanceDispatcher' (Inflow). If the service is > deployed and it is active, then ping handler can get the service > status from AxisConfiguration. If the service is not deployed then the > service information is not available in the AxisConfiguration. Then > the ping module can respond to the ping requests accordingly. +1 > > well... this is the fundamental functionality of the ping module, > monitoring the availability of the services deployed in axis2. But > extending the MessageReceiver api with a ping method will enhance this > functionality. Managing a service (like sending a ping message) is generic requirement or a specific requirement, as I can see it is very specific requirement. So Im not that much like to change the MR api to cope with requirement. > Since the method is added to the AbstractMessageReceiver it will not > break the existing implementations of the MessageReceiver interface. > This ping method can be used to check real status of the services, > whether they are up and running. There may be instances, where the > services are available but they are not in a position to respond to > requests. So , how come that response to ping request if it is in such a position :) --------------------------------------------------------------------- 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]
