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

Mon Oct 22 08:34:01 EDT 2012

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

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

Coming in on discussions from the weekend.

1) Initial intent. I'm 100% sure that Gavin intended @ApplicationScoped to be shared across the EAR originally, and that the comment about "standard scopes defined by Servlet spec" was the mistake. However, as I've been proved wrong here before, I've double checked it with him. Hopefully I can get an answer soon!

2) Whilst you may see most people using CDI standalone, what we are actually specifying here is how CDI works in Java EE 7 and above, and this what we must focus on. We must take account, of course, these other users, but they are lower than other considerations like how CDI works in Java EE 7 and above, backwards compatibility with Java EE 6 application servers.

> 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