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

[Pete Muir (JIRA)]

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

Pete Muir commented on CDI-129:
-------------------------------

We discussed this, and we are strongly in favor of:

* @ApplicationScoped being shared across the EAR
* Visibility rules being applied as described in CDI 1.0

Other approaches are very interesting, and should be prototyped, but we don't believe that changing the way either of these concepts works from certain 1.0 CDI implementations is correct.

Note that we don't believe the concerns raised about specialization and alternatives to truly be an issue, as beans which have been specialized, and beans for which there is a selected alternative are not enabled in the application in the 1.0 specification.

Working on the assumption that the EG is not agreed on this position, I will start a vote on this topic next week.
                
> 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