You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2002/09/20 20:49:34 UTC
DO NOT REPLY [Bug 12872] New: -
ForwardAction doesn't play nice with Declarative Exception Handling
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=12872>.
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=12872
ForwardAction doesn't play nice with Declarative Exception Handling
Summary: ForwardAction doesn't play nice with Declarative
Exception Handling
Product: Struts
Version: 1.1 Beta 2
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Standard Actions
AssignedTo: struts-dev@jakarta.apache.org
ReportedBy: beskrowni@alumni.cmu.edu
Suppose you have a generic global exception configured to catch
java.lang.Exception. Now suppose you are using
org.apache.struts.actions.ForwardAction to forward to a jsp, say page.jsp. Now
suppose there is an compilation error in page.jsp, then the container (at least
this is what we're seeing with wls 6.1) will try to display an error page with
the jsp compilation messages immediately. Also, ForwardAction catches the
exception thrown and tries to forward to the configured error page, but it
can't because the response has already been committed.
The only solution I can think of would be to have ForwardAction swallow any
exceptions that get thrown when it attempts to forward.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>