On Fri, 15 Mar 2013 07:02:47 -0300, Muhammad Gelbana <m.gelb...@gmail.com>
wrote:
I'm having trouble *understanding and knowing* what needs to be done.
I've seen deroke's metro web-services integration but it seems to be
designed
for filters and not servlets. I understand that should not be a huge
difference since you define the url pattern for either the
patter\servlet. But I have some questions like, if it's all about the
url pattern
specification, why should i direct tapestry to contribute a http request
filter ? is it only to be able to access tapestry's registry through the
servlet context ? (i.e. What I very much need to do)
Exactly. Anything you do inside the Tapestry framework has the advantage
of using it. If you write a servlet filter or a servlet, the most you can
do is to get the Registry from the ServletContext and use it.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
