[jboss-jira] [JBoss JIRA] Updated: (JBAS-7709) Review beans that bind in JNDI to add a dependency on Naming

[Ondrej Žižka (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-7709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Žižka updated JBAS-7709:
-------------------------------

    Attachment: jboss-ejb3-tutorial-mdb.jar


Attaching EJB which causes
javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099
when shutting down.

> Review beans that bind in JNDI to add a dependency on Naming
> ------------------------------------------------------------
>
>                 Key: JBAS-7709
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7709
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-6.0.0.M3
>
>         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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira