This has turned out more difficult than I expected because of how the ManagedObjectFactory/Builder are oriented towards creating a ManagedObject template from a Class view that is expected to have the management annotations on it.
The problem for the JBAS-6676 issue is that there is a bean factory creating BeanMetaDatas for bean proxies whose ManagedObject interface is to mirror the JMX mbean the proxy is to promote to a ManagedObject.
One way would be to add an annotation on the metadata instance via the mdr MetaData view that is passed into the ManagedObjectFactory.
Another would be to have the metadata instance implement an ObjectInstanceFactory interface or some such that assumed the ManagedObjectFactory task of creating the ManagedObject based on the instance metadata.
Either of these could be done in time for the CR1 release. Neither one seems ideal, I'm trying each to see which is most natural for the user wanting to describe a ManagedObject.
More generally I'm thinking the way in which we create MangedObjects for a deployment should change to have the DeployersImpl generate the ManagedObjects in two passes, the first that creates a ManagedObjectMetaData view attachment if one does not exist, and then creates the ManagedObjects from this. This would allow more flexibility in how the ManagedObject view is created.
