I never used JServ, but I didn't think that it ever handled .jsp at all!!!
I'm just stating the obvious, but, there is a big difference in when .jsp's
get compiled compared to servlets.
Rick
On Thu, 15 Feb 2001, you wrote:
> It's not the jsp file that has to know if an underlying class
> has changed, it's the classloader of the servlet engine.
>
> Good old jserv was able to recognize changes in beans and
> classes if the classes where found through it's classloader.
> If the class was in the classpath it was not reloaded, because
> the jserv classloader only loaded classes if they couldn't be
> found through the claspath. (jserv had something like an
> alternate classpath called repositories to find those classes)
>
> > -----Urspr�ngliche Nachricht-----
> > Von: Rick Roberts [mailto:[EMAIL PROTECTED]]
> > Gesendet: Donnerstag, 15. Februar 2001 06:29
> > An: [EMAIL PROTECTED]
> > Betreff: Re: Caching with Tomcat 3.2
>
> <snip/>
>
> > The .jsp file can't know that you have recompiled a bean or a
> > java class that it is referencing.
>
> <snip/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
