[
https://issues.jboss.org/browse/CDI-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Muir updated CDI-49:
-------------------------
Component/s: Java EE integration
> The availability of the BeanManager should follow the normal EE visibility
> rules
> --------------------------------------------------------------------------------
>
> Key: CDI-49
> URL: https://issues.jboss.org/browse/CDI-49
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Java EE integration, Packaging and Deployment, Resolution
> Affects Versions: 1.0
> Environment: JSR-000316 Java Platform, Enterprise Edition 6
> Specification
> Reporter: Aslak Knutsen
>
> EE 6 spec
> EE.5.19
> A bean manager is only available in modules in which CDI has been enabled.
> In e.g. a EAR deployment, a WAR module can see a EJB module. With CDI enabled
> in the EJB, the WAR can only see the BeanManager if the WAR itself is also
> CDI enabled. In cases where you want to do dynamic introspection of available
> beans etc, this is a bit cumbersome, especially since the introspecting code
> can be in a packaged jar inside a unknown WAR..
--
This message is automatically generated by JIRA.
-
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
