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 (Updated) (JIRA)" <ji...@apache.org> on 2011/09/28 01:02:45 UTC

[jira] [Updated] (TAP5-1675) Tapestry 5.3 allows a subcomponent to define a parameter with the same name as a base component

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

Howard M. Lewis Ship updated TAP5-1675:
---------------------------------------

    Summary: Tapestry 5.3 allows a subcomponent to define a parameter with the same name as a base component  (was: Tapestry 5.3 allows a subcomponent to defined a parameter with the same name as a base component)
    
> Tapestry 5.3 allows a subcomponent to define a parameter with the same name as a base component
> -----------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1675
>                 URL: https://issues.apache.org/jira/browse/TAP5-1675
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Howard M. Lewis Ship
>            Priority: Critical
>
> I believe you got a more reasonable error message in 5.2. In 5.3 you may get an error if both the fields have @Property, due to a name collision on the getter/setter method names. Instead, Tapestry should fail early explaining that both the component and (the identified base class) define the same parameter name.

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