Tapestry
  1. Tapestry
  2. TAPESTRY-1479

It would be nice to have a pipeline between the Dispatchers and the RequestHandlers (for component action requests and for page render requests)

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.0
    • Fix Version/s: 5.0.5
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      It would be very useful to have a pipeline step between the point where the type of request is known and that information is executed. Something like:

      interface RequestPipeline

      { void handleAction(String logicalPageName, String nestedComponentId, String eventType, String[] context, String[] activationContext); void handleRender(String logicalPageName, String[] context, PageRenderer renderer); }

      interface RequestPipelineFilter

      { void handleAction(String logicalPageName, String nestedComponentId, String eventType, String[] context, String[] activationContext, RequestPipeline pipeline); void handleRender(String logicalPageName, String[] context, PageRenderer renderer, RequestPipeline pipeline); }

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        ... it's also now necessary to support setting the request encoding after the page has been identified.

        Show
        Howard M. Lewis Ship added a comment - ... it's also now necessary to support setting the request encoding after the page has been identified.
        Hide
        Howard M. Lewis Ship added a comment -

        The names and such have changed a bit from when the issue was first added, and its two separate handler interfaces and matching filter interfaces.

        For TAPESTRY-1294, this pipeline was necessary so that the request encoding could be properly set.

        Show
        Howard M. Lewis Ship added a comment - The names and such have changed a bit from when the issue was first added, and its two separate handler interfaces and matching filter interfaces. For TAPESTRY-1294 , this pipeline was necessary so that the request encoding could be properly set.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development