[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger edited comment on CDI-129 at 10/18/12 4:16 AM:
---------------------------------------------------------------
{quote}I cannot see any classloading issue!{quote}
The fact that you could possibly implement it that way does not mean that it is the right
thing to do nor does it mean that it is the correct interpretation of the spec.
{quote}Btw: Weld 1.x and 2.x implement it EXACTLY THAT WAY ALREADY!{quote}
This is not true. Even if it was it would only mean that there are bugs in Weld. That
happens.
was (Author: jharting):
{quote}I cannot see any classloading issue!{quote}
The fact that you could implement it does not mean that it is the right thing to do nor
does it mean that it is the correct interpretation of the spec.
{quote}Btw: Weld 1.x and 2.x implement it EXACTLY THAT WAY ALREADY!{quote}
This is not true. Even if it was it would only mean that there are bugs in Weld. That
happens.
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