Another item which might be important to mention is the differences in building managedObjects. Whereas most spec deployment descriptor (ejbs, wars) mostly represent the desired management view already (excl. metrics). This is different for jboss-beans.xml and -service.xml which are more assembly descriptors than something directly usable for management. In AS5 we are already applying some changes based on the managedObject view to the actual deployment descriptor which is quite tricky, as the actual injected value might differ from the deployment descriptor - especially for more complex values - like we had for the ServiceBindingManager. Also those changes would need to get applied earlier not after classloading to support something like offline-edits. I'll start with some changes in jboss-man, which we should do regardless of the additional requirements for the domain model. Basically starting with separating the population with the building of ManagedObjects. This should be a separate step, maybe even built on a different managedObject metadata/structure. This description represents a model for the managedObject itself and should be reusable for the same type of components - only that the values are going to be different. The deployers integration could also be improved, to something a bit more explicit where we don't process the same meta data several times. I also want to move some Component processing (currently done in the ManagementView) more in this model building. Maybe the only thing the ManagementView should do is to create some composite ManagedObjects - containing more managedObjects which cannot be grouped during this building process. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261854#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...