Hi Paul; Cant we do the same thing as we are doing in ServiceLifeCycle interface in this case too. Let's introduce new interface to manage the service (ServiceManager) and ask service author to implement that the way he want (and ask to add entry to services.xml as an optional tag). So once we get the request we will check the AxisService whether it has impl of that ServiceManager interface if so we call that and send the response else ...... (need to decide) With this approach we are not going to touch the service impl class , and that help us to mange the service independent of the session scope.
Paul Fremantle wrote: > Bill > > Maybe I misunderstood the discussion, but I thought we had the > following approach in mind. > > 1) Implement a ping module. This does its best to let you know if the > service is up. > 2) Add a new interface (e.g. PingableMR) that MR's may implement. This > allows the ping module to ask the MR if the service is up. (better > than just the module's answer). For example the MR may try to new up > an instance of the Service class (if that is appropriate) to ensure > classloading is working. > 3) The MR that implements the PingableMR interface can see if the > service implements the PingableService interface. If this is the case > then the MR will call that method. This will allow the service itself > to test things (such as connections to databases, classloading, > whatever). This is the best test. > > Unless you deploy the Ping module then none of this is exposed. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
