You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2013/07/25 01:01:50 UTC

[jira] [Commented] (TAP5-2118) Bug in ComponentClassResolverImpl

    [ https://issues.apache.org/jira/browse/TAP5-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718987#comment-13718987 ] 

Howard M. Lewis Ship commented on TAP5-2118:
--------------------------------------------

Really wasn't thinking in terms of nested package names that similar.

A patch with tests would be welcome.

I suspect the package names should be stripped off the base class name in reverse order; "exports", the "export".
                
> Bug in ComponentClassResolverImpl
> ---------------------------------
>
>                 Key: TAP5-2118
>                 URL: https://issues.apache.org/jira/browse/TAP5-2118
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.6
>            Reporter: Thilo Tanner
>
> There is a small bug in ComponentClassResolverImpl in the method toLogicalName.
> Consider the following page: pages.export.exports.ExportsIndex
> This page will be mapped to:
> export/exports/sIndex instead of export/exports
> It seems that stripTerm is invoked with export instead of exports.
> I can contribute a patch if you like. Please let me know.
> Thanks and kind regards,
> Thilo

--
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