[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Romain Manni-Bucau edited comment on CDI-129 at 10/18/12 5:28 PM:
------------------------------------------------------------------
i understood it (and in implementation that's consistent) as "let the ejb
container manage it" and don't add a proxy in front on another proxy. The best
choice in CDI 1.0 IMO
was (Author: rmannibucau):
i udnerstood it (and in implementation that's consistent) as "let the ejb
container manage it" and don't add a proxy in front on another proxy. The best
choice in CDI 1.0 IMO
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