You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/08/26 23:27:02 UTC

DO NOT REPLY [Bug 11485] - Jasper2 caches tag library descriptors too long

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

kin-man.chung@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME



------- Additional Comments From kin-man.chung@sun.com  2002-08-26 21:27 -------
Craig,

If the tld mapping is defined in web.xml, and the mapping is changed, then
tomcat needs to be restarted; but that's because any change in web.xml requires
a restart of tomcat for it to take effect.  However, if web.xml is not modified,
or if the tld is specified in uri attribute of the taglib directive, then any
change in tld, as well as any change in the tag handlers referenced there, will
take effect when the page is recompiled.  Jasper only caches the tld mappings
defined in web.xml, and never the tlds themselves.  I have verified that with
some simple examples.

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