[
https://issues.jboss.org/browse/WELD-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ales Justin resolved WELD-765.
------------------------------
Fix Version/s: (was: 1.2.0.Beta1)
Resolution: Out of Date
New OSGi API (imo) fixes this.
> Simplify access to a deployment's BeanManager, when its id (or the BDA id) is
> known
> -----------------------------------------------------------------------------------
>
> Key: WELD-765
> URL: https://issues.jboss.org/browse/WELD-765
> Project: Weld
> Issue Type: Feature Request
> Components: Weld SPI
> Affects Versions: 1.1.0.Beta2
> Reporter: Marius Bogoevici
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
