"timfox" wrote : "@JMX" is not a standard annotation from the JDK libraries, so we can't have it in our core classes since it will introduce a build time dependency on whatever library that comes from (AOP?), and we don't want to force our embedded users to drag in jars they don't need. This is the main issue that requires administration to be treated as an aspect that can be applied as an integration concern. We override the default jms destinations to apply the management aspect in jbossas. In general, we need to support different aspect mappings to allow projects to use whatever is natural to them. If you want to use jmx, fine. If you want to use the mc @ManagementObject stuff, fine. The integration layer need to define the correct aspect that allows this information to be properly brought into the management view of the environment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130913#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...