[cdi-dev] [JBoss JIRA] (CDI-129) Clarify behaviour of @ApplicationScoped in EARs

Thu Oct 18 04:30:01 EDT 2012

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

Mark Struberg commented on CDI-129:
-----------------------------------

I already explained the argumentation chain which allows to interpret 5.1 to perfectly fit this picture in some posts above.

BDA is btw is currently broken and the EG is working on a solution right now. See CDI-18.
To interpret 5.1 in the way you propose would contradict the definitions of
* BeanManager#getBeans(String)
* BeanManager#getBeans(Class)
* BeanManager#resolve()
* BeanManager#getReference(Bean<?>, Type, CreationalContext<?>)

In other words: that would be broken for EARs as well.

> Clarify behaviour of @ApplicationScoped in EARs
> -----------------------------------------------
>
>                 Key: CDI-129
>                 URL: https://issues.jboss.org/browse/CDI-129
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Contexts
>    Affects Versions: 1.0
>            Reporter: Mark Struberg
>            Assignee: Pete Muir
>             Fix For: 1.1 (Proposed)
>
>
> Since @ApplicationScoped currently is defined in 6.5.2 as to be 'like in the Servlet specification' this means that you will get a new instance for every WebApplication (WAR file).
> There is currently no specified CDI scope for providing a single shared instance for a whole EAR.
> We could (ab-)use @Singleton for that, but this is currently not well defined at all.
> Alternatively we could introduce an own new annotation like @EnterpriseScoped or likes. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira