tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Remy Maucherat <r...@betaversion.org>
Subject Re: Servlet Re-loading in TC4
Date Tue, 01 May 2001 18:35:37 GMT
Quoting Martijn Koster <mak@greenhills.co.uk>:

> On Tue, May 01, 2001 at 11:41:00AM +0100, Kevin Jones wrote:
> 
> > The log says
> > 
> > StandardLoader[/AddressBook]: Reloading checks are enabled for this
> Context
> > 
> > but re-loading doesn't (appear) to work.
> 
> Same problem here. The mailing list archives show others experience it
> too. I've appended a test which shows what's going on with the
> HelloWorld example.
> 
> The StandardClassLoader.findClass successfully loaded the servlet
> class from a "jndi:" URL, and then tried to convert that to a File so
> it can track modification dates. That file can't be found, and is
> therefore not cached, and therefore not tracked by modified(). You
> can't just convert a JNDI to a File pathname like that, AFAIK.
> 
> It seems to me that to support reloading StandardClassLoader should
> either use URLs and URLConnections only to load classes and track
> modification dates (not explicit File's), or else that the jndi URL
> should somehow be resolved into a file URL. At the very least
> findClass() could spot non-file URLs and not bother to do the File
> conversion, and instead log the fact that this repository cannot be
> tracked for modification to reduce recurring confusion.

Yes, I think that's probably the problem here. I'll implement the changes and 
see if it helps.

> But being completely new to Tomcat I may be completely off the mark,
> and certainly won't claim to know the right solution. :-) Can anyone
> enlighten us?

Remy

Mime
View raw message