DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20302>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20302 DispatchAction catches an exception, then throws it away [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2003-05-29 14:14 ------- If DispatchAction (or any code) encounters an exception which results in it returning an error status to the container (eg 400 Internal Server Error), then the corresponding exception should be written to the container's log file using ServletContext.log(), not Struts' private logging mechanism. In short, if I see an error message with "tomcat error message blah" in it, then I expect to see the corresponding stack trace logged in the tomcat log file. You don't throw an error message to mechanism A (tomcat) and then log the stacktrace to mechanism B (log factory), that's just silly. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
