The actual error reported is caused by what looks like a defect: java.lang.NullPointerException org.apache.tapestry5.internal.services.assets.CompressionAnalyzerImpl.isCompressable
The code: public boolean isCompressable(String contentType) { assert contentType != null; int x = contentType.indexOf(';'); ... The assertion here is not helpful when you get a null contentType passed in... I'm going to change this to return false if contentType == null. Josh On Tue, Jan 10, 2012 at 8:22 AM, Howard Lewis Ship <hls...@gmail.com> wrote: > 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 > <stephan.windmuel...@tu-dortmund.de> 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: 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