Hi, I've been reading through the JMX spec, specifically the Inheritance Patterns section, relating to how compliant JMX agents determine the management interface of an MBean. The spec appears to say to me that if a class A implements an interface called AMBean then the interface AMBean constitutes the entire definition of methods in the MBeans management interface, methods in other interfaces perhaps implemented by superclasses of A are NOT in the management interface. Now I notice all over the jboss project MBeans often extend ServiceMBeanSupport, an abstract class that implements the ServiceMBean interface that extends the Service interface, together providing init, start, stop destroy etc. method signatures. An example of this is ClassPathExtension. However ClassPathExtension is declared to implement ClassPathExtensionMBean, which is empty, effectively blowing away all of the management interfaces in the hierarchy. Is this the intention? Doesn't this mean that other JMX agents are not going to see init, start, stop etc. cheers craig -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] List Help?: [EMAIL PROTECTED]
