The way exceptions are dealt with in Tapestry is 'second to none!' ... one of the frameworks best features imho, see this page: http://tapestry.apache.org/tapestry5/tapestry-core/guide/event.html
There are many ways to handle exceptions, you choose whats best for you, what I am doing is using a base page with a single onException(Throwable e), which keeps my pages very clean, and ensures I don't rewrite error handling over and over. cheers, Peter ----- Original Message ----- From: "Moritz Gmelin" <moritz.gme...@gmx.de> To: "Tapestry users" <users@tapestry.apache.org> Sent: Monday, 15 June, 2009 14:53:53 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Redirect from Exception Page (with Tomcat) in 5.1 Hi, I'd like to have all Exception of my Application handled by its special ExceptionReport in the way that on the production system the ExceptionReport directly redirects the user to the start page. This works well using Jetty as AppServer and checking for the error reason in beginRender and then sending a redirect. Using Tomcat this fails and brings a Tomcat 500 error message java.lang.RuntimeException: Page ExceptionReport did not generate any markup when rendered. This could be because its template file could not be located, or because a render phase method in the page prevented rendering. The Error did not appear in T5.0.18. So how can I realize such a redirect from the ExceptionReport page (which does not get through onActivate) using T5.1 and Tomcat? Thanks Moritz --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
