[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

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.1.0.0
• Fix Version/s: 5.1.0.0
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 27/Jan/09 15:38
• Updated: 27/Jan/09 19:21
• Resolved: 27/Jan/09 19:21

Description

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.