[jboss-jira] [JBoss JIRA] Updated: (JBAS-7580) Move RemoteNamingBean to deploy

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated JBAS-7580:
-----------------------------------

    Fix Version/s: JBossAS-6.0.0.M3
                       (was: JBossAS-6.0.0.M2)


ProfileService changes in M3 could make this issue obsolete.

> Move RemoteNamingBean to deploy
> -------------------------------
>
>                 Key: JBAS-7580
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7580
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Naming
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-6.0.0.M3
>
>
> RemoteNamingBean is currently in deployers. Move it to deploy.  Bean Validation's JndiBinder is using JNDI in deployers, but it only needs LocalNamingBean. Once LocalNamingBean is deployed, any new InitialContext() call inside the AS will find the local server, so that should be sufficient; nothing in deployers should need RemoteNamingBean.

-- 
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