9:35 a.m.
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
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
9:35 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-9224) Automatic JNDI implementation
[
https://issues.jboss.org/browse/JBAS-9224?page=com.atlassian.jira.plugin....
]
David Lloyd updated JBAS-9224:
------------------------------
Fix Version/s: 7.0.0.Beta3
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
10:54 p.m.
New subject: [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:
------------------------------------
test SessionFactoryTestCase fails during testsuite/integration. The deployment error is
shown here: http://pastebin.com/0LrgKPcw
The Hibernate "hibernate.session_factory_name" property is mentioned here:
http://docs.jboss.org/jbossas/jboss4guide/r3/html/ch13.html#ch13.config.t...
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
11:06 p.m.
New subject: [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:
------------------------------------
better doc is here
http://docs.jboss.org/hibernate/core/3.3/reference/en/html/session-config...
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
8:56 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9224) Automatic JNDI implementation
[
https://issues.jboss.org/browse/JBAS-9224?page=com.atlassian.jira.plugin....
]
Steve Ebersole commented on JBAS-9224:
--------------------------------------
For Hibernate, as a "pesky legacy subsystems" that uses a standard Java-defined
API {{Context#bind}} to attempt to make users lives easier, what do you suggest we do?
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
9:08 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9224) Automatic JNDI implementation
[
https://issues.jboss.org/browse/JBAS-9224?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JBAS-9224:
-----------------------------------
Nice, Steve. :)
To bind things into JNDI your corresponding subsystem must go through the service layer.
Otherwise, if things express an injection dependency on a JNDI binding it will not start
in the right order and the whole thing falls apart. Note that there's nothing in the
EE spec that says that the "java:" JNDI context should be writable by the user.
The mechanism specified in the description allows things which inflexibly require JNDI
binding to be effectively faked out so that it can still work, at the cost of some perf.
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
9:15 a.m.
New subject: [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
11:21 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-9224) Automatic JNDI implementation
[
https://issues.jboss.org/browse/JBAS-9224?page=com.atlassian.jira.plugin....
]
David Lloyd updated JBAS-9224:
------------------------------
Fix Version/s: 7.0.0.Beta4
(was: 7.0.0.Beta3)
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.Beta4
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
11:54 p.m.
New subject: [JBoss JIRA] Updated: (AS7-421) Automatic JNDI implementation
[
https://issues.jboss.org/browse/AS7-421?page=com.atlassian.jira.plugin.sy...
]
Jason Greene updated AS7-421:
-----------------------------
Fix Version/s: 7.1.0.Alpha1
(was: 7.0.0.CR1)
This is mostly done but moving it to 7.1 to track the hibernate issue.
Automatic JNDI implementation
-----------------------------
Key: AS7-421
URL: https://issues.jboss.org/browse/AS7-421
Project: Application Server 7
Issue Type: Task
Components: EE, Naming
Reporter: David Lloyd
Assignee: John Bailey
Priority: Critical
Fix For: 7.1.0.Alpha1
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
10:20 p.m.
New subject: [JBoss JIRA] Updated: (AS7-421) Automatic JNDI implementation
[
https://issues.jboss.org/browse/AS7-421?page=com.atlassian.jira.plugin.sy...
]
Jason Greene updated AS7-421:
-----------------------------
Fix Version/s: 7.1.0.Beta1
(was: 7.1.0.Alpha1)
Automatic JNDI implementation
-----------------------------
Key: AS7-421
URL: https://issues.jboss.org/browse/AS7-421
Project: Application Server 7
Issue Type: Task
Components: EE, Naming
Reporter: David Lloyd
Assignee: John Bailey
Priority: Critical
Fix For: 7.1.0.Beta1
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
1:52 p.m.
New subject: [JBoss JIRA] (AS7-421) Automatic JNDI implementation
[
https://issues.jboss.org/browse/AS7-421?page=com.atlassian.jira.plugin.sy...
]
David Lloyd resolved AS7-421.
-----------------------------
Resolution: Done
This is finished.
Automatic JNDI implementation
-----------------------------
Key: AS7-421
URL: https://issues.jboss.org/browse/AS7-421
Project: Application Server 7
Issue Type: Task
Components: EE, Naming
Reporter: David Lloyd
Assignee: John Bailey
Priority: Critical
Fix For: 7.1.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4586
days inactive
4797
days old
10 comments
5 participants
participants (5)
-
David Lloyd (JIRA) -
David Lloyd (Resolved) (JIRA)
-
Jason Greene (JIRA)
-
Scott Marlow (JIRA)
-
Steve Ebersole (JIRA)