[jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Next step in ServiceController Lifecycle

[adrian@jboss.org]

Related to this thread
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087219#4087219

Where I'd really like to get to is that the JMX lifecycle is tied to the POJO
lifecycle.

Currently the ServiceController advice just does a start() straight away
once the object is registered in jmx

  |       MBeanServer server = serviceController.getMBeanServer();
  |       server.registerMBean(mbean, objectName);
  |       try
  |       {
  |          serviceController.start(objectName);
  |       }
  | 

But what I really want is the following for the POJO states:
NOT_INSTALLED => MBean registered but with no management interface (Note 1)
INSTANTIATED => MBean gets real management interface
CREATE => serviceController.create(ObjectName)
START => serverController.start(ObjectName)
etc.

The Note 1 is because there should a simple management interface
where users can choose to start "on-demand" POJOs.

But I'm not sure what this would look like with the new lifecycle stuff.
What would the aop config look like for the different callbacks at different pojo events?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087223#4087223

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087223