JDK-6385694 : SAXException doesn't handle exception nesting
  • Type: Enhancement
  • Component: xml
  • Sub-Component: org.xml.sax
  • Affected Version: 5.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-02-14
  • Updated: 2020-08-04
  • Resolved: 2020-08-04
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
tbdFixed
Related Reports
Relates :  
JDK-6385749 - XMLStreamException doesn't handle exception nesting correctly.
Relates :  
JDK-6857903 - SAXException.initCause() does not correctly set Exception
Description
SAXException can take a nested exception, but it doesn't implement the getCause method, so it doesn't participate in the exception nesting mechanism introduced in JDK 1.4.

Because of this, when one prints out "e.printStackTrace()", it doesn't show exceptions nested inside SAXException.
Comments
Fixed by JDK-6857903.
04-08-2020
EVALUATION Norm Walsh: "The SAX developers have agreed to do it, but not fast enough for JAXP 1.4, alas. (They also claim it's not 100% backwards compatible, so I'm reluctant to do it in 1.4 before they do.)" this will be JAXP.next feature.
15-03-2006
EVALUATION this will require a small CCC request?
14-02-2006
SUGGESTED FIX Please add public Throwable getCause() { return exception; }
14-02-2006