Fix AS7-5492. Make JNDI listBindings() work with multiple NamingStores.

[doctau]

This is a small fix for AS7-5492, by making listChildren() return items from the ServiceRegistry too.

Potential performance concerns:

1. It iterates through the entire contents of the registry. I don't see a way of fixing that without adding additional ServiceRegistry API to either get partial contents or to notify the store of changes.
2. It checks whether entries are in the child list when adding which is O(n^2) in the number of items from the registry. It would be O(n) to use an IdentityHashMap as a set, but probably not worth it since the number of entries is likely to be small. Reversing the order of adding to be registry then boundServices may be better (though then n^2 in the number of boundServices matches)

[wildfly-ci]

Triggering build using a merge of 6685a8c on branch master:
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/

[wildfly-ci]

Build 3839 is now running using a merge of 6685a8c on branch master:
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/3839

[wildfly-ci]

Build 3839 outcome was FAILURE using a merge of 6685a8c on branch master:
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/3839

[doctau]

Is that just an intermittent test failure?

java.util.concurrent.TimeoutException
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:228)
at java.util.concurrent.FutureTask.get(FutureTask.java:91)
at org.jboss.as.test.integration.common.HttpRequest.execute(HttpRequest.java:49)
at org.jboss.as.test.integration.common.HttpRequest.get(HttpRequest.java:79)
at org.jboss.as.test.integration.jaxrs.async.JaxrsAsyncTestCase.performCall(JaxrsAsyncTestCase.java:66)
at org.jboss.as.test.integration.jaxrs.async.JaxrsAsyncTestCase.testJaxRsWithNoApplication(JaxrsAsyncTestCase.java:71)

[kabir]

Retest this please!

[wildfly-ci]

Triggering build using a merge of 6685a8c on branch master:
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/

[wildfly-ci]

Build 3849 is now running using a merge of 6685a8c on branch master:
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/3849

[wildfly-ci]

Build 3849 outcome was SUCCESS using a merge of 6685a8c on branch master:
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/3849

[n1hility]

We need to find another way to address this problem. This solution doesn't work for all cases and as you mention it's going to be terribly slow.

[stuartwdouglas]

I have addressed this a different way in #3026.