I faced a similar problem when I was using response.sendRedirect() in ComponentRequestFilter#handlePageRender. I later used response.disableCompression() and it solved my problem.
Still, i believe, npe should be taken care of by the framework. regards Taha On Tue, May 31, 2011 at 10:30 PM, Josh Canfield <joshcanfi...@gmail.com>wrote: > > java.lang.NullPointerException @ > > > org.apache.tapestry5.internal.services.ResponseCompressionAnalyzerImpl.isCompressable(ResponseCompressionAnalyzerImpl.java:65) > > > > Can you provide more of the stack trace? It's strange for the > content-type to be null unless you're doing something with the > response before it get's to the GZIP filter. Can you provide a small > page class/template that reproduces the problem? > > > Josh > > On Mon, May 23, 2011 at 7:32 AM, rorschach > <the.spider.jerusa...@gmail.com> wrote: > > We recently upgraded a big project we're working on to Tapestry 5.2.5. > After > > the upgrade, certain form submits just randomly stopped working. > > > > On clicking submit, we get hit with the following error: > > java.lang.NullPointerException @ > > > org.apache.tapestry5.internal.services.ResponseCompressionAnalyzerImpl.isCompressable(ResponseCompressionAnalyzerImpl.java:65) > > > > That Impl class is trying to find the position of a semicolon in the > content > > type string that gets passed to it, problem is that string is null. > > > > The backend method which receives the form data disassembles it, sets > some > > parameters in an @Inject'ed object and then returns that same object. > > Nothing has changed, other parts of the app that use identical logic work > > just fine. I've compared the request headers of a functioning submit and > the > > broken one, everything is the same. The content type is added, everything > > looks OK. > > > > Weirdest part is that this only happens with Tomcat. I've tried 6.0.24 > (the > > same version as before the upgrade when the app worked fine), 6.0.32 and > > even 7.0.14, fails every time. But when I run the app in Jetty, the > submits > > work perfectly and there are no exceptions. > > > > This is a long shot since it's a really random exception, but maybe > someone > > else has experienced a similar thing or just has an idea how to tackle > this > > problem? > > > > Thanks in advance. > > > > -- > > View this message in context: > http://tapestry.1045711.n5.nabble.com/T5-2-5-NPE-on-form-submit-tp4419202p4419202.html > > Sent from the Tapestry - User mailing list archive at Nabble.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 > >
