Tapestry
  1. Tapestry
  2. TAPESTRY-2220

In some cases, component event requests are incorrectly interpretted as render requests (with a page activation context)

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 5.0.10
    • Fix Version/s: 5.0.11
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      The PageRenderDispatcher runs first, and it sees a URL like /folder/name.componentid (clearly, an action URL) as page "/folder/index" activation context "name.componentId".

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        The ComponentEventDispatcher is currently wired to run after the PageRenderDispatcher. Perhaps these should be reversed? CED was rewritten a ways back to be much pickier about what paths it processes, based on a regular expression.

        Show
        Howard M. Lewis Ship added a comment - The ComponentEventDispatcher is currently wired to run after the PageRenderDispatcher. Perhaps these should be reversed? CED was rewritten a ways back to be much pickier about what paths it processes, based on a regular expression.
        Hide
        Howard M. Lewis Ship added a comment -

        Moving the CED before the PRD solves the problem.

        Show
        Howard M. Lewis Ship added a comment - Moving the CED before the PRD solves the problem.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development