-
Bug
-
Resolution: Fixed
-
P2
-
1.4.2, 6u10
-
b86
-
generic, x86, sparc, itanium
-
generic, linux, solaris_8
If the user has a file and a symlink, e.g.:
/home/user/data/file.txt
/data -> /home/user/data,
and wants to select the file through that symlink, he can't browse there,
because the JFileChooser will convert /data to /home/user/data
There are legitimate uses for the need to get the user selected symlink
instead of the canonical path to the target, example:
The selected path may be persisted between app sessions and the user may need
to change the target of the symlink (different version of a library, some VCS uses symlinks for paths to latest valid bits, ...)
File.getCanonical* calls are not apparently made from JFileChooser itself, nor from FileSystemView, but are made from various FileChooserUI subclasses.
###@###.### 2004-07-21
- duplicates
-
JDK-4893175 JCK1.4a-runtime api/javax_swing/JFileChooser/descriptions.html#CtorNew failed
-
- Closed
-
-
JDK-5077426 symbolic link support for JFileChooser
-
- Closed
-
- relates to
-
JDK-2191571 4906607 is not fixed for NIMBUS L&F
-
- Closed
-
-
JDK-4615460 Enhancements to Swing/JFileChooser for IDE tools
-
- Closed
-
-
JDK-6358641 File.getNormalized{File,Path}() which does not traverse symlinks unlike getCanonical{File,Path}()
-
- Closed
-
-
JDK-4199911 JFileChooser.setCurrentDirectory(file) sets dir to canonical path
-
- Resolved
-
-
JDK-6938481 4906607 is not fixed for NIMBUS L&F
-
- Closed
-