[
https://issues.jboss.org/browse/AS7-5492?page=com.atlassian.jira.plugin.s...
]
James Livingston commented on AS7-5492:
---------------------------------------
Using the example I uploaded, master + your patch from github finds the entry using
lookup() but the listBindings() still doesn't return anything.
The AS 7.1 branch + patch and EAP 6 + patch (applies cleanly to both) causes it to fail to
find anything with lookup() which works without the patch.
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