title: Websphere Name Space Bindings affect the JNDI scope resolution order
body: <p>Here is the situation:</p>
  
  <p>I'm on websphere Network Deployment v8.0.0.3 
  I've an application which use 2 queuese
  One Queue is for internal application usage (Publisher and Consumer are inside the same application) the other queue is used by other modules deployed on Other application server inside the cell.</p>
  
  <p>So I have configured the 1st queue at Cell Scope level and the second queue at Cluster scope level.</p>
  
  <p>Everything was working until I added a Name Space Binding.
  After that every jms jndi object Cluster Scoped are not present anymore inside a dumpNameSpace.sh output.</p>
  
  <p>Seams like the resolution of the scopes are modified by the presence of a Name Space Binding.
  Which indeed is really odd but I got the same behaviour on 2 different installations of WAS.</p>
  
  <p>Thanks for anyone which knows this.</p>
  
  <p><strong>Update</strong></p>
  
  <p>This is the diff between the jndi dump that works and the one which not.</p>
  
  <pre><code>--- clsdumpOk   2012-08-07 11:49:43.000000000 +0200
  +++ clsdumpKo2  2012-08-07 11:49:59.000000000 +0200
  @@ -454,28 +454,12 @@
   (top)/clusters/TestCluster/jdbc/modulobase
   (top)/clusters/TestCluster/jms
   (top)/clusters/TestCluster/jms/as
  -(top)/clusters/TestCluster/jms/as/BatchRequest
  -(top)/clusters/TestCluster/jms/as/BatchResponse
   (top)/clusters/TestCluster/jms/as/ciccio
  -(top)/clusters/TestCluster/jms/as/FSCleaner
   (top)/clusters/TestCluster/jms/as/License
   (top)/clusters/TestCluster/jms/as/Mailer
  -(top)/clusters/TestCluster/jms/as/Plans
  -(top)/clusters/TestCluster/jms/as/RiaResponse
  -(top)/clusters/TestCluster/jms/ConnectionFactory
  -(top)/clusters/TestCluster/jms/pac
  -(top)/clusters/TestCluster/jms/pac/as
  -(top)/clusters/TestCluster/jms/pac/as/Events
   (top)/clusters/TestCluster/jms/queue
  -(top)/clusters/TestCluster/jms/queue/batch-request
  -(top)/clusters/TestCluster/jms/queue/batch-response
  -(top)/clusters/TestCluster/jms/QueueConnectionFactory
  -(top)/clusters/TestCluster/jms/queue/events
  -(top)/clusters/TestCluster/jms/queue/filesystem-cleaner
   (top)/clusters/TestCluster/jms/queue/license
   (top)/clusters/TestCluster/jms/queue/mailer
  -(top)/clusters/TestCluster/jms/queue/plans
  -(top)/clusters/TestCluster/jms/TopicConnectionFactory
   (top)/clusters/TestCluster/jta
   (top)/clusters/TestCluster/jta/usertransaction
   (top)/clusters/TestCluster/SecurityServer
  @@ -495,8 +479,10 @@
   (top)/clusters/TestCluster/url/casCfgFile
   (top)/clusters/TestCluster/UserRegistry
   (top)/clusters/TestCluster/wb25
  -(top)/clusters/TestCluster/wb25/topic
  -(top)/clusters/TestCluster/wb25/topic/ria-response
  +(top)/clusters/TestCluster/wb25/conf
  +(top)/clusters/TestCluster/wb25/conf/locking
  +(top)/clusters/TestCluster/wb25/conf/locking/lockingEnabled
  +(top)/clusters/TestCluster/wb25/conf/rootFolder
   (top)/clusters/TestCluster/wm
   (top)/clusters/TestCluster/wm/ard
   (top)/clusters/TestCluster/wm/default
  </code></pre>
  
  <p>as you can see once the </p>
  
  <p>+(top)/clusters/TestCluster/wb25/conf/locking/lockingEnabled</p>
  
  <p>is added</p>
  
  <p>all the rest is removed.
  It's really weird.</p>