Il giorno 19/ago/05, alle 16:03, Sylvain Wallez ha scritto:
Well, standard is the way to go as we can't assume everybody will want
to deploy Xalan just to have error pages.
Hmmm, I have a better idea, inspired once again by the Orbeon folks
(don't whine, it was you who pointed to
http://www.orbeon.com/blog/2005/08/16/ops-stack-traces/ first ;-) ).
Why don't we modify the Exception generator so that, instead of
outputting the Java stacktrace as a text, we do a getStackTrace on the
exception, traverse the returned array of StackTraceElement's and for
each one we output a <ex:stackTraceElement> having <ex:className>,
<ex:methoName>, etc. as children?
This would give us much more flexibility in presenting stacktraces,
without having to convert newlines into <br>s and such silliness.
Only problem, Throwable.getStackTrace was introduced in 1.4, AFAIK. So
we could do this for trunk only, unless there's another method to get
to the same info.
Ugo
--
Ugo Cei
Tech Blog: http://agylen.com/
Open Source Zone: http://oszone.org/
Wine & Food Blog: http://www.divinocibo.it/
