Are you setting an error code to your response? You haven't configured
the filter to handle error dispatches:
<filter-mapping>
<filter-name>app</filter-name>
<url-pattern>/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>ERROR</dispatcher>
</filter-mapping>
Error handling in Jetty and Tomcat differ, see
http://www.cacoethes.co.uk/blog/software/a-tomcat-gotcha for more
info.
Kalle
On Tue, Jan 31, 2012 at 2:50 AM, Brian Long <bl...@annadaletech.com> wrote:
> Hi all,
>
> I'm sure I'm not the first person to experience this issue but can't
> seem to find any answers in the mail archive or on the web. I have an
> ExceptionReport page implementing ExceptionReporter so any nasty
> surprises like NPE's result in a nice and friendly "We experiencing
> technical difficulties" page being presented to the user, this works
> fine in jetty but when I deploy my war file to tomcat 6, the
> exceptions are not caught by the ExceptionReporter and the stacktrace
> is shown to the user?
>
> If anyone know what setting in tomcat needs to change so I can get
> this to work as it does in jetty I appreciate it.
>
> Regards, Brian.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
