On Thu, 15 Jul 2010 10:56:03 -0300, Adam Zimowski <zimowsk...@gmail.com>
wrote:
So I *could* do it like this with Tapestry by extending Tapestry's
filter, but that's not in the spirit of Tapestry. Furthermore, the
framework is famous for making things amazingly simple. I think I'm
missing something. What is it?
You can implement a HttpServletRequestFilter and contribute it to the
HttpServletRequestHandler service. It's basically a servlet filter, but
inside the Tapestry infrastructure. All requests, even the ones not
handled by Tapestry, are passed to it. If you want to intercept just
Tapestry-handled events, implement a RequestFilter instead.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
