[cdi-dev] [JBoss JIRA] Updated: (CDI-84) Non EE modules should be able to trigger creation of a BeanManager

Pete Muir (JIRA) jira-events at lists.jboss.org
Tue Feb 1 12:27:39 EST 2011

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

Pete Muir updated CDI-84:

    Fix Version/s: 1.1 (Proposed)
                       (was: TBD)

> Non EE modules should be able to trigger creation of a BeanManager
> ------------------------------------------------------------------
>                 Key: CDI-84
>                 URL: https://issues.jboss.org/browse/CDI-84
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Java EE integration, Packaging and Deployment
>    Affects Versions: 1.0
>            Reporter: Aslak Knutsen
>             Fix For: 1.1 (Proposed)
> EE.5.19
> A bean manager is only available in modules in which CDI has been enabled.
> Where EE modules are defined to be; ejb-jar, rar, client jar and war. 
> This is a missmatch between the EE spec and the CDI spec. According to the CDI spec, any archive with a beans.xml is defined as a BeanArchive and should be included in a BeanManager, EE define it to be only EE modules should trigger BeanManager creation. 
> Opening this up to follow the CDI spec will let any library use the BeanManager to introspect other BeanArchives without having to involve the owning EE module in the loop.

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


More information about the cdi-dev mailing list