tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Le Merdy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAP5-2172) ComponentClassResolver does not resolve logical name to the more intuitive component
Date Fri, 06 Sep 2013 09:31:14 GMT

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

Olivier Le Merdy updated TAP5-2172:

    Attachment: bug-sample.zip

Bug sample project
> ComponentClassResolver does not resolve logical name to the more intuitive component
> ------------------------------------------------------------------------------------
>                 Key: TAP5-2172
>                 URL: https://issues.apache.org/jira/browse/TAP5-2172
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.7
>            Reporter: Olivier Le Merdy
>            Priority: Minor
>         Attachments: bug-sample.zip
> ComponentClassResolver does not always resolve components the more intuitive way.
> See attached sample project for demonstration purposes but given a set of three components:
"foo/Bar", "foo/FooBar" and "foo/BarFoo", the logical name "foo/bar" will be resolved to "foo/FooBar"
component instead of the more intuitive "foo/Bar".
> The workaround is to rename our components but, given the stripping can happen at multiple
package levels, it is sometimes hard to predict (and debug) what is happening, e.g.: "layout/detail/Section"
logical name will resolve primarily "layout/detail/SectionLayout" component instead of "layout/detail/Section"
> Looking at ComponentClassResolverImpl implementation, the component name cache is filled
following classpath alphabetical order, overriding any previous entry found.
> Could it be possible to privilege a component when its unstripped name exactly match
its logical name?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message