JDK-4722261 : Clarification in spec for javax.imageio.FileImageOutputStream
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.imageio
  • Affected Version: 1.4.0_03
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-07-29
  • Updated: 2017-05-16
  • Resolved: 2003-09-29
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.
Other
5.0 tigerFixed
Related Reports
Relates :  
JDK-4722178 - (spec) Tighten specifications of file-opening constructors
Description
An issue has arisen concerning a 1.4 JCK test that is being run on a licensee system.The licensee wants that JCK test javax_imageio/stream/FileImageOutputStream/Ctor should
 be excluded because of bug #4353929. The reason for this test failing on the licensee's system is  a file and a directory can each have the same name at the same time -- ie they have distinct namespaces, not a single shared namespace.  After a detailed discussion with JCK, javax.imageio Engineering team, Mark Reinhold, it was decided that this is an issue with the spec itself.

Proposed changes for spec are in Tiger release time frame.

The spec for FileImageOutputStream should be changed to something like : 

    @throws FileNotFoundException
    If 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
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b22
14-06-2004
EVALUATION The description is only partially correct as primarily this is related to ambiguities in the java.io.File spec filed as bug 4722178 Specifically there is a difference of interpretation over what the phrase "instead of a regular file" adds in the context of the circumstances java.io APIs might throw FileNotFoundException. This will be a spec clarification only, with no semantic change intended. No spec change is proposed. Nor are code changes needed. Once the spec in java.io.File is clarified, then Image I/O API docs can copy the wording there to adopt the same clarification, and hopefully remove the possibility of future differences of interpretation, whilst accommodating platform differences. This will not affect users of the API, nor change the intent of the specification. ###@###.### 2002-07-29 ============================ Removed reference to directories in the exception documentation. ###@###.### 2003-09-15 ===========================
29-07-2002