Directly adding a tapestry url also works <error-page> <error-code>404</error-code> <location>/NotFound.html</location> </error-page>
That was in T4 that used the servlet (instead of filter) approach... perhaps it also works in T5. On Mon, May 19, 2008 at 5:35 PM, Toby Hobson <[EMAIL PROTECTED]> wrote: > Given that a JSP is basically a servlet, why not do something like > > <% > response.include(request.getContextPath() + "/MyTapestryErrorPage); > %> > > from your jsp exception page > > btw I can't remember - can you map an exception handler to a servlet in > web.xml? > > Toby > > ----- Original Message ---- > From: Thiago HP <[EMAIL PROTECTED]> > To: Tapestry users <users@tapestry.apache.org> > Sent: Monday, 19 May, 2008 2:52:02 PM > Subject: Re: T5: Exception Handling > > On 5/19/08, Peter Stavrinides <[EMAIL PROTECTED]> wrote: >> To configure: >> You would simply use a standard JSP / HTML error page, and wire it in your >> web.xml. I am using Tomcat and it works great... works on Jetty too. > > Something I've done once is to setup a 404.html page that redirects to > a Tapestry page via Javascript, including the original URL so I can > log it. ;) > > -- > Thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
