It sounds like your legacy application is using JNDI for connection pooling(not really a legacy model). I do not believe you are able to define a JNDI Resource in your server.xml file and not have the file located in your %CATALINA%\common\lib folder.
It really sounds like you are trying to include duplicate libraries (in the WEB-INF\lib and %CATALINA%\common\lib) which isn't a good practice. I think you just have configuration problem in your use of Jbuilder. Try looking for a CLASSPATH setting in JBuilder, and add your libraries to this CLASSPATH, so you don't have to include them in the WEB-INF\lib folder. - Andrew -----Original Message----- From: Iain Downie [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 12:35 PM To: Tomcat Users List Subject: Library problem (and JBuilder/Tomcat issue?) Dear list, I have inherited a legacy application, which uses DataSources defined within the server.xml of Tomcat 4 connecting to a database. To get the basic system working, I first create a .war in JBuilder6Pro on my PC, then FTP the .war, and then use manager to deploy correctly on my remote linux server. Problem - there seems to be a bug in Tomcat 4 that won't allow any libraries to be contained in the application WEB-INF when it is deployed. To compile the application and classes etc. properly in JBuilder, I need them. JBuilder will not access the database correctly through Tomcat4 at runtime within JBuilder, but it does compile OK. However, once deployed I have to manually delete them from WEB-INF (ensuring they are all still present in the Tomcat/common/lib folder) and explicitly refer to the datasource in the web.xml with 'java:comp/env/jdbc/myApplication' instead of just 'jdbc/myApplication' - no other permutation seems to work. However, given that JBuilder is supposed to be a powerful testing/development environment, I want to get it set up so that I can use Datasources to connect to Oracle. I know that there are many other ways to do this (QuerySets etc. in JBuilder), and the tutorials show you how, but I need to work around this legacy system which makes these other ways impossible. Has anyone ever encountered this similar problem, and might suggest a good way of configuring the whole process? Regards Iain -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
