[cdi-dev] [JBoss JIRA] (CDI-129) Clarify behaviour of @ApplicationScoped in EARs
[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-129:
-------------------------------
{quote}
naturally (reading the spec the fisrt time) i thought about 2) but if Module == webapp for
war (what about bda? if module is taken from JEE definition that sounds fine for me)
{quote}
Right, somewhat confusingly (though understandable perhaps if you think of the age of the
Java EE spec), Java EE names EJB JARs, WARS etc as "modules". Modules are *not*
the same as a library (e.g. which goes in WEB-INF/lib or is installed in the app server).
However I'm not sure about @ModuleScoped, for the obvious reason that the word module
has a wider meaning, especially if modularity makes it into the JDK. I suspect we need
another term :-(
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