tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1835) Stripping of package names from logical page name may not occur in intuitive order
Date Mon, 22 Aug 2016 06:48:22 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jochen Kemnade closed TAP5-1835.
--------------------------------
    Resolution: Incomplete

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.4.1 or newer), feel free
to provide the necessary information and reopen.

> Stripping of package names from logical page name may not occur in intuitive 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
>              Labels: bulk-close-candidate
>         Attachments: terms_strip_order.diff
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message