Cool, so I'm still going the POJO route to pave the way for the future. Plus it's easy to just write a deployer to do this. What I'm seeing however, is that only *one* @ManagedObject is exposed per DeploymentUnit, and it's whatever the last one added by my deployer is. ManagedDeployment: vfszip:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x/build/output/jboss-5.2.0.Beta/server/default/deploy/stateless-test.jar/ | +++ ManagedComponent(name=org.jboss.ejb3.metrics.deployer.BasicStatelessSessionInstanceMetrics, type=(ComponentType{type=MCBean, subtype=*}), compName=jboss.j2ee:service=EJB3,name=UnsecuredStatelessBean-metrics-instance, attachment: org.jboss.ejb3.metrics.deployer.BasicStatelessSessionInstanceMetrics | ++++++ properties: [removeCount, currentSize, maxSize, createCount, availableCount Is this because of a non-unique name for the attachment? du.addAttachment(BeanMetaData.class, bean); The following does not pick up any attachments: du.addAttachment(uniqueName, bean, BeanMetaData.class) What's the deployer which inspects the DU attachments? Once I get all my attachments in place, I'm done w/ exposing EJB3 Metrics :) S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234009#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...