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.
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.
- relates to
-
JDK-4722261 Clarification in spec for javax.imageio.FileImageOutputStream
-
- Resolved
-
-
JDK-4984465 (fmt) Additional convenience constructors and minor changes to related ctor spec
-
- Resolved
-