[jboss-jira] [JBoss JIRA] (AS7-5492) JNDI listBindings() does not work for items in java:jboss/exported
[
https://issues.jboss.org/browse/AS7-5492?page=com.atlassian.jira.plugin.s...
]
James Livingston commented on AS7-5492:
---------------------------------------
Thinking about it more, even if that fixes the issue with exported JNDI entries, there
still seems to be an issue with lookup() and list/listBindings() not being consistent.
With ServiceBasedNamingStore, you can successfully lookup entries that are not in the
return value from the list* methods. Should that be possible? Regardless of which
particular store instance you have, things in the service registery can only be accessed
if you know the name and never found by walking the tree.
JNDI listBindings() does not work for items in java:jboss/exported
------------------------------------------------------------------
Key: AS7-5492
URL: https://issues.jboss.org/browse/AS7-5492
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: James Livingston
Assignee: Stuart Douglas
Attachments: BindJndiDemo.java
When an object is bound to java:jboss/exported/abc/def (for example using the naming
subsystem in standalone.xml), it can be retrieved from a remote client with
context.lookup("abc/def").
Calling context.listBindings("abc") return 0 bindings. This appears to be
because ServiceBasedNamingStore.lookup() checks the service registry and then the
boundServices, but listBindings() only checks the boundServices.
--
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