[jboss-jira] [JBoss JIRA] Commented: (JBAS-9224) Automatic JNDI implementation
[
https://issues.jboss.org/browse/JBAS-9224?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on JBAS-9224:
------------------------------------
For the JPA case, I wonder if we could set the Hibernate properties to bridge the gap.
I'm not sure of how this would work but we do have the JPA PersistenceUnitService
representing the Persistence Provider EntityManagerFactory. If that helps, I would have
to toolkit the integration generically (for any persistence provider).
hibernate.jndi.java.naming.factory.initial
hibernate.jndi.java.naming.factory.url.pkgs
Automatic JNDI implementation
-----------------------------
Key: JBAS-9224
URL: https://issues.jboss.org/browse/JBAS-9224
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: EE, Naming
Reporter: David Lloyd
Assignee: John Bailey
Priority: Critical
Fix For: 7.0.0.Beta3
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira