AW: AW: Caching with Tomcat 3.2

2001-02-14 Thread Ralph Einfeldt
ust the lack of resources to implement this. > -Ursprüngliche Nachricht- > Von: Rick Roberts [mailto:[EMAIL PROTECTED]] > Gesendet: Donnerstag, 15. Februar 2001 07:52 > An: [EMAIL PROTECTED] > Betreff: Re: AW: Caching with Tomcat 3.2 > > I never used JServ, but

Re: AW: Caching with Tomcat 3.2

2001-02-14 Thread Rick Roberts
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

AW: Caching with Tomcat 3.2

2001-02-14 Thread Ralph Einfeldt
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, b