Right noticed that. The TapestryFilter is all about final methods. I currently use a request handler and borrow ideas from cometd implementation :)
2013/8/16 Thiago H de Paula Figueiredo <thiag...@gmail.com> > On Fri, 16 Aug 2013 12:22:57 -0300, Martin Kersten < > martin.kersten...@gmail.com> wrote: > > Lance currently I go with extending the TapestryFilter and bend it >> together with AtmosphereServlet30. If I get some results I post it here. If >> it is >> working I will make a blog post and donate the code. Maybe we find a more >> transparent way, then. Fingers crossed. >> > > I suggest you to implement it as Tapestry HttpServletRequestFilter filter > instead. This way, you can use all the existing Tapestry infrastructure and > you don't need to juggle Tapestry-controlled and non-Tapestry-controlled > stuff. > > > -- > Thiago H. de Paula Figueiredo > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > > For additional commands, e-mail: users-h...@tapestry.apache.org > >
