This won't work because it requires the mbean code to use the annotations. The point of the indirection was to allow the deployment descriptor to specify the class to parse for the annotations, and to provide that as part of the server integration code. So, a queue would use the mbean/annotation to indicate the class to pass to the AbstractManagedObjectFactory: | <mbean code="org.jboss.jms.server.destination.QueueService" | name="jboss.messaging.destination:service=Queue,name=DLQ" | xmbean-dd="xmdesc/Queue-xmbean.xml"> | <annotation&gt;(a)org.jboss.system.deployers.managed.ManagementObjectClass(code=&quot;org.jboss.jms.server.destination.QueueServiceMO&quot;)&lt;/annotation&gt; | <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> | <depends>jboss.messaging:service=PostOffice</depends> | </mbean> | The org.jboss.jms.server.destination.QueueServiceMO class would be in the jbossas/messaging integration codebase. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102688#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...