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

[Mark Struberg (JIRA)]

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

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

Btw, I do agree with you that we need to get a common understanding about how Modularity should work. The BDA approach was way too restrictive but a flat structure doesn't work neither.

Also the CDI spec prominently uses the terminus tecnicus 'bean' for 5 different things:

* Bean<T>
* the class which gets scanned and might lead to 0..n Bean<T>
* the Contextual Reference
* the Contextual Instance
* the Type on the Injection Point

Even in the aforementioned paragraph 5.1 many those 5 meanings are perfectly mixed up.

                
> 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