[weld-issues] [JBoss JIRA] Updated: (WELD-765) Simplify access to a deployment's BeanManager, when its id (or the BDA id) is known

Pete Muir (JIRA) jira-events at lists.jboss.org
Tue Dec 7 10:37:01 EST 2010


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

Pete Muir updated WELD-765:
---------------------------

    Fix Version/s: 1.2.0.Beta1
                       (was: 1.1.0.CR1)


> Simplify access to a deployment's BeanManager, when its id (or the BDA id) is known
> -----------------------------------------------------------------------------------
>
>                 Key: WELD-765
>                 URL: https://jira.jboss.org/browse/WELD-765
>             Project: Weld
>          Issue Type: Feature Request
>          Components: Weld SPI
>    Affects Versions: 1.1.0.Beta2
>            Reporter: Marius Bogoevici
>             Fix For: 1.2.0.Beta1
>
>
> Currently, the BM id and BDA ID are practically equivalent.
> Retrieving the BeanManager if said ID is known requires iterating Deployment.getBeanDeploymentArchives() until the BDA is found and then retrieving the BeanManager from the deployment by using Bootstrap.getManager(BeanDeploymentArchive beanDeploymentArchive).
> This can be simplified by introducing Deployment.getBeanDeploymentArchive(String BDAid). Another possibility is to provide Bootstrap.getManager(String  bdaID). Both variants would simplify the access code and make it work faster.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the weld-issues mailing list