JDK-4722178 : (spec) Tighten specifications of file-opening constructors
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.io
  • Affected Version: 1.4.0_03
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-07-29
  • Updated: 2017-05-16
  • Resolved: 2003-12-19
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 Availabitlity Release.

To download the current JDK release, click here.
Other
5.0 b32Fixed
Related Reports
Relates :  
Relates :  
Description
The current specifications of the RandomAccessFile constructors are ambiguous
with respect to what should happen if the given String or File object names
both a file and a directory.  This is possible on some operating systems, such
as VMS, in which files and directories have their own name spaces.

The specification should be revised to say something like:

  @throws FileNotFoundException
  If the mode is <tt>"r"</tt> but the given file object does not denote an
  existing regular file, or if the mode begins with <tt>"rw"</tt> but the
  given file object does not denote an existing, writable regular file and a
  new regular file of that name cannot be created, or if some other error
  occurs while opening or creating the file

Similar changes should be made, if needed, to the File{In,Out}putStream
constructors.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger tiger-beta FIXED IN: tiger-beta INTEGRATED IN: tiger-b32 tiger-beta
2004-06-14

EVALUATION We'll do this in Tiger. -- ###@###.### 2002/7/30
196-10-07 0