This is a known "bug" (really a configuration issue) currently in JBoss5.

The issue is that the AOP advice for @JMX is not installed until
after conf/jboss-service.xml or bootstrap-beans.xml is processed.

This is because it is done by the aop deployer which runs later.

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=125347

In general the implementation details (rather than the deployment layer)
like the transaction manager  should be in "deploy" anyway, 
\but there's lots of work to be done before that is possible. e.g.
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112404
to properly define dependencies and make sure deployers are 
properly seperated from runtime infrastructure.

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

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115034
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to