[jira] [Closed] (TAP5-1646) When a subclass defines a parameter with a given name that conflicts with a parameter of the superclass, Tapestry should throw an exception at page construction time; instead the field in the subclass seems to be null (a change in behavior from 5.2)

["Howard M. Lewis Ship (Closed) (JIRA)" <ji...@apache.org>]

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

Howard M. Lewis Ship closed TAP5-1646.
--------------------------------------

    Resolution: Duplicate
      Assignee: Howard M. Lewis Ship

Fixed as TAP5-1675.
                
> When a subclass defines a parameter with a given name that conflicts with a parameter of the superclass, Tapestry should throw an exception at page construction time; instead the field in the subclass seems to be null (a change in behavior from 5.2)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1646
>                 URL: https://issues.apache.org/jira/browse/TAP5-1646
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> To reiterate:
> Base class defines a @Parameter field
> Sub class defines another field, same name, also @Parameter
> In the subclass, the value for the field is null
> I believe 5.2 handled this better, though I'm not sure.

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