The AspectManager bean needs to depend on the mbeanserver in order to register itself into JMX, and appying @JMX to that will not work since the @JMX aspect in turn will depend on the AspectManager service? This was originally done to be able to run the AOP testsuite since that needs to turn on weaving with JMX. I see what you mean wrt the JBossServer being injected at the end. I'll try creating a new wrapper bean for the JMX registration of the AspectManager so that the original AspectManager can start up in the same way as in the standalone tests then. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009965#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...