[
https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-129:
-----------------------------------
Come on Jozef, do your homework
From the EE-6 umbrella spec referenced in CDI:
"EE.6.2.4.7 Context Class Loader
This specification requires that Java EE containers provide a per thread context class
loader for the use of system or library classes in dynamically loading classes provided by
the application. The EJB specification requires that all EJB client containers provide a
per thread context class loader for dynamically loading system value classes. The per
thread context class loader is accessed using the Thread method getContextClassLoader.
The classes used by an application will typically be loaded by a hierarchy of class
loaders. There may be a top level application class loader, an extension class loader, and
so on, down to a system class loader. The top level application class loader delegates to
the lower class loaders as needed. Classes loaded by lower class loaders, such as portable
EJB system value classes, need to be able to discover the top level application class
loader used to dynamically load application classes."
This will work perfectly fine without breaking any specs.
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