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

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 5.3
• Fix Version/s: 5.3
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 27/Sep/11 22:05
• Updated: 28/Sep/11 00:52
• Resolved: 27/Sep/11 23:42

Description

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.