[
https://issues.apache.org/jira/browse/TAPESTRY-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572143#action_12572143
]
Howard M. Lewis Ship commented on TAPESTRY-2150:
------------------------------------------------
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.
> Tapestry should recognize pages that are "nested" beneath other pages
> ---------------------------------------------------------------------
>
> Key: TAPESTRY-2150
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2150
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.10
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> 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).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
