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

        Hide
        Kevin Menard added a comment -

        As I've said on the mailing list, I think extending the concept of a "Start" page to each package would largely avoid this problem. I guess there could still be ambiguity between activation context for the root page and locating other pages in the package, but I think it could be sorted out by giving preference to page names then to context.

        An alternative to requiring the page be named "Start" is to have some sort of @Index or @Root annotation that could be attached to any page.

        Show
        Kevin Menard added a comment - As I've said on the mailing list, I think extending the concept of a "Start" page to each package would largely avoid this problem. I guess there could still be ambiguity between activation context for the root page and locating other pages in the package, but I think it could be sorted out by giving preference to page names then to context. An alternative to requiring the page be named "Start" is to have some sort of @Index or @Root annotation that could be attached to any page.
        Hide
        Howard M. Lewis Ship added a comment -

        I agree, but searching for longest match first is part of the approach towards supporting an "Index" page in each package. Eventually, the "Start" page concept would be deprecated in favor of a root-level Index page.

        Show
        Howard M. Lewis Ship added a comment - I agree, but searching for longest match first is part of the approach towards supporting an "Index" page in each package. Eventually, the "Start" page concept would be deprecated in favor of a root-level Index page.

          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