You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Nick Faiz <ni...@q9software.com> on 2006/02/22 15:01:23 UTC
tapestry and interceptor like things
Hi,
I actually sent this through earlier today but I haven't seen it appear
on the list. If it has appeared twice, I apologize ...
I want to find a way to create a security layer in my application which
I can re-use elsewhere. I've imagined something like an interceptor or a
page event listener
(http://jakarta.apache.org/tapestry/UsersGuide/events.html).
Tapestry doesn't seem to support interceptors. I want to keep my
solution within Tapestry - relying on Tapestry to redirect to various
pages, etc..
Any ideas? Right now it seems as though I have to build all of my logic
into a Page object, but that is hardly a clean solution for code re-use.
Cheers,
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: tapestry and interceptor like things
Posted by Nick Faiz <ni...@q9software.com>.
James - okay, I'll check it out. I can't work on interceptors today but
will probably get back to it tomorrow.
Cheers,
Nick
James Carman wrote:
> Nick,
>
> Tapernate adds a OpenSessionInViewFilter to the WebRequestServicerPipeline
> if you want an example.
>
> -----Original Message-----
> From: Nick Faiz [mailto:nick@q9software.com]
> Sent: Wednesday, February 22, 2006 4:16 PM
> To: Tapestry users
> Subject: Re: tapestry and interceptor like things
>
> James,
>
> Thanks for the pointer - I'm checking it that link now.
>
> Cheers,
> Nick
>
> James Carman wrote:
>
>> Tapestry does include support for "interceptors" via the
>> WebRequestServicerPipeline, I believe.
>>
>>
>>
> http://jakarta.apache.org/tapestry/tapestry/hivedocs/config/tapestry.request
>
>> .WebRequestServicerPipeline.html
>>
>> There's another pipeline for intercepting servlet requests (the Servlet
>>
> API
>
>> directly), but I think you can probably get by with this.
>>
>> -----Original Message-----
>> From: Nick Faiz [mailto:nick@q9software.com]
>> Sent: Wednesday, February 22, 2006 9:01 AM
>> To: Tapestry users
>> Subject: tapestry and interceptor like things
>>
>> Hi,
>>
>> I actually sent this through earlier today but I haven't seen it appear
>> on the list. If it has appeared twice, I apologize ...
>>
>> I want to find a way to create a security layer in my application which
>> I can re-use elsewhere. I've imagined something like an interceptor or a
>> page event listener
>> (http://jakarta.apache.org/tapestry/UsersGuide/events.html).
>>
>> Tapestry doesn't seem to support interceptors. I want to keep my
>> solution within Tapestry - relying on Tapestry to redirect to various
>> pages, etc..
>>
>> Any ideas? Right now it seems as though I have to build all of my logic
>> into a Page object, but that is hardly a clean solution for code re-use.
>>
>> Cheers,
>> Nick
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: tapestry and interceptor like things
Posted by James Carman <ja...@carmanconsulting.com>.
Nick,
Tapernate adds a OpenSessionInViewFilter to the WebRequestServicerPipeline
if you want an example.
-----Original Message-----
From: Nick Faiz [mailto:nick@q9software.com]
Sent: Wednesday, February 22, 2006 4:16 PM
To: Tapestry users
Subject: Re: tapestry and interceptor like things
James,
Thanks for the pointer - I'm checking it that link now.
Cheers,
Nick
James Carman wrote:
> Tapestry does include support for "interceptors" via the
> WebRequestServicerPipeline, I believe.
>
>
http://jakarta.apache.org/tapestry/tapestry/hivedocs/config/tapestry.request
> .WebRequestServicerPipeline.html
>
> There's another pipeline for intercepting servlet requests (the Servlet
API
> directly), but I think you can probably get by with this.
>
> -----Original Message-----
> From: Nick Faiz [mailto:nick@q9software.com]
> Sent: Wednesday, February 22, 2006 9:01 AM
> To: Tapestry users
> Subject: tapestry and interceptor like things
>
> Hi,
>
> I actually sent this through earlier today but I haven't seen it appear
> on the list. If it has appeared twice, I apologize ...
>
> I want to find a way to create a security layer in my application which
> I can re-use elsewhere. I've imagined something like an interceptor or a
> page event listener
> (http://jakarta.apache.org/tapestry/UsersGuide/events.html).
>
> Tapestry doesn't seem to support interceptors. I want to keep my
> solution within Tapestry - relying on Tapestry to redirect to various
> pages, etc..
>
> Any ideas? Right now it seems as though I have to build all of my logic
> into a Page object, but that is hardly a clean solution for code re-use.
>
> Cheers,
> Nick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: tapestry and interceptor like things
Posted by Nick Faiz <ni...@q9software.com>.
James,
Thanks for the pointer - I'm checking it that link now.
Cheers,
Nick
James Carman wrote:
> Tapestry does include support for "interceptors" via the
> WebRequestServicerPipeline, I believe.
>
> http://jakarta.apache.org/tapestry/tapestry/hivedocs/config/tapestry.request
> .WebRequestServicerPipeline.html
>
> There's another pipeline for intercepting servlet requests (the Servlet API
> directly), but I think you can probably get by with this.
>
> -----Original Message-----
> From: Nick Faiz [mailto:nick@q9software.com]
> Sent: Wednesday, February 22, 2006 9:01 AM
> To: Tapestry users
> Subject: tapestry and interceptor like things
>
> Hi,
>
> I actually sent this through earlier today but I haven't seen it appear
> on the list. If it has appeared twice, I apologize ...
>
> I want to find a way to create a security layer in my application which
> I can re-use elsewhere. I've imagined something like an interceptor or a
> page event listener
> (http://jakarta.apache.org/tapestry/UsersGuide/events.html).
>
> Tapestry doesn't seem to support interceptors. I want to keep my
> solution within Tapestry - relying on Tapestry to redirect to various
> pages, etc..
>
> Any ideas? Right now it seems as though I have to build all of my logic
> into a Page object, but that is hardly a clean solution for code re-use.
>
> Cheers,
> Nick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: tapestry and interceptor like things
Posted by James Carman <ja...@carmanconsulting.com>.
Tapestry does include support for "interceptors" via the
WebRequestServicerPipeline, I believe.
http://jakarta.apache.org/tapestry/tapestry/hivedocs/config/tapestry.request
.WebRequestServicerPipeline.html
There's another pipeline for intercepting servlet requests (the Servlet API
directly), but I think you can probably get by with this.
-----Original Message-----
From: Nick Faiz [mailto:nick@q9software.com]
Sent: Wednesday, February 22, 2006 9:01 AM
To: Tapestry users
Subject: tapestry and interceptor like things
Hi,
I actually sent this through earlier today but I haven't seen it appear
on the list. If it has appeared twice, I apologize ...
I want to find a way to create a security layer in my application which
I can re-use elsewhere. I've imagined something like an interceptor or a
page event listener
(http://jakarta.apache.org/tapestry/UsersGuide/events.html).
Tapestry doesn't seem to support interceptors. I want to keep my
solution within Tapestry - relying on Tapestry to redirect to various
pages, etc..
Any ideas? Right now it seems as though I have to build all of my logic
into a Page object, but that is hardly a clean solution for code re-use.
Cheers,
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org