on 11/22/99 1:04 PM, David Medinets <[EMAIL PROTECTED]> wrote:
>
> I'm probably misinterpreting what I'm seeing, but when using Jakarta/
> Tomcat v2.2 the changed class isn't being reloaded.
No, that is different. If you execute a servlet in Tomcat and then change
that servlet and recompile it, it will not currently get reloaded. This is
because it doesn't have a custom classloader and a system that knows how to
create a new CL each time classes change. This is something that we have
perfected in Apache JServ 1.1, but have not yet ported over to Tomcat. It is
definitely on the TODO list, we were just talking about this the other day
in fact.
If you have a servlet that calls class.forName().newInstance() on some other
code and you recompile that other code and re-execute your servlet, that
other code will display the changes because the old instance is GC'd.
-jon
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
