[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-129:
-----------------------------------
coming back to Stuarts comment:
"The application context is shared between all servlet
requests"
Ok, if you take it so word for word: in this case, since it
doesn't say 'per EAR', we obviously must share the ApplicationContext even
across different EARs on the same Server? See, it doesn't specify the EAR in this
paragraph, so the only specific definition is in 2.4.1.
@Jozef: I think we already clarified somewhere that events must only be sent to active
Contexts. This e.g. happens if you try to send an event in a ServletFilter to a JSF
related Context.
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