tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 11485] - Jasper2 caches tag library descriptors too long
Date Mon, 26 Aug 2002 22:39:48 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11485>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Jasper2 caches tag library descriptors too long





------- Additional Comments From kin-man.chung@sun.com  2002-08-26 22:39 -------
The problem is not with caching of TLD's or tag handler classes, because they
are not cached.  The problem is that the page that uses the modified TLD or tag
handler is not recompiled.  TLD, and indirectly the tag handlers are only
processed at translation time, and when they change, the page that uses them
need to be recompiled.  This is because the codes that are generated for the JSP
page depends on the properties of the tag handlers and would become invalid when
the tag handlers are modified.  This is analogous to class dependency in Java:
if Foo references Bar and Bar.java is modified, then Foo.java needs to be
recompiled, otherwise you'll get a ClassChangedException at runtime.

The simple workaround in this case is to either touch the JSP page or remove its
.class file, just to force a recompilation of that page.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message