[ http://issues.apache.org/jira/browse/BEEHIVE-757?page=all ] Alejandro Ramirez closed BEEHIVE-757: -------------------------------------
Verified Fixed. Executed the repro steps and now the user is sent to the Tomcat error page. I also executed the tests with sharedflows catching Exception.class instead of the pageflow. The same results was observed (the tomcat error page is displayed instead of the 503 error page). > 503 error when @Jpf.Catch forwards to an error page with a compile error in it > ------------------------------------------------------------------------------ > > Key: BEEHIVE-757 > URL: http://issues.apache.org/jira/browse/BEEHIVE-757 > Project: Beehive > Type: Bug > Components: NetUI > Versions: v1m1 > Environment: Tomcat 5.0.25 > Reporter: Rich Feit > Assignee: Alejandro Ramirez > Fix For: V1 > Attachments: j757.zip > > Repro: > - Add the attached page flow to a Beehive webapp, build, and hit > /foo/Controller.jpf. > - Click the 'throwException' link. > EXPECTED: a Tomcat error page for the IllegalStateException thrown from the > page. > ACTUAL: a 503 error returned to the browser; the original exception is > nowhere to be found, in the logs or on the console. > This only happens when the JSP's page flow has a @Jpf.Catch with > type=Exception.class. There's an infinite loop happening, where the page > exception is getting caught by the @Jpf.Catch, which re-forwards to the error > page. The 503 is the Page Flow framework's decision to break out of the > string of forwards when some threshold is reached (25 by default). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
