[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Bauke Scholtz commented on CDI-129:
-----------------------------------
Dupont Dupont has a very valid question in #4. This is currently completely blocking the
usage of JSF utility library OmniFaces in multiple WARs in the same EAR which is deployed
to a Java EE 6 compatible container. See also
https://code.google.com/p/omnifaces/issues/detail?id=251.
I only wonder, isn't specifically this issue already fixed by
https://issues.jboss.org/browse/WELD-1259? Haven't tried Weld 2 yet as JBoss AS 7 /
EAP 6 can't be upgraded to use Weld 2.
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
Labels: application-scoped, visibility
Fix For: TBD
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