"scott.stark(a)jboss.org" wrote : | 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. | The way I look at it, whether an class is exposed via management or not, is configuration information - deploy time configuration, and should not be hardcoded into the source. Actually this is a gripe I have with annotations as they are used in many situations - deploy time meta-data infects the source. This seems plain wrong to me. Yes, one way around this is to move out those classes into an integration layer, but since the same classes need to be used in a non MC environment we would then have to maintain two versions of the same classes - one with and one without the annotations in the worst case, or at least subclass the files with versions with annotations and put the annotated subclasses in an integration layer. This seems very hacky to me. I believe deploy time meta data (which this is) belongs in configuration files, not in the source code! Can't we just specify management in our microcontainer jbm-beans.xml config? This would make more sense to me. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131056#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...