Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-2044

Component action requests are not capable of handling the case where the active page and the page containing the component are different

    Details

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

      Description

      This can happen when page A renders a block from page B that contains component C. In this case, page A's logical name and activation context should go into the URL, as well as page B's logical name, and page C's nested id and event context. The current implementations (of LinkFactory, Dispatcher, etc.) assume that page A is always the same as page B.

        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: