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/06 02:27:30 UTC
DO NOT REPLY [Bug 11485] New: -
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
Summary: Jasper2 caches tag library descriptors too long
Product: Tomcat 4
Version: 4.1.8
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Jasper 2
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: craig.mcclanahan@sun.com
Using either 4.1.7 or 4.1.8 beta releases, I can do the following:
* Deploy an app with a custom tag library
* Successfully use tags from the library in a JSP page
* Add a new tag to the TLD (and corresponding tag class to the webapp)
* Update a JSP page in the webapp to use the new tag
* Reload the webapp (or remove/install, it makes no difference)
* Navigate to the page using the new tag
* Get a compile error stating that the new tag does not exist
in the tag library
This problem doesn't go away until Tomcat is restarted, which implies that the
TLDs are being cached beyond the lifetime of the webapp that declared them.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>