[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-129:
-----------------------------------
Gosh Jozef, please don't drive me nuts! just read the thread above to find it!
a.) It is not clear what the term 'Bean' used in 5.1 means
b.) Pete was not sure about the TCCL, go on read the TCCL paragraph again please. Imo it
is relevant.
c.) your interpretation is contradicted by the example shown in "2.2. Bean
types"
d.) the whole BeanManager API design contradicts your arguments
what else?
The spec is just not clear. I f***n don't care on which end. If A contradicts B then
there are 3 ways to fix that: fix A, fix B or fix both.
To me the only sure thing is that we need to fix something as no possible interpretation
closes all the gaps. Although the interpretation with the 1 per WAR would imo be the
closest one and is also the only interpretation EXPLICITLY defined in the spec. All other
interpretations are just indirect consequences of other definitions.
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