"scott.stark(a)jboss.org" wrote : Yes, but I"m not sure what else might need to be updated to support this yet. I believe the existing jmx notification based stuff should map over to an aspect that exposes a ManagedDeployment and its ManagedComponents as the jsr77 mbeans. I think we should really be doing this on the ManagedObjects? We already have a type, so once we have the notion of scope in the ManagedObjects it should be relatively trivial to map them to the jsr77 tree/naming convention? I think the only issue is whether we enforce that the POJOs/MBeans should implement the jsr77 classes, e.g. the statistics classes or whether we do some adaption in the jsr77 facade? I'd favour the latter simply because it allows the implementation to provide custom extra statistics and seperate the invocation/pooling/caching stats while still being able to map them to the standard classes for jsr77. The downside is that it is going to require some knowledge (hard wiring) of the real implementation in the jsr77 facade to make this work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015054#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...