[
https://issues.jboss.org/browse/AS7-6121?page=com.atlassian.jira.plugin.s...
]
Eduardo Martins commented on AS7-6121:
--------------------------------------
This feature was designed to bind a msc service that provides "jndi lookup of X"
as a managed value. When changed the managed value to a linkref, which is only
dereferenced when doing a JNDI lookup, injection of the msc bind service, for instance as
a dependency, injects the linkref itself, since it does not uses JNDI at all.
Now its a fact that the lookup subsystem op also creates a link, since it binds this
"lookup of x" into JNDI, and this is possibly where we could do a change, by
instead having a separated subsystem op (for instance "link") to bind link
refs.
I need to look carefully to all the usages of the current feature before proposing
anything at all.
Naming subsystem <lookup> could use LinkRef/Reference
-----------------------------------------------------
Key: AS7-6121
URL:
https://issues.jboss.org/browse/AS7-6121
Project: Application Server 7
Issue Type: Feature Request
Components: Naming
Affects Versions: 7.1.3.Final (EAP)
Reporter: James Livingston
Assignee: Eduardo Martins
Fix For: 7.2.0.Alpha1
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