[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-129:
-----------------------------------
For my side I have a pretty clear opinion:
We have 3 options as listed above, and the one which makes users get different contextual
instances depending on where the injection into gets made is an absolute no-go.
So 2 Options remain (and I will not argue about which one is in the spec, because BOTH are
covered + contradicted in CDI 1.0)
either
* restrict @Specializes and @Alternative to all non Object.class CDI-Bean Types to the
outermost module
* go with semi-static wiring IF needed. Again: this is NOT needed if we do not inject into
a bean which is of a broader scope than 1 per webapp! By clarifying that
@ApplicationScoped is 1 per WAR we could use fully static wiring for all CDI beans!
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