Hi All; > 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.
Say for an instance we deploy a service in application scope, then the expected behavior is to have only one instance of the service impl class, but if we are going to new up a service impl whenever we get the ping req , then we are doing smt wrong. We are going to have multiple instance of the same service class even in application scope. For me that is not good idea. > 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. > > Paul > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
