JCE Verifier - a bug in the Java Docs?

Question

When implementing a new JCE Provider, one should follow the special docs, such as http://java.sun.com/j2se/1.4.2/docs/guide/security/jce/HowToImplAJCEProvider.html
In the section "Creating a JarFile Referring to the JAR File", there's this code snippet proposed to get the jar to verify:
// Always get a fresh copy, so we don't have to
// worry about the stale file handle when the
// cached jar is closed by some other application.
conn.setUseCaches(false);
jf = conn.getJarFile();
My question: is it still necessary to switch off using the jar caches before trying to get the file? My impression is that this is related to the old bug 4271671 which is a duplicate of 4211817 which has been closed four years ago (see:http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4211817) . Isn't this just some leftover from those times in the documentation?
This is an issue for us as switching the cache off forces the Java Plugin to always download a fresh copy of an applet jar during the initiation phase, thus slowing down the applet start time very considerably, especially over slow lines.
Thanks everybody!

Answer 1

When implementing a new JCE Provider, one should follow the special docs, such as http://java.sun.com/j2se/1.4.2/docs/guide/security/jce/HowToImplAJCEProvider.html
In the section "Creating a JarFile Referring to the JAR File", there's this code snippet proposed to get the jar to verify:
// Always get a fresh copy, so we don't have to
// worry about the stale file handle when the
// cached jar is closed by some other application.
conn.setUseCaches(false);
jf = conn.getJarFile();
My question: is it still necessary to switch off using the jar caches before trying to get the file? My impression is that this is related to the old bug 4271671 which is a duplicate of 4211817 which has been closed four years ago (see:http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4211817) . Isn't this just some leftover from those times in the documentation?
This is an issue for us as switching the cache off forces the Java Plugin to always download a fresh copy of an applet jar during the initiation phase, thus slowing down the applet start time very considerably, especially over slow lines.
Thanks everybody!