Howdy, >The full trace of the root cause is now logged (instead of the full >trace of the exception, which was not very useful IMO). >The new display seems to me significantly easier on users (esp when >using the request dispatcher a lot, which could have created huge stack >traces in the past).
Ahh, that makes more sense now that I've read it twice ;) Thanks. >> Curious: why is log4j not adapted / what's missing from it for this >> use-case? > >Because log4j wasn't with Apache for Tomcat 4.0. Also, I believe TC's >container logger can be configured more easily and consistently with >other components. Got it ;) Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
