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:31 ------- By "private logging system" I meant "not ServletContext.log()". It should not be necessary to do extra configuration to struts for the stacktrace to be passed to tomcat along with an HTTP status code. When tomcat's error screen reports an error, I go to the tomcat log file to find the stacktrace - it's the most logical thing to do. If the struts or the jsp error catching mechanism catches the error and prints me a pretty page, then I can expect the stack trace to go wherever the struts or jsp error catching mechanism wants it. The present behaviour is completely illogical and should be changed. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
