[jira] Commented: (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

["Massimo Lusetti (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667714#action_12667714 ] 

Massimo Lusetti commented on TAP5-476:
--------------------------------------

Another long awaited feature. These could easier to add features to the chenillekit-access module. Great!

BTW, in the context of "is logged in", doesn't sound reasonable to also make the logic to interpret the URL a service which can be reused, like by the chenillekit-access for example, so every "is logged in" module is sure to interpret the URL the correct way?

> 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
>
> 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.