[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger commented on CDI-129:
-------------------------------------
{quote} By not providing a scope bigger than 1 per WAR, we DO NOT HAVE THOSE
AFOREMENTIONED PROBLEMS IN CDI. {quote}
OK, assume there is a shared @RequestScoped bean R in the shared library injected both
into a Servlet in your web app and into the MailService. No alternatives nor
specialization this time. What you say is that the Servlet would operate on a different
instance of the same R bean than the MailService? In the same call stack during processing
of the single same request? How is that consistent? Maybe we could do a poll if this is
what people want ;-)
{quote} on which part? On the 'unusable' or the 'multiple contextual instances
per Injection Point for the same call stack'? {quote}
I disagree that it is unusable.
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