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

Gerhard Petracek (JIRA) jira-events at lists.jboss.org
Wed May 18 05:57:01 EDT 2011


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

Gerhard Petracek commented on CDI-129:
--------------------------------------

pete - no there was a different statement:

> "Therefore I would follow Marius suggestion and [...] add a clause indicating that non-portability is an issue here ..."

just specifying a recommendation (as suggested afterwards) isn't enough (imo)

... that was the reason for my answer.

> 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