Tapestry 5
  1. Tapestry 5
  2. 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 New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s:
    • Fix Version/s:
    • Component/s: tapestry-core
    • Labels:


      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.


        Howard M. Lewis Ship created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Resolution Fixed [ 1 ]
        Status In Progress [ 3 ] Closed [ 6 ]
        Fix Version/s [ 12313428 ]


          • Assignee:
            Howard M. Lewis Ship
            Howard M. Lewis Ship
          • Votes:
            1 Vote for this issue
            1 Start watching this issue


            • Created: