Replacing default FileSystemProvider

Michael Hall mik3hall at gmail.com
Sun Mar 28 23:50:50 UTC 2021



> On Mar 28, 2021, at 11:40 AM, Michael Hall <mik3hall at gmail.com> wrote:
> 
> 
> 
>> On Mar 28, 2021, at 10:17 AM, Alan Bateman <Alan.Bateman at oracle.com <mailto:Alan.Bateman at oracle.com>> wrote:
>> 
>>> 
>> 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.
>> 

Exactly correct about inconsisten wrapping . About half the methods for my Path class that returned Path’s directly returned the platform ones and about half returned ones where I wrapped the returned as my class. I changed to wrap all returned Path’s and the test and my application work. 

So I have a version of the application that fully replaces com.apple.eio.FileManager including functionionality from my DefaultFileSystemProvider. The application requires some changes after jpackage puts it together to include the exploded classes as per earlier. 

I will try to figure that out and maybe add a little code that further utilizes the DefaultFileSystemProvider. But working more or less as I intended the 5 or 6 years ago. 





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


More information about the nio-dev mailing list