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

        Howard M. Lewis Ship created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Status Open [ 1 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Status In Progress [ 3 ] Closed [ 6 ]
        Fix Version/s 5.0.11 [ 12312968 ]
        Resolution Fixed [ 1 ]
        Mark Thomas made changes -
        Workflow jira [ 12424899 ] Default workflow, editable Closed status [ 12568584 ]
        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568584 ] jira [ 12591624 ]

          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