[cdi-dev] [JBoss JIRA] (CDI-129) Clarify behaviour of @ApplicationScoped in EARs
Mark Struberg (JIRA)
jira-events at lists.jboss.org
Thu Oct 18 02:57:01 EDT 2012
[ https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727517#comment-12727517 ]
Mark Struberg commented on CDI-129:
> The same thing would happen for a @Dependent scoped bean
> or a @Request scoped bean. Although Mark thinks that restricting
> @ApplicationScoped per war fixes this it actually does not.
Again Jozef, this is JUST NOT TRUE for CDI!
The problem is not the scope of the bean which gets injected, but the scope of the bean you inject into. Are we d' accord on this part? It just doesn't friggin depend whether the injected bean is @Dependent, @SessionScoped or @DumbassScoped!
By not providing a scope bigger than 1 per WAR, we DO NOT HAVE THOSE AFOREMENTIONED PROBLEMS IN CDI.
We could go on and define the behaviour for scopes larger than 1 per WAR in CDI 1.1.
We EJB EG would probably need to clarify the restrictions for injecting into shared stateful EJBs, but indeed that is not so much a problem of CDI.
> I disagree.
on which part? On the 'unusable' or the 'multiple contextual instances per Injection Point for the same call stack'?
> 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
More information about the cdi-dev