The java:/ namespace can only be accessed inside
the same virtual machine.
kind of defeats the purpose of JNDI, doesn't it? (remote lookups of common services)
Do you want to bind your datasource into the global
namespace, retrieve a connection from a pool and then
send it over the network?
Isn't it better to have a local pool?
Also, depending upon your config, your datasource could
give insecure access to the database.
These considerations are the purpose of the java:/
I see your point, and in a production environment, the ideal would be to have datasources only accessible from
the JBoss VM.
I got started on this because I want to test JDBC connectivity. I just installed a MySQL driver, so I wrote a client program to get a connection from the pool using a DataSource, to see if the driver works. The java: namespace is preventing me from doing this test.
Can I temporarily bind my data source into the global
namespace? I could find no documentation on this in the
PDF manual I bought online.