Tapestry
  1. Tapestry
  2. TAPESTRY-2150

Tapestry should recognize pages that are "nested" beneath other pages

    Details

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

      Description

      From the mailing list.

      If I have a page class of pages.Orders (that lists Orders) and two other pages: pages.orders.EditOrders and pages.orders.ViewOrders then the later URLs (/orders/edit and /orders/view) appear to be for the /orders page (and include activation context).

      Tapestry should be careful to look for the longest match.

      As a workaround, the list page could be named pages.orders.ListOrders (/orders/list).

        Activity

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

          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