Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4227544

design bug: File.mkdir(), etc. don't provide reason for failure

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Won't Fix
    • Icon: P4 P4
    • None
    • 1.2.0
    • core-libs
    • generic
    • generic



      Name: vi73552 Date: 04/07/99


      There is a problem in the design of several methods of
      java.io.File. Specifically, methods such as mkdir don't
      return any indication of why they failed if they fail.

      This means that a calling program has no further information
      to use to take corrective action or to report to the user.

      If something like mkdir() fails, there should be a reason
      (e.g., already exists, some parent directory does not exist,
      general IO error, IO permissions error (something other than
      the existing SecurityException case)).

      In that case, mkdir() should return information about the reason
      (e.g., by throwing an exception whose class and message and/or
      data contents carry that information).


      DSB/DFI
      (Review ID: 56635)
      ======================================================================

            mmcclosksunw Michael Mccloskey (Inactive)
            vasya Vassili Igouchkine (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: