Fw: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5390

[Bill Barker <wb...@wilshire.com>]

I was never really involved in the 3.2.x development, so I'm sending back to
the list to try and get ideas on how to get 3.3 to act more like 3.2.x in
the deprecated case.
----- Original Message -----
From: <mi...@ds808.net>
To: "Bill Barker" <wi...@wilshire.com>
Sent: Friday, January 04, 2002 7:39 PM
Subject: Re: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5390


> Yea... sort of works but nothing like 3.2.3.  The classes that have been
> called previously are still alive but any uncalled classes in the jar are
> dead (404 error).  And a restart (remove, add) of the context will kill
off
> all the classes in the jar (404 error).  Still not a viable solution.
>
> Regards,
> Mike
>
>
> ----- Original Message -----
> From: "Bill Barker" <wb...@wilshire.com>
> To: <mi...@ds808.net>
> Sent: Friday, January 04, 2002 3:11 PM
> Subject: Re: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5390
>
>
> The same hack is actually available (at least in theory, I've never tried
> it).  If you set fullReload="false" in the ReloadInterceptor element of
> server.xml, you are supposed to get the 3.2.x reload behavior.  The
default
> fullReload="true" is supposed to be cleaner (and is much if you only use
> classes) since it throws away the app-ClassLoader and re-loads everything
on
> a brand new one.  With the 3.2.x fullReload="false", classes that have
been
> loaded are just re-fetched from the ClassLoader (no jar reading involved).
>



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>