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.
