[
https://jira.jboss.org/browse/JBAS-7709?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated JBAS-7709:
-----------------------------------
Fix Version/s: 6.0.0.Final
(was: 6.0.0.M4)
It is quite likely this will be moved to "Unscheduled" unless someone else wants
to take it on.
Review beans that bind in JNDI to add a dependency on Naming
------------------------------------------------------------
Key: JBAS-7709
URL:
https://jira.jboss.org/browse/JBAS-7709
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 6.0.0.Final
Attachments: jboss-ejb3-tutorial-mdb.jar
There are a number of services/beans that bind things in JNDI that just assume a naming
server is available. This assumption is only valid because historically the local Naming
server has been deployed in a "deployment phase" prior to when those services
are deployed. A proper dependency should be declared to make server startup more robust.
The MC name of the bean to depend on is "LocalNamingBean" but IMHO we should
give it a different name or an alias. Perhaps just "LocalJNDI". "JNDI"
sounds tempting but some I think the name should make clear that no remote capability
exists.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira