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=15875>. 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=15875 Support global sharing of tag libraries Summary: Support global sharing of tag libraries Product: Tomcat 4 Version: Nightly Build Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Jasper 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Being able to share a tag library globally for all the web applications running under Tomcat is something that is often desirable. Unfortunately, the way to do this currently in Tomcat is more complex than it should be. While the jar files associated with the taglibs to be shared can be "shared" in <tomcat>/shared/lib, the TLD mappings must be defined within the web.xml of every web application that wants to use that shared library. (defining the TLD mappings in <tomcat>/conf/web.xml does not currently work because Jasper only processes TLD mappings in the web.xml of the webapp) JSP 1.2 has simplified the use of tag libraries by supporting the auto discory of TLD mappings in jar files. One simply has to drop the tag-library's jar file at the proper location, and voila... the container will process any TLD contained in these jar files and record the proper mappings. It would really be nice if it were possible to do the same at the container (Tomcat) level. As suggested by Craig, this could be supported in the following way: Extend the "search for TLDs inside a JAR file" algorithm to work its way up the parent class loaders as well. That way, one can simply drop the jar files of tag libraries to be shared into <tomcat>/common/lib and they would be recognized without requiring any TLD mappings in any web.xml. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
