Looks like your suggestion does work for one servlet.
Not sure whether its scalable enough of a solution for me though.
The root cause of the problem is that tapestry doesn't deal with the outside
servlets
and gives up its processing pipeline. Its more of a design issue on my side
now of how to
On Thu, 08 Sep 2011 14:17:59 -0300, Lenny Primak
wrote:
This relates to my battle with securing servlets with tap-security /
shiro.
I found out that because tapestry 'ignores' my outside servlets
(REST/WebServices) security information isn't getting propagated.
If I could just let tapestr
This has to do with my security battle.
I figured out that the security information isn't getting propagated because
servlet falls 'outside' of the tapestry domain and is just getting ignored by
the
tapestry servlet filter and the whole pipeline.
I need to get all these servlets into the filter pi
> this will require me to 'wrap' all the servlets individually,
Hmm... well originally you said you only had the one servlet! :)
> I have a servlet which I need to use as part of the Tapestry web app.
In what way do you need the servlet to be "in the pipeline"?? If you
just need access to servic
If I understand you correctly Thiago,
this will require me to 'wrap' all the servlets individually, i.e.
the tapestry part would have to know about all the servlets,
which isn't desirable. Or am I missing something?
On Sep 8, 2011, at 12:43 PM, Lenny Primak wrote:
> no but I will try :)
>
> On
no but I will try :)
On Sep 8, 2011, at 12:41 PM, Thiago H. de Paula Figueiredo wrote:
> On Thu, 08 Sep 2011 13:39:41 -0300, Lenny Primak
> wrote:
>
>> I have a servlet which I need to use as part of the Tapestry web app.
>> Since it's not an asset, etc. Tapestry completely ignores it.
>> Is t
On Thu, 08 Sep 2011 13:39:41 -0300, Lenny Primak
wrote:
I have a servlet which I need to use as part of the Tapestry web app.
Since it's not an asset, etc. Tapestry completely ignores it.
Is there any way to add it to the pipeline?
Have you tried wrapping it in a HttpServletRequestFilter an
I have a servlet which I need to use as part of the Tapestry web app.
Since it's not an asset, etc. Tapestry completely ignores it.
Is there any way to add it to the pipeline?
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.
