New release DefaultFileSystemProviders

Michael Hall mik3hall at gmail.com
Wed Aug 4 10:25:39 UTC 2021



> On Aug 4, 2021, at 1:17 AM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
> 
> On 03/08/2021 22:25, Michael Hall wrote:
>> :
>> 
>> I had filed an incident report against my application for these errors when I was asked to verify the security manager on command line fix.
>> Having no simple test case the bug report was just closed as unable to reproduce.
>> If https://bugs.openjdk.java.net/browse/JDK-8263940 <https://bugs.openjdk.java.net/browse/JDK-8263940> is assumed to still cover the current situation that’s fine. Otherwise there is no bug report I know of to track the current errors.
> This is the only outstanding issue that I'm aware of. It requires the java.util.zip.ZipFile implementation to be changed to use the built-in file system provider to read the classes for the custom file system that has been packaged in JAR file and configured to be the default file system provider. That's how the recursive initialization issue arises.
> 
> -Alan

I’ll wait until that is resolved to see if that is the root cause for the issues I see now. They seem to get to there differently but might end up failing the same. 


More information about the nio-dev mailing list