[jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-362) Need InstanceClassFactorys to properly extract the managed object information from KernelDeployment/BeanMetaDataFactory

[Scott M Stark (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMICROCONT-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott M Stark updated JBMICROCONT-362:
--------------------------------------

    Fix Version/s:  JBossMC-2.2.0.GA
                       (was: JBossMC.2.0.0.GA )


A KernelDeploymentManagedObjectCreator is being developed in jbossas. A default managed object creator can be integrated into the mc in the future.


> Need InstanceClassFactorys to properly extract the managed object information from KernelDeployment/BeanMetaDataFactory
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMICROCONT-362
>                 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-362
>             Project: JBoss Microcontainer
>          Issue Type: Feature Request
>          Components: Deployment
>    Affects Versions: JBossMC.2.0.0.CR2
>            Reporter: Scott M Stark
>             Fix For:  JBossMC-2.2.0.GA
>
>
> The current behavior of the AbstractManagedObjectFactory/AbstractManagedObjectPopulator requires that the attachment metadata is what is annotated with the management information. This is not the case for the mcbeans. Similar to mbeans, the deployment metadata points to the bean class which is what is annotated with the management information.
> An InstanceClassFactory can return the bean class which should be scanned for management annotations.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira