Which part do you mis then?
because the root isn't cut of:
sb.append("Root cause:\n\n");
outputThrowable(cause, sb, false); << false is don't stop at
wicket servlet.
all other causes do stop at the wicket servlet (but those are mostly just
invocation target and so on)
for all we just skip the: !(traceString.startsWith("sun.reflect.")
so that we don't have all those reflection stacks in it that don't give you
any information then you already had.
johan
On 5/30/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
while i like shorter stack traces in some sense, i've run into a couple of
cases where the stack trace being shown by wicket cut out important
information. could we review the code in Strings.toString(Throwable) to
make sure we're really doing the right thing here? i'd rather have too
much
stack trace information from wicket than lose a key piece of info at a
critical time. unless we can feel really sure we're not cutting out
important information, i think we ought to err on the safe side.
--
View this message in context:
http://www.nabble.com/abbreviated-stack-traces-tf3837742.html#a10866083
Sent from the Wicket - Dev mailing list archive at Nabble.com.
