"adrian(a)jboss.org" wrote : I think there's also a dependency with the AspectManager bean expecting | ServiceMBeanSupport to be available. | | But JMX deployment should come after AOP. | | The eventual idea is to make JMX optional. I am putting the original AspectManagerService code in a delegate and wrapping that in a POJO (MC/AS5) and in a class extending ServiceMBeanSupport (AS4). However, the original code contains a few methods to do with JMX from ServiceMBeanSupport such as sending out JMX notifications, getting the ObjectName of the service, getting the MBeanServer etc. Can all that stuff be left out for the MC/AS5 version? I am not really clear on how the MC beans eventually get mapped onto JMX in AS5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176848#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...