In Tapestry, Request abstracts away from either a HttpServletRequest or
a PortletRequest (not implemented yet). So to make your application work
in both a Portlet and a Servlet context, you have to use the Request.
But since you have to get hold of the HttpServletRequest you are
nevertheless stuck to a Servlet context and it doesn't matter whether
you write a HttpServletRequestFilter, a RequestFilter (and inject the
HttpServletRequest) or a Dispatcher (and inject the HttpServletRequest).
Just choose one.
Uli
Andrey Larionov schrieb:
It's not a hack, but RequestFilters services Request not an HttpServletRequest.
On Thu, Aug 20, 2009 at 19:15, Thiago H. de Paula
Figueiredo<thiag...@gmail.com> wrote:
Em Thu, 20 Aug 2009 11:54:02 -0300, Andrey Larionov <anlario...@gmail.com>
escreveu:
Thanks. I decide to try HttpServletRequestFilter, couse injecting
HttpServletRequest in Dispatcher or RequestFilter looks like a hack.
I don't consider it a hack (injecting services into services is absolutely
normal in Tapestry and Tapestry-IoC), but an HttpServletRequestFilter is a
valid choice too.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
