Having users write to jar files that are in use by a JDK is one of the most common sources of JDK crashes. There's a long history of bugs open in the bug database. Windows doesn't have this problem -- they have the opposite problem of locking jar files in use so that they cannot be updated.
Fixing this would require hooking into the OS file modification notification mechanism; not easy; how to abort a class load in progress? Martin On Mon, May 12, 2008 at 9:47 PM, Peter B. Kessler <[EMAIL PROTECTED]> wrote: > Does the Java platform do anything to prevent files from changing > out from under it? E.g., once one has opened a jar file for class > loading, could a malicious (or oblivious) user write to the jar > file and disturb the VM? Or is that all relegated to "the operating > system", file system permissions, etc.? > > ... peter >
