I thought of using the location tag, but I couldn't get it to work...
it appeared as though Tapestry couldn't resolve the resource from the
response and throws a 404 not found instead.
Howard Lewis Ship wrote:
Chances are, Tapestry is passing on the requests because there are
real static HTML
Hi
I would like to customize the various error pages for my servlet
(404,500,401 etc...), I have implemented the configuration in my
web.xml, but Tapestry 5 doesn't pick them up... how should I go about this?
Thanks
Peter
-
On a related note, I'd like to send 404 responses as well as a custom
error page through T5, like when a user or article isn't found (but
requested by id, for example). I remember a thread about this I think...
Peter Stavrinides wrote:
Hi
I would like to customize the various error pages for
Chances are, Tapestry is passing on the requests because there are
real static HTML files present.
The problem is that if you delete 505.html, you need to come up with a
class named 505. That's going to be a problem :-).
I'm not sure what the servlet container will do if you configure the
Isn't T5 acting as a filter? So if Tomcat/etc hands control to T5 to
find the correct resource/page, T5 has the opportunity to handle
things like error messages. Is it out of the question for Tapestry to
provide base error pages that we can override, or configure Tapestry
to pass errors back to
