The Xalan-J trace options also aren't portable, their output tends to be a bit verbose, and it's hard to see from the messages exactly what part of the output was produced where.

Now we'll add a bit of complexity by accessing the stack trace of an exception.

That trace output is getting a bit wordy, isn't it?