[
https://issues.apache.org/jira/browse/TAPESTRY-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572136#action_12572136
]
Kevin Menard commented on TAPESTRY-2150:
----------------------------------------
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.
> 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]
