[cdi-dev] [JBoss JIRA] Commented: (CDI-23) Allow BeanManager to be resolved as though you were in another bean archive

Mark Struberg (JIRA) jira-events at lists.jboss.org
Mon May 9 10:25:18 EDT 2011

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

Mark Struberg commented on CDI-23:

> If an extension is provided in a shared library, then it would currently 
> see the BM which is applicable for the bean archive for that shared library

humm, in OWB - even if the Extension is in the shared lib of an EAR - you will get 1 instance of this very Extension _per_ _war_.
That's what I meant with 1 BeanManager per WAR in OWB in my explanation above. That's important because the extension might be configured completely different for each WAR. That's the same thing like saying your JSF container must be configured the same for each and every WAR deployed in an EAR.

> Allow BeanManager to be resolved as though you were in another bean archive
> ---------------------------------------------------------------------------
>                 Key: CDI-23
>                 URL: https://issues.jboss.org/browse/CDI-23
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Portable Extensions, Resolution
>    Affects Versions: 1.0
>            Reporter: Pete Muir
>             Fix For: 1.1 (Proposed)
> Currently it's not possible to access beans as though you were in another bean manager, something that is useful for extensions to be able to do. For example, if I want to create a facade over the ELResolver, or access a particular configuration bean.

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