Ok, this list-lurker is confused...
I thought there was something documented about classes not reloading
similiar to what was mentioned below (I can't get to jakarta.apache.org
at the moment and verify).
Maybe I'm behind on the powercurve : )
So reloading should work fine whether you use tomcat standalone and in
conjunction with other webservers (in particular apache) due to the same
AdaptiveClassLoader that is used from Jserv.
thanks!
P.S. Yes I did download 3.1 and run some tests and everything worked
fine, a little assurance though would make me feel better!
-------- Original Message --------
Subject: Re: what happens to sessions?
Date: Thu, 11 May 2000 15:56:04 -0700
From: Costin Manolache <costin@costin.dnt.ro>
Reply-To: tomcat-dev@jakarta.apache.org
To: tomcat-dev@jakarta.apache.org
References: <200005112158.e4BLwGG14785@clearink.com>
<391B3238.8CBB5E6F@eng.sun.com>
> > What happens, in Tomcat, to session objects that have been created by a
> > servlet after a classloader reload?
> >
> > I just spent about 30 minutes trying to find what happens in the code, but
> > it is so badly documented I can't figure it out. :-(
> >
>
> Last time I looked at that particular piece of code, that was the conclusion I
> came to as well.
>
> There are other flaws in the current implementation of auto-reload in Tomcat
> 3.1 -- for example, it only checks for changes to servlet classes, not any
> other classes.
That's not true. We use the AdaptiveClassLoader from JServ and it does
check all the classes, not only the servlet.
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
|