[cdi-dev] [JBoss JIRA] Commented: (CDI-129) Clarify behaviour of @ApplicationScoped in EARs
Mark Struberg (JIRA)
jira-events at lists.jboss.org
Wed May 18 07:49:01 EDT 2011
[ https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602901#comment-12602901 ]
Mark Struberg commented on CDI-129:
-----------------------------------
Yes stu, I confused the paragraphs. What I meant was
> 2.4.1. Built-in scope types
> The @RequestScoped, @ApplicationScoped and @SessionScoped annotations defined in Section 6.7,
> “Context management for built-in scopes” represent the standard scopes defined by
> the Java Servlets specification.
which clearly says 1 contextual instance for each webapp.
> 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 (Confirmed)
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the cdi-dev
mailing list