Logical page name strip order
-----------------------------
Key: TAP5-1835
URL: https://issues.apache.org/jira/browse/TAP5-1835
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.2.5
Reporter: Vladimir Velikiy
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
