[cdi-dev] [JBoss JIRA] Commented: (CDI-129) Clarify behaviour of @ApplicationScoped in EARs
[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger commented on CDI-129:
-------------------------------------
There is a similar issue related to events. I am not sure if the proposed solution for the
@ApplicationScoped issues fixes the events issue implicitly or a clarification of the
Events chapter is needed. The issue follows:
Should a web application bundled within an ear should be notified of an event fired by
another web application bundled within the same ear? The observer resolution algorithm
should take bean visibility into account and notify only those observer methods from whom
the event firer is visible.
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