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=14854>. 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=14854 Allow redeploying tag libraries from the same jar, do not lock the jar files on Windows Summary: Allow redeploying tag libraries from the same jar, do not lock the jar files on Windows Product: Tomcat 5 Version: Nightly Build Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Jasper2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] There are two separate but related problems: When Jasper loads .tld files from the tag library jar files, it does not close the jar files. Because of this, the file can not be deleted/overwritten on Windows, which causes pain when developing the application (and frequent changes are desirable). When using Jasper inside Catalina, then a workaround is to stop the application using the manager application (or stop the server, but that does not help the speed of the development cycle). However, when Jasper is used outside the server as a standalone embedded application, then there is no workaround. The second problem is that Jasper uses the caches in JarURLConnection, which means that one .tld can not be redeployed from the same jar. A simple fix is to call connection.setUseCaches(false), which now in JDK 1.4 finally works. Another minor issue in class TldLocationsCache is the fact that it does not always close the .tld file stream, which seems strange. I don't see any reason why not to close the stream. The following patch may not be a complete solution to all these problems, but it goes in that direction. Please consider applying it. Thanks. Petr -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
