Uploaded image for project: '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
    • Status: Closed
    • Priority: 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".

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: