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=7059>. 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=7059 Jasper compiler holds pointers to jars in WEB-INF/lib: cannot delete ------- Additional Comments From [EMAIL PROTECTED] 2002-03-15 22:25 ------- Adding a jarFile.close() on each use of the jar file fails for the two watchdog tests because jarFile is residing on a temp directory after its first use, apparently as a result of caching by VM, and subsequent code such as JarURLConnection conn = (JarURLConnection) url.openConnection(); jarFile = conn.getJarFile(); is not reopening the jar file, but merely getting the cached version, and if that's already closed, would get an "zip file closed" exception when it is accessed. Turned out adding a "conn.setUseCaches(false);" fixes this problem, and the two watchdog failures now pass. So my compiler has both "conn.setUseCaches(false);" and "jarFile.close();", and one should be able to replace .jar files now. However, the tag handler class that was loaded by the class loader remain loaded, and replacing a jar file would not force the class loader to reload it, so I don't think it solves the original requirement for redeploying and reloading of web applications. But that is another issue, right? I wonder if there is any value in committing my "fixes". -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
