Re: jar's still not picked up in WEB-INF/lib

[Bill Pfeiffer]

Leon,   I added a "context" into the server and it found my jars.  But, careful what you ask for, the ordering ends up being important.  I had to go back to using the classpath to make sure that the jars are hit in the proper order.  Oh well.   BTW, my reply below was based on my having misread Raghu's response.  I incorrectly thought he was talking about not using the WEB_INF\lib dir.   Unzipping my clashing jars would not bode well.  Problem is that my app talks to more than 1 app server and the jar arrangement is precarious at best.  Some of the same, slightly different, packages included in client jars from the app server vendors.  One classpath ordering works, the other doesn't.   Bill P. ----- Original Message ----- From: Leon Palermo To: [EMAIL PROTECTED] Sent: Wednesday, November 01, 2000 1:05 PM Subject: Re: jar's still not picked up in WEB-INF/lib I agree that you should not put application specific jar files in the main $TOMCAT/lib directory because the jar files should reside with their application.  I was saying, as a last resort try putting the jars in the main TOMCAT lib.  Did you try it?   I always just unzip any zip files in the WEB-INF/classes directory or you could make your own jar file of those classes.   -Leon  ----- Original Message ----- From: Bill Pfeiffer To: [EMAIL PROTECTED] Sent: Wednesday, November 01, 2000 10:28 AM Subject: Re: jar's still not picked up in WEB-INF/lib Aside from the fact that it does not work in certain situations, why would you think it is not a good idea to put your app specific libs under the WEB-INF\lib directory.    The spec says to do it.  It allows for good application orginization.  What would be your arguments against it?   Actually I can think of one argument against it, and that is that by including your libs in the classpath instead, you can control the order of the classpath.  It appears that using the libs directory would allow for random ordering (based on OS directory ordering) of these libs.  Also, I need to include zip files and these don't get picked up anyway.  Maybe using the classpath is the way to go.   Bill Pfeiffer   ----- Original Message ----- From: Raghu Havaldar To: '[EMAIL PROTECTED]' Sent: Wednesday, November 01, 2000 9:34 AM Subject: RE: jar's still not picked up in WEB-INF/lib The Context setup is for the web-app.   I do not think it is a good idea to put app-depedent libs under $TOMCAT/lib.   Just for experimentation, I tried placing the JARs under $TOMCAT/lib and $TOMCAT/webapps/web-inf/lib.  Does not work.   Tried with 3.1 and 3.2beta6 on WinNT 4.0.   -raghu -----Original Message----- From: Leon Palermo [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 7:31 AM To: [EMAIL PROTECTED] Subject: Re: jar's still not picked up in WEB-INF/lib I would definitely set up a context in server.xml like this:   <Context path="/Oasis"  docBase="webapps/Oasis"  debug="0"  reloadable="true" > </Context>   That should solve you problem.  Otherwise, just put the .jar files in the D:\Java\jakarta-tomcat\lib directory.  Then the jars would be available for all applications served by tomcat.   Leon Palermo Zedak Corporation Valhalla, NY ----- Original Message ----- From: Bill Pfeiffer To: Tomcat Sent: Wednesday, November 01, 2000 8:13 AM Subject: Re: jar's still not picked up in WEB-INF/lib I am experiencing the same problem that others have reported on this topic.  I explicitly set my Tomcat classpath to be sure of no redundancies in the jars.  I have a Tomcat startup batch file with one line that adds in all the jars in my WEB-INF\lib to the classpath explicitly.  When I comment that line out, I get the classnotfound errors.  When I put it back in, my web app runs fine.  Obviosly I want the line commented out and have the jars picked up in the lib dir, but that aint happening.   Because the jars work when explicitly included in the classpath, I conclude that the jars are not corrupt.  I also conclude, based on commenting out the explicit lib jars classpath, that there are not redundant jars in the classpath.  I have also checked other sources for possible classpath jar redundancies and I am just not finding any.    I am running under Win2000 using jdk1.3.    These is the exact dir structure I have set up:   D:\Java\jakarta-tomcat\webapps D:\Java\jakarta-tomcat\webapps\Oasis D:\Java\jakarta-tomcat\webapps\Oasis\jsp D:\Java\jakarta-tomcat\webapps\Oasis\META-INF D:\Java\jakarta-tomcat\webapps\Oasis\resources D:\Java\jakarta-tomcat\webapps\Oasis\WEB-INF D:\Java\jakarta-tomcat\webapps\Oasis\WEB-INF\classes D:\Java\jakarta-tomcat\webapps\Oasis\WEB-INF\lib   I have gone through Craig McClanahans list of things to check and all seems to be as it should.   Any hope for a fix?  Should I continue to look at my config?  I have heard some people talk about setting up an explicit context for the app in the server.xml.  Does this solve the problem consistantly?     TIA,   Bill Pfeiffer