Details
-
Task
-
Resolution: Done
-
Critical
-
None
-
None
Description
The JNDI subsystem should become fully service-oriented, meaning:
1) Contexts are always read-only
2) The NamingStore is populated solely by services
3) When the last binding in a context is removed, the context is automatically removed
For pesky legacy subsystems which still expect to be able to bind into Context, we could possibly make up a "fake" Context from which the bound ObjectFactory (or whatever) is extracted to create the "real" service.
Attachments
Issue Links
- blocks
-
AS7-242 @EJB injection with same "name" on two different fields leads to DuplicateServiceException
- Resolved
- is blocked by
-
AS7-604 Fix injection of global resources
- Closed
-
AS7-218 hibernate fails to bind session factory name to jndi
- Closed
- is related to
-
AS7-2667 Applications cannot use Hibernate hibernate.session_factory_name
- Closed
- relates to
-
AS7-4990 Cannot embed Jersey 1.13-b01 with error: UnsupportedOperationException: JBAS011859: Naming context is read-only
- Resolved