Good thing, that's one way to set things up and I've used it myself
but it only goes half way. The even better idea (if I say so myself)
is to use Tynamo's (and in the future core Tapestry)
tapestry-exceptionpage module for mapping exceptions directly to error
pages (see http://tynamo.org/tapestry-
Hi Kalle,
yes I managed finally track down the answer after searching through
pages of search results, unfortunately my original search query
included the terms "tomcat", "tapestry" and "error" which produces
reams of result (most of them irrelevant)!
Like you mentioned in your reply I needed to
Are you setting an error code to your response? You haven't configured
the filter to handle error dispatches:
app
/*
REQUEST
ERROR
Error handling in Jetty and Tomcat differ, see
http://www.cacoethes.co.uk/blog/softwa
