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/01/04 08:03:20 UTC
DO NOT REPLY [Bug 5684] -
WEB-INF/lib jar file loading and operations problems.
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=5684>.
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=5684
WEB-INF/lib jar file loading and operations problems.
------- Additional Comments From william.barker@wilshire.com 2002-01-03 23:03 -------
1) This is really a Windows issue, since *nix machines happily let you delete
open files. (and Tomcat delegates which files are open to
java.lang.Classloader).
2) This is a known problem, but it is basically a bug in java.util.zip. (and,
yes, this one effects *nix boxes as well). What happens is that the JVM holds
on to it's old index of the jar file (which is no longer valid of course), so
it is unable to reload the class when Tomcat asks it to. My understanding of
the feeling among the developers is that they'd really rather that Sun fix this
one than re-write java.util.zip.
AFAIK, this is still an issue in Java 1.4 Beta, but I might be wrong.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>