I’ve noticed that both ways of looking up a DataSource using JNDI work:
- jdbc/DataSource
- java:comp/env/jdbc/DataSource
With the added bonus that the first one doesn’t seem to anger Websphere when used from an unmanaged thread ( started by Quartz ).
Are there any pitfalls from accessing JNDI objects without the prefix?
This should be OK, since
java:comp/envis the global JNDI namespace.It may depend on the application server where such configurations also appear in the JNDI tree.
Locate your JDBC DataSource in WebSphere Application Server using JNDI