Replacing default FileSystemProvider

[Alan Bateman]

On 28/03/2021 15:44, Michael Hall wrote:
>
> Simple reproducing test case…
>
> import org.apache.hc.client5.http.impl.classic.HttpClientBuilder;
> import org.apache.hc.client5.http.impl.classic.CloseableHttpClient;
>
> public class TestREST {
>
>
> public static void main(String[] args) {
> try (CloseableHttpClient client = HttpClientBuilder.create().build();) {
> }
> catch (ClassCastException cce) {
> System.out.println("as cce");
> cce.printStackTrace();
> }
> catch (java.io.IOException ioex) {
> System.out.println("as ioex");
> }
> }
> }
>
My guess is that this CCE is due to somewhere in the custom file system 
provider that isn't wrapping or unwrapping consistently. I've run 
several tests based on the TestProvider that I linked to and I couldn't 
duplicate the issue.

The SO post that you linked to seems to be something else. The 
cryptographic jurisdiction policy defaults to "unlimited" since JDK 9 so 
I wouldn't expect any issues there, unless conf/security/java.security 
has been changed to set crypto.policy to "limited" and I doubt that is 
the case.

-Alan.
||
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/nio-dev/attachments/20210328/d1f3a425/attachment-0001.htm>