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

NamingException spec should conform to other chained exception legacies.

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 1.4.2
    • Fix Version/s: 5.0
    • Component/s: core-libs
    • Subcomponent:
    • Resolved In Build:
      tiger
    • CPU:
      sparc
    • OS:
      solaris_9

      Description


      A Chained Exception facility was added to the Throwable class in 1.4
      (see RFE 4209652). This allows an exception to indicate that it was
      thrown due to some other exception. By the time this facility was
      added, a number of exception classes were using ad-hoc solutions to
      the same problem. When 4209652 was integrated most of these ad-hoc
      solutions were brought into line with the new generic facility but --
      probably due to time constraints -- javax.naming.NamingException was not.

      NamingException's behavior is already consistent with the treatment
      given to other legacy classes, so only the javadoc needs to be updated
      for consistency.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              sseligmasunw Scott Seligman (Inactive)
              Reporter:
              sseligmasunw Scott Seligman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: