[cdi-dev] [JBoss JIRA] (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:
-------------------------------------
{quote} No of course not! At least not in my model {quote}
OK, let's assume then that we took the approach 3) you proposed above
(@ApplicationScoped per war) which claims to fix the issue. If the web app in my example
above introduces a class
{code:JAVA}
@RequestScoped
@Specializes
public class S extends R {
}
{code}
The Servlet would arguably operate on an instance of S. Assuming the servlet invokes the
shared mail service, instance of which class would MailService operate on?
a) R, which means that the problem is not fixed and you are wrong (@ApplicationScoped per
war does not change anything)
b) S, however S is not accessible from the MailService so this is wrong
From there we can see that @ApplicationScoped is per war has no impact
on the "issue" that which you described as "user no-go".
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