Return-Path: <R.Riley@lse.ac.uk>
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 63670 invoked from network); 6 Dec 2000 17:24:04 -0000
Received: from eximc-1.lse.ac.uk (158.143.100.31)
  by locus.apache.org with SMTP; 6 Dec 2000 17:24:04 -0000
Received: by eximc-1.lse.ac.uk with Internet Mail Service (5.5.2448.0)
	id <Y29L6K0C>; Wed, 6 Dec 2000 17:23:30 -0000
Message-ID: <C43AC8B3315CD211846000609457C7BB03A8E0A4@exchf3.lse.ac.uk>
From: "Riley,R" <R.Riley@lse.ac.uk>
To: "'tomcat-user@jakarta.apache.org'" <tomcat-user@jakarta.apache.org>
Subject: RE: New class definition not being picked up
Date: Wed, 6 Dec 2000 17:23:28 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

Andreas

Thanks for responding.  

I've done everything that you suggest (except upgrade) and still have the
same result.

I'll try re-installing tomcat.

Regards

Ron

> -----Original Message-----
> From:	Stubenrauch,Andreas [SMTP:mex02@erv.de]
> Sent:	Wednesday, 06 December 2000 16:25
> To:	'tomcat-user@jakarta.apache.org'
> Subject:	RE: New class definition not being picked up
> 
> You have to put your .jar files in the appropriate
> webapps/yourcontext/WEB-INF/lib directory
> automatic reload only works in this directory. Further more they must not
> be
> 
> set in your classpath.
> 
> BTW: I recommend upgrading to Tomcat 3.2
> 
> Regards,
> Andreas
> 
> > -----Original Message-----
> > From: Riley,R [mailto:R.Riley@lse.ac.uk]
> > Sent: Wednesday, December 06, 2000 3:53 PM
> > To: 'tomcat-user@jakarta.apache.org'
> > Subject: New class definition not being picked up
> > 
> > 
> > Hi
> > 
> > I'm new to tomcat, so sorry if this is an obvious one - I've 
> > searched the
> > archive.
> > 
> > Using tomcat 3.1 on redhat linux with jdk1.3.
> > 
> > All of my java classes are in .jar files in a separate 'jars' 
> > directory.
> > Each of the jar files is listed in the class path.
> > 
> > Everything worked fine until I replaced one of the class 
> > files in one of the
> > jars.  If the browser page source is to be believed then the new class
> > definition is not being picked up by tomcat.  Somehow tomcat 
> > continues to
> > use the prevous class after running shutdown.sh and startup.sh.
> > 
> > I've de-compiled the class in the jar file to ensure that it 
> > is the correct
> > (new) one.  If I remove the .jar file then tomcat can't find 
> > the classes in
> > that jar, and throws an error, but when I replace the jar 
> > file, with one
> > including the new class,  then then the original class continues to be
> > used(!).
> > 
> > I've ensured that the browser isn't using a cached copy of an 
> > old page.
> > 
> > I'd be really pleased to hear from anyone who has any ideas 
> > about this.
> > 
> > Many thanks
> > 
> > Ron Riley
> >