tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Remy Maucherat <>
Subject Re: What's about unloading policy of jsp-servlets ?
Date Sat, 04 Mar 2006 10:25:40 GMT
Costin Manolache wrote:
> Thanks for the patch...
> This is a well known problem, JSPs are not unloaded unless the entire
> webapp is unloaded. And to make things worse - by default all JSP
> static content is compiled to strings, that take all the memory. I
> think we have ( or had ) an option to generate some non .class file -
> which could be more easily managed.
> Unfortunately I'm not familiar enough with jasper code - but it looks
> good to me. The model of keeping the entire jsp static content in
> memory forever is IMO very broken... It may help cheat on some
> benchmarks ( i.e. jsp versus html, etc ), but it's wrong for real
> world.

Huh ? This is nonsense. JSPs, until further notice, are servlets. As a 
result, why should they have unloding strategies and similar nonsense ?

Strong -1: I will veto any attempt to fix this "issue".


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message