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

Mark Struberg (JIRA) jira-events at lists.jboss.org
Sun Oct 21 02:15:04 EDT 2012

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

Mark Struberg commented on CDI-129:

EAR is only defined in EE. I see no way to deploy an EAR to a non-EE server ;)

All the other mentioned stuff like MDB, @Timeout, etc are ALL EJB parts as well.
A legacy application could still use a simple static field if they like to share state. That was the way they did it with Spring and they will do it with CDI as well.

Btw, actually most CDI users I know do NOT use an EE6 server but still EE5 + either Weld or OWB in their webapps. Amongst them are huge banks, 2 of the 10 biggest stock exchanges worldwide, the biggest international military pact and, some universities, etc. They all run those 'big irons' and replaced Spring with Weld or OpenWebBeans. I actually know _very_ few projects who already use a big EE6 server in production. To be honest: non of the big companies I know use it yet, they are still just testing.

And now please answer me what all those companies do get if they drop Weld or OpenWebBeans into their webapps and add the ServletListener to boot the CDI container? Exactly, they get 1-per-WAR behaviour.
> 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 mailing list