-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
9
-
x86
-
os_x
A DESCRIPTION OF THE REQUEST :
In moving the contributed legacy Apple code to JDK 9. That is the...
com.apple.eawt
com.apple.eio
packages. Where the only class in com.apple.eio is FileManager.
They were placed in the java.desktop module.
JEP 272 was to integrate these into new java.awt.Desktop api's.
This was done and dealt completely with the com.apple.eawt code. It did not address com.apple.eio.FileManager.
My own use of this code involves determining platform specific locations for application data. As desktop platforms for different operating systems get more security conscience and more particular in what desktop applications can and can't do, including where they can store and access data. It becomes more important for applications to be able to do this correctly in a platform specific way.
This code was generally available for use for Mac applications for some time. I can't speak to what other use cases it may of been put to by others. So I can't cherry pick what functionality from the FileManager class should or should not be supported.
My request is that the status of this code, com.apple.eio.FileManager be resolved in some manner.
Ways this could be done.
1). Fully incorporate it somehow into java.desktop. Meaning to my understanding somewhere in java.awt.
2). Find a more proper place for it elsewhere. core-libs/java.nio was suggested by Phil Race.
3). Discontinue support completely. Remove it from the java.desktop module. Leave it up to the user community to continue support.
JUSTIFICATION :
Existing Mac application may be using this API. One use case was already mentioned. In it's current form it is pretty much unusable.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Access to the api's in some way or the ability to set up access outside the jdk.
ACTUAL -
It isn't available in jdk api's or once it is eliminated even from Runtime in any way.
---------- BEGIN SOURCE ----------
It is JDK included.
---------- END SOURCE ----------
CUSTOMER SUBMITTED WORKAROUND :
For now I believe the api is available runtime, or if someone has access to the source they can provide it themselves.
In moving the contributed legacy Apple code to JDK 9. That is the...
com.apple.eawt
com.apple.eio
packages. Where the only class in com.apple.eio is FileManager.
They were placed in the java.desktop module.
JEP 272 was to integrate these into new java.awt.Desktop api's.
This was done and dealt completely with the com.apple.eawt code. It did not address com.apple.eio.FileManager.
My own use of this code involves determining platform specific locations for application data. As desktop platforms for different operating systems get more security conscience and more particular in what desktop applications can and can't do, including where they can store and access data. It becomes more important for applications to be able to do this correctly in a platform specific way.
This code was generally available for use for Mac applications for some time. I can't speak to what other use cases it may of been put to by others. So I can't cherry pick what functionality from the FileManager class should or should not be supported.
My request is that the status of this code, com.apple.eio.FileManager be resolved in some manner.
Ways this could be done.
1). Fully incorporate it somehow into java.desktop. Meaning to my understanding somewhere in java.awt.
2). Find a more proper place for it elsewhere. core-libs/java.nio was suggested by Phil Race.
3). Discontinue support completely. Remove it from the java.desktop module. Leave it up to the user community to continue support.
JUSTIFICATION :
Existing Mac application may be using this API. One use case was already mentioned. In it's current form it is pretty much unusable.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Access to the api's in some way or the ability to set up access outside the jdk.
ACTUAL -
It isn't available in jdk api's or once it is eliminated even from Runtime in any way.
---------- BEGIN SOURCE ----------
It is JDK included.
---------- END SOURCE ----------
CUSTOMER SUBMITTED WORKAROUND :
For now I believe the api is available runtime, or if someone has access to the source they can provide it themselves.
- duplicates
-
JDK-8168762 com.apple.eio.FileManager replacements missing
-
- Closed
-