[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-129:
-----------------------------------
Sorry Jozef, you are a pretty clever dude in general and you did hit quite some nails. But
in this case you started to drop "it is that way" sentences but missed the most
important part of it: the actual argument! I had expected something like "I think it
is that way BECAUSE ${argument}, ${quote}, etc" ;)
And no, it is not unrelated to cdi-1.0.
Another argument why we need further clarification. If you get the BeanManager from JNDI
then according to your interpretation you would like to get different results for
getBeans() depending on what? How would that ever work? Please shed some light, I
don't get it.
I think we would need to add some BeanManager#getBeans(injectionclass, type, qualifiers) +
resolve with the same + getReference ...
We do not have all that currently.
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