Re: Tomcat vs Weblogic JNDI Lookup

2008-09-07 Thread Luther Baker
The * was just a wildcard for the example. Fill it in with whatever you like. Let's say we have a datasource named appds So code deployed to WEBLOGIC can do this: context.lookup(appds); While code deployed to TOMCAT must do this: context.lookup(java:comp/env/jdbc/appds); That is my

Tomcat vs Weblogic JNDI Lookup

2008-09-06 Thread Luther Baker
The Weblogic servers we are using have been configured to allow JNDI datasource names like appds. For development (localhost), we might be running Tomcat and when declared in the context section of server.xml, Tomcat will hang JNDI datasources on java:comp/env/jdbc/* in the JNDI tree. *Problem:*