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

Wed Oct 17 05:24:01 EDT 2012

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

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

> In other words, CDI contexts are never isolated between bean archives.
I don't get that. Where do you read that I like to do that?

What I was talking about was that you always see only exactly 1 'slice' of a context for each Thread. All users share the same SessionContext, but still each request can only see the contextual instances of the single currently active session of each request.

The same would happen for webapplications. Each request knows to which webapp it belongs. And a single request can only belong to exactly one single webapp! So he will only see the @ApplicationScoped contextual instances of this very webapp the request is for.

> 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