[jboss-jira] [JBoss JIRA] (AS7-1338) Remote JNDI support for AS7

[Ed Keen (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665121#comment-12665121 ] 

Ed Keen commented on AS7-1338:
------------------------------

I added a context.close() right after I send the message, and I am still seeing the error being logged.  Since this does not affect functionality, we can wait until the patch makes its way through.  Any chance this will go out with 7.1.0 Final?
                
> Remote JNDI support for AS7
> ---------------------------
>
>                 Key: AS7-1338
>                 URL: https://issues.jboss.org/browse/AS7-1338
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Naming
>            Reporter: Richard Opalka
>            Assignee: John Bailey
>            Priority: Critical
>              Labels: eap6_prd_req
>             Fix For: 7.1.0.Final
>
>
> Add support for remote JNDI after all.  It was agreed that:
> * Remote JNDI would run over Remoting
> * Remote JNDI for EJB is strictly a legacy access protocol, deprecated in favor of "ejb:"
> * The Remote JNDI service would proxy to a specific Context of the server JNDI tree - maybe "java:jboss/shared", maybe something else
> * Server-side services would opt-in to Remote JNDI; initially we'd only support:
> ** Remote EJB interfaces
> ** HornetQ connection factories
> * In the future we may support:
> ** User bindings, so long as they're serializable
> * In the future we will never support:
> ** Proxied DataSources
> ** Proxied JMS invocations
> Initial project tree is at https://github.com/dmlloyd/jboss-remote-jndi for now.

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