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

[Aslak Knutsen (JIRA)]

    [ https://issues.jboss.org/browse/CDI-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579437#comment-12579437 ] 

Aslak Knutsen commented on CDI-84:
----------------------------------

To my understanding, a BeanArchive packaged in a WAR or EAR's(EE Modules) library folder should not trigger the creation of a BeanManager unless the EE module itself is a BeanArchive.


ps: I might be referring to the wrong Spec point here. 
pss: This might be a dup of CDI-49 depending on the definition of available(create vs visible).

Between this and CDI-49, the general point is: Where ever the BeanArchive is located and whether or not you yourself(the caller) is a BeanArchive, you should see a BeanManager with content that follow the normal EE class visibility rules. (of course only if there are any BeanArchives within your visible range)

> 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