>FYI, this is not completely true. JBoss only looks to see if your Mbean >exports "create", "start", "stop", or "destroy" JBoss service lifecycle >methods via your mbean's MBeanInfo. Since you're using a standard mbean (as >opposed to a DynamicMBean or ModelMbean), the JMX server uses introspection >on your service interface to build the MBeanInfo descriptor. So, long story >short, you can just define any of the service lifecycle methods that you >want to be called in your MBean interface and it will work!
Tanx a lot for the information. I canged my class accordingly. And of wonder is works :) Now I still use two classes of Jboss: org.jboss.naming.NonSerializableFactory and org.jboss.logging.Logger Specialy my knowlabe about JNDI is to poor to replace the NonSerializableFactory easily. If anyone have ideas for that I will try to remove any reference to the jboss jars. The changed MBean is attached Thorsten
AvalonManager.java
Description: Binary data
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
