[jboss-jira] [JBoss JIRA] (WFLY-368) Naming subsystem <lookup> could use LinkRef/Reference

[Jason Greene (JIRA)]

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

Jason Greene updated WFLY-368:
------------------------------

    Fix Version/s: 8.0.0.Alpha3
                       (was: 8.0.0.Alpha2)

    
> Naming subsystem <lookup> could use LinkRef/Reference
> -----------------------------------------------------
>
>                 Key: WFLY-368
>                 URL: https://issues.jboss.org/browse/WFLY-368
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Naming
>            Reporter: James Livingston
>            Assignee: Eduardo Martins
>             Fix For: 8.0.0.Alpha3
>
>
> NameBindingAdd.installLookup() sets up the machinery so that when Context.lookup() is done it looks up the redirected name and returns it.
> It should be possible to do that by binding a LinkRef, Reference or similar object into JNDI instead.
> Where this could make a difference is when Context.lookupLink() is called instead.
> Currently if you have
>    <simple name="java:/v" value="hello"/>
>    <lookup name="java:/a" lookup="java:/b"/>
> lookupLink("java:/a") will return "hello" rather a LinkRef/Reference/whatever pointing to java:/b.
> We need to decide whether a <lookup> should be considered a "link" for the purposes of lookup() or not. If it should be considered one, then we should change NameBindingAdd.installLookup() to make lookupLink() return the other value.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira