Order of method calls for MBeanRegistration

[cfaucher]

Hello,

I'm new at JMX implementation. I have a question about the order the methods are calls on my Mbean. I am using JBoss MX (Jboss 3.0 - Tomcat 4.0.3).

More specifically, I have an DynamicMBean, which implements the MBeanRegistration interface as well. I noticed the methods are called in this order:
1 - preRegister(...)
2 - postRegister(...)
3 - setAttributeList(...)

Since I need attributes defined in my-service.xml, declaring the MBean, my initialisation fails in preRegister/postRegister, since these attributes are not yet set in my MBean. I am opening an HTTP connection (SOAP server), but I dont know the address to use yet.

I would have expected an order similar to:
1 - setAttributeList/setAttribute
2 - preRegister
3 - postRegister

Then, with this order, attributes are known from my-service-xml, and the service can use them to do actions around registration.

Am i right or wrong to expect this order?

Christian Faucher
Tetra Technologies.

[schaefera]

You can't change the order because this is part of the JMX spec. Note that you can hand over constructor arguments in the like:
<mbean ... >


...

...


Note that the list of arguments must match an available constructor in your MBean and that the type is important and that you don't now what it means in the service.xml file.

Have fun - Andy

[davidjencks]

You might want to implement the jboss service lifecycle, create/start/stop/destroy called in order by the container. setAttributes will be called before create. You don't have to implement all te methods as I recall... usually I use the non-dynamic ServiceMBeanSupport base class and a standard mbean.

[cfaucher]

Thanks for the suggestions and answers.

One more stupid question: could you point me to the interface/class name for the JBoss service interface?

Cheers!

Christian Faucher

[davidjencks]

org.jboss.system.Service, in the system module. I'm not sure you need to implement the interface explicitly if you have a dynamic mbean. The Container class is dynamic and uses the lifecycle stuff, you could compare. (server module, org.jboss.ejb.Container).

If you decide on a standard mbean, you want your interface to extend ServiceMBean and might want your class to extend ServiceMBeanSupport.

[cfaucher]

Thanks for the info!

Cheers,

Christian Faucher