Here is another approach that also moves toward having the annotations in the xml config. We do have some annotation support in the service mbean descriptors, for example: | <mbean name="jboss.test:type=BasicMBeanName" code="BasicMBeanCode"> | <annotation>@org.jboss.test.system.metadata.annotation.CompType(type="DS",subtype="LocalTX")</annotation> | </mbean> | so I can add a ManagedCode annotation that allows you to specify the class to scan for the management annotations. You can then add empty subclasses of the jms destination mbeans in the server/messaging project and then specify the management annotations on those, and point to those classes using the annotation element. Perhaps this can reuse the legacy mbeans Clebert updated. I have reopened JBAS-4658 for this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087289#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...