Order counts; your filter needs to be ordered after Tapestry's "ErrorFilter" contribution; otherwise, there's nothing to catch the exception and report it.
On Tue, Jan 10, 2012 at 1:10 AM, Stephan Windmüller <[email protected]> wrote: > Am 10.01.2012 09:51, schrieb Stephan Windmüller: > >> In the AppModule class we defined a custom component transaction >> filter. When this filter throws an exception, it is not rendered with >> the exception report page, instead we are getting this stacktrace: > > Forgot to mention: We are using Tapestry 5.3.1. > > - Stephan > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
