I noticed that the CascadingException class does not currently print out
the stack
trace of the nested cause along with the stack trace of the
CascadingException.
It seems like it would be a lot more useful if it did. I am including
the patch and
can submit it if there are no objections, but I wanted to make sure that
there
wasn't a reason why this shouldn't be done first.
Cheers,
Leif
RCS file:
/home/cvs/jakarta-avalon/src/java/org/apache/avalon/framework/CascadingException.java,v
retrieving revision 1.3
diff -r1.3 CascadingException.java
9a10,12
> import java.io.PrintStream;
> import java.io.PrintWriter;
>
51a55,72
> }
>
> public final void printStackTrace()
> {
> super.printStackTrace();
> System.out.print( ExceptionUtil.printStackTrace( m_throwable, 8, true ) );
> }
>
> public final void printStackTrace( PrintStream stream )
> {
> super.printStackTrace( stream );
> stream.print( ExceptionUtil.printStackTrace( m_throwable, 8, true ) );
> }
>
> public final void printStackTrace( PrintWriter writer )
> {
> super.printStackTrace( writer );
> writer.print( ExceptionUtil.printStackTrace( m_throwable, 8, true ) );
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
