I've been trying to get the JNDI browser for eclipse to connect to NS support over JNP without any luck. did you have to do anything special to get it to work? What JNDI browser are you using?
You can browse bindings through the web-based jmx-console provided with JBoss.
At the main page, you can select "service=JNDIView", and then invoke the list function to list JNDI definitions that JBoss knows about.
You can also look at the ConnectionFactory under jboss.management.local on the main page.
Hope that is serviceable enough for your needs.
I am using JNDI Browser 1.0.1 by EJTools.org
I am not using Eclipse.
I downloaded the file from sourceforge.net and just followed the installation instructions. There were some files I could not find but thats ok. Just added jbossall-client.jar instead of some files mentioned for jboss in the installation steps.
Besides that didnt have to do extra to get it working.
Hope that helps is you are looking for a non-eclipse solution.
My guess is that this jndi browser is running in a different vm than jboss, so it will not be able to see anything in the java:/ context, including any datasource. You can see them in jndi-view from the jmx console since that is running in the jboss vm.
jonlee, thanks for the tip. I found it in the 3.0.2 docs on page 132...thanks!
rshinde, thanks for the reference. I was missing the jbossall-client.jar file. I had mistakenly used jboss.jar (which in hindsight was silly). I also added the jboss-jmx.jar from the lib directory to get the javax/management classes that were needed.
David, unfortunately, as you pointed out, I was not able to see anything in the java:/ context since i wasn't running in the same JVM--much like the EJTools software which only allows you to see if you use the Web version.
I'm curious if this will be fixed when Remote JMX is available? What is the source of this limitation?
Thanks again for both of your suggestions.
Well, I'm not really a jndi expert, but my understanding of the purpose of the java: namespace is that it should not be accessible to other vms. Therefore I would regard anything that allowed direct lookups in the java: namespace from another vm as a critical bug. I would expect this to prevent any tool that uses only jndi protocols and runs in another vm from ever, under any circumstances, being able to see the java: context.
If you are willing to use non-jndi protocols there is nothing stopping you today from using the jmx rmi connector to get the xml list view from the jndiview mbean and parsing however you see fit for display, or writing something such as an mbean that runs in the jboss vm and produces whatever view of the jndi tree you like.