You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/01/27 20:22:59 UTC
[jira] Closed: (TAP5-476) Have a common handler/filter pipeline for
both component event and page render requests, to make it easier to add
filters that apply to both types of requests
[ https://issues.apache.org/jira/browse/TAP5-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-476.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.0
> Have a common handler/filter pipeline for both component event and page render requests, to make it easier to add filters that apply to both types of requests
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-476
> URL: https://issues.apache.org/jira/browse/TAP5-476
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.1.0.0
>
>
> Currently, if you want to put a filter in place that afects both types of request, you have to a contribute a ComponentEventRequestFilter to the ComponentEventRequestHandler service, and a nearly identical PageRenderRequestFilter to the PageRenderRequestHandler service.
> It would be nice if there was a service that acted as a facade around the two existing pipelines. The terminator of that pipeline could forward the request into one of the two existing pipelines.
> The common example of this is a "is logged in" filter that sends a redirect if the user is not logged in; you want to do this for both types of requests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Closed: (TAP5-476) Have a common handler/filter pipeline
for both component event and page render requests, to make it easier to add
filters that apply to both types of requests
Posted by Massimo Lusetti <ml...@gmail.com>.
On Wed, Jan 28, 2009 at 1:57 PM, Ulrich Stärk <ul...@spielviel.de> wrote:
> Howard,
>
> could you please explain to me how the two pipelines work and how to add
> filters to them and also how to use this new facade service? I couldn't find
> any documentation on them and the "is logged in" scenario you are aiming at
> seems so common that it should be documented somewhere...
>
Almost a shameless plug but... Have a look at the chenillekit-access module.
Regards
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [jira] Closed: (TAP5-476) Have a common handler/filter pipeline
for both component event and page render requests, to make it easier to add
filters that apply to both types of requests
Posted by Ulrich Stärk <ul...@spielviel.de>.
Howard,
could you please explain to me how the two pipelines work and how to add
filters to them and also how to use this new facade service? I couldn't
find any documentation on them and the "is logged in" scenario you are
aiming at seems so common that it should be documented somewhere...
Thanks,
Uli
Howard M. Lewis Ship (JIRA) schrieb:
> [ https://issues.apache.org/jira/browse/TAP5-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Howard M. Lewis Ship closed TAP5-476.
> -------------------------------------
>
> Resolution: Fixed
> Fix Version/s: 5.1.0.0
>
>> Have a common handler/filter pipeline for both component event and page render requests, to make it easier to add filters that apply to both types of requests
>> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>>
>> Key: TAP5-476
>> URL: https://issues.apache.org/jira/browse/TAP5-476
>> Project: Tapestry 5
>> Issue Type: New Feature
>> Components: tapestry-core
>> Affects Versions: 5.1.0.0
>> Reporter: Howard M. Lewis Ship
>> Assignee: Howard M. Lewis Ship
>> Fix For: 5.1.0.0
>>
>>
>> Currently, if you want to put a filter in place that afects both types of request, you have to a contribute a ComponentEventRequestFilter to the ComponentEventRequestHandler service, and a nearly identical PageRenderRequestFilter to the PageRenderRequestHandler service.
>> It would be nice if there was a service that acted as a facade around the two existing pipelines. The terminator of that pipeline could forward the request into one of the two existing pipelines.
>> The common example of this is a "is logged in" filter that sends a redirect if the user is not logged in; you want to do this for both types of requests.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org