Re: Question about Exception behaviour
- From: poisonrain0@xxxxxxxxx
- Date: 16 Jan 2006 05:04:24 -0800
Hi Chris,
So you are saying that in class Throwable (as i can see it too) it
allows one to set the message and the cause to null, hmmm!
well, here is the stinger... even if it DOES produce odd results in the
stack trace it does have the information of a line of two after it...
Example:
cz.unicorn.afu_v1.af_v1.util_v1.date_v1.test.TestException
at
cz.unicorn.afu_v1.af_v1.util_v1.date_v1.test.ExceptionChainingTest.topLink(ExceptionChainingTest.java:29)
at
cz.unicorn.afu_v1.af_v1.util_v1.date_v1.test.ExceptionChainingTest.main(ExceptionChainingTest.java:19)
BUT if you see the earlier example the last line of the trace is JUST a
"Caused by: java.lang.NullPointerException"
which is very strange... meaning it just appeared with the stack frames
being empty :-) !!
any more ideas...
-U
.
- References:
- Question about Exception behaviour
- From: poisonrain0
- Re: Question about Exception behaviour
- From: Chris Uppal
- Question about Exception behaviour
- Prev by Date: going CRAZY with servlet / xls download on winXP
- Next by Date: Re: Question about Exception behaviour
- Previous by thread: Re: Question about Exception behaviour
- Next by thread: Re: Question about Exception behaviour
- Index(es):
Relevant Pages
|