JDK-6873681 : (file) Re-examine Path.checkAccess
- Type: Bug
- Component: core-libs
- Sub-Component: java.nio
- Affected Version: 7
- Priority: P4
- Status: Closed
- Resolution: Duplicate
- OS: generic
- CPU: generic
- Submitted: 2009-08-19
- Updated: 2010-12-10
- Resolved: 2010-12-10
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 7 |
|---|
7Resolved  |
Related Reports
|
Duplicate :
|
Description
The checkAccess method is currently very awkward to use, requiring applications to catch an exception for the case that access is denied, or some other I/O error occurs. Some developers have suggested methods equivalent to File's canXXX methods but they are problematic too because checking access can fail for many reasons. In addition to re-examining this method, the spec for the exists/notExists method should be changed to not require the implementation use checkAccess.
Comments
|