You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by vvv <ve...@gmail.com> on 2012/01/27 14:40:13 UTC

Logical page name strip order

I have page in library with prefix requests. Its logical path is:
requests/requeststatus/RequestStatusView. After stripping logical page name
by ComponentClassResolver I see the following result:
requests/requeststatus/tatusView. This is because the terms of the path
prefix are processed in direct order: requests, requeststatus. It would be
more correct way to handle the terms in reverse order: requeststatus,
request, which will give more correct result: requests/requeststatus/View.
The last term in the path prefix has a close value to the name of the page
than the previous.
I opened the issue: https://issues.apache.org/jira/browse/TAP5-1835


--
View this message in context: http://tapestry.1045711.n5.nabble.com/Logical-page-name-strip-order-tp5435443p5435443.html
Sent from the Tapestry - Dev mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org