Referencing JNDI data source: Tomcat 6 vs WebSphere 6.1

Question

Hi,
I've noticed a problem whereby there is a difference in the way I have to specify my JNDI data source depending on the application server I deploy it on.
In Tomcat my code specifies "java:comp/env/DB_NAME" and this works fine.
This doesn't work though in WebSphere and I have to remove the "java:comp/env" prefix to get it to work.
Is there a common solution for this whereby my code/properties can specify the same JNDI value?
Thanks

Answer 1

jwenting wrote:
mycoffee wrote:
ted_hankey wrote:
Hi,
I've noticed a problem whereby there is a difference in the way I have to specify my JNDI data source depending on the application server I deploy it on.
In Tomcat my code specifies "java:comp/env/DB_NAME" and this works fine.
This doesn't work though in WebSphere and I have to remove the "java:comp/env" prefix to get it to work.
Is there a common solution for this whereby my code/properties can specify the same JNDI value?
ThanksShould not be different
wrong. There's nothing in any specification stating that jndi resource names should be identical between platforms.
On weblogic for example it would be jdbc/DB_NAME :)No
Tomcat, websphere or weblogic are not different in that term
The differences are about configuration of the servers. If the servers are configured the same, it should be the same. (Check all the config xml files)
This post is more clear
http://www.theserverside.com/discussions/thread.tss?thread_id=42158
I wrote my code like this
Context intC = new InitialContext();
Context c = (Context )intC.lookup("java:comp/env");
DataSource ds = (DataSource)c.lookup("myDataBase");
con = ds.getConnection();and it works for Tomcat + Websphere (did not try on Weblogic yet but believe it should be OK)