[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Marius Bogoevici commented on CDI-129:
--------------------------------------
Pete said:
{quote}
In fact, this makes me wonder if there isn't an "obvious" solution staring
us in the face? If we clarify that @ApplicationScoped means "shared across the
ear" and also that the same bean class packaged in two locations which are not
visible to one another (e.g. warA and war B) and cannot share state. Now we provide both
options of ear scoped state and war scoped state, and the state is only shared if the bean
class is packaged in a shared library or shared module (e.g. ejb module).
{quote}
This is correct and will reflect the preservation of behaviour when WARs are packaged
inside EARs. At the same time please note that the deployment of the same class in
multiple archives within the same deployment is deemed non-portable. So perhaps we can add
a clause indicating that non-portability is an issue here *if the beans from different
archives are visible at the same time*.
introduce @EnterpriseScoped (or similar)
----------------------------------------
Key: CDI-129
URL:
https://issues.jboss.org/browse/CDI-129
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Mark Struberg
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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira