I feel like I have to go on record and say I know how exceptions are chained, I was just missing it completely. That's what happens when you work late. You wind up archived looking silly on google forever ;)
On 1/29/07, Curt Cox <curtcox@xxxxxxxxx> wrote:
What compatibility issues did you have in mind? The strings produced
by a stack trace have varied from release to release, platform to
platform, and probably from vendor to vendor. As I read it, the RFE
wouldn't change the API introduced in
1.4.
Just for the record, some rare ThrowableS don't allow causes.
On 1/29/07, Kohsuke Kawaguchi <Kohsuke.Kawaguchi@xxxxxxx> wrote:
> Jesse Glick wrote:
> > Eric Crahen wrote:
> >> I should have known from the InvocationTargetException type..
> >
> > Actually, any kind of Throwable can have an attached cause, so in
> > general you need to scroll down to check for "Caused by:" lines.
> >
> > FWIW, I have an RFE for Java to display nested stack traces in a more
> > natural order:
> >
> > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6507809
>
> Your RFE makes sense, but I suspect changing it now is nearly impossible
> given the compatibility and all...
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems
kohsuke.kawaguchi@xxxxxxx
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@xxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxxxxx
--
- Eric
| 