Affects Version/s: 1.0
Fix Version/s: None
Component/s: core / taglib.core
JellyException has some built-in support for nested exceptions. In particular, when it displays a stack trace, it tries to also displays the nested exception, which is great.
What's not so great is that when JDK 1.4 added this on its own, both Jelly and JDK try to display the nested exceptions, and you ended up seeing O(n^2) stack traces for n-level nested exception.
Imagine a situation where N JellyExceptions are nested inside each other.
With the following current printStackTrace:
Outer JellyException prints its stack trace first (in which JDK prints out all the nested exceptions),
and then JellyException prints the stack trace of the inner JellyException. Then this same step is repeatedly, causing an output like this:
See the attached patch for one possible fix.
Personally, I don't mind if JellyException choose to completely stop trying to print out the nested exception on its own, and simply delegate everything to JDK. This will make the output worse on JDK 1.3 and earlier, but the # of people using those is shrinking every day.