Tapestry 5.3 allows a subcomponent to defined 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
