-Original Message-
From: Leon Palermo [mailto:[EMAIL PROTECTED]]
Sent: 01 November 2000 18:05
To: [EMAIL PROTECTED]
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
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
Forgot to mention, I'm using Tomcat
3.2beta6.
- 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
classpath
I can control this. How would you control it otherwise?
Bill Pfeiffer
- Original Message -
From:
Raghu Havaldar
To: '[EMAIL PROTECTED]'
Sent: Wednesday, November 01, 2000 10:42
AM
Subject: RE: jar's still not picked up in
WEB-INF/lib
I
think u misread
I unpacked a jar file in the WEB-INF classes
directory. It had a servlet and another class
called by the servlet. The servlet could be run
okay, but when the servlet tried to use the other
class, it was not found. Are you saying that if I
leave the classes in the jar and put the jar in
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
W
not picked up in WEB-INF/lib
I unpacked a jar file in the WEB-INF classes
directory. It had a servlet and another class
called by the servlet. The servlet could be run
okay, but when the servlet tried to use the other
class, it was not found. Are you saying that if I
leave the classes
