SAXException *still* doesn't do the proper exception chaining, masking the root
cause of the problem.

Add the following method to SAXException:

public Throwable getCause() {
    return exception;
}
Posted Date : 2009-02-24 17:36:22.0

public class SAXExceptionExt  extends SAXException {
    private Exception exception;
    public SAXExceptionExt(Exception e) {
        super(e);
        exception = e;
    }
    public Throwable getCause() {
        return exception;
    }


}

SAXException should implement getCause in order to do the proper exception chaining.
Posted Date : 2009-02-26 20:01:20.0

Hi,

I think this change has broken the behaviour. We have a test case which does the following:

        Exception cause = new Exception();
        SAXException e = new SAXException("A SAX exception");
        e.initCause(cause);
        assertSame(cause, e.getCause());

Using 6u14 this now fails because initCause(Throwable t); is not overriden in SAXException. 

Taking a step back though, why do you need to store the Exception in SAXException? Why can you not simply delegate all calls to Throwable? I see no logic that SAXException adds on top of Throwable (aside from the breaks)