[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Gerhard Petracek commented on CDI-129:
--------------------------------------
that's also not "more objective", because it isn't only mark who has
this opinion.
since openwebbeans handles it that way, the owb team agreed on it as well.
i know a lot of big projects which (have to) use EARs as "deployment-bundles"
for huge applications, but every web-app has to be independent, but they share e.g.
portable cdi extensions like deltaspike, codi, seam3, ... if you don't follow his
recommendation in this case, you break them all (for weld based servers).
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