[jboss-jira] [JBoss JIRA] (AS7-5492) JNDI listBindings() does not work for items in java:jboss/exported

[James Livingston (JIRA)]

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

James Livingston updated AS7-5492:
----------------------------------

    Attachment: BindJndiDemo.java


It doesn't seem to for me. Attached is the customer's test class. To use it you need to bind abc/def into the exported JNDI and then run "java -cp $JBOSS_HOME/bin/client/jboss-client.jar BindJndiDemo  remote://127.0.0.1:4447"



<subsystem xmlns="urn:jboss:domain:naming:1.2">
  <bindings>
    <simple name="java:jboss/exported/abc/def" value="Hello"/>
  </bindings>
  <remote-naming/>
</subsystem>


It should print out one line after the "NamingEnumeration object" one, containing the JNDI entry.
                
> 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