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-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
