[TAP5-2268] @Property may generate a method that conflicts with an existing one, without error, and with unpredictable results

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.3.7, 5.4
• Fix Version/s: 5.4
• Component/s: tapestry-core
• Assignee: Unassigned
• Reporter: Alexey Chalov
• Created: 26/Dec/13 14:48
• Updated: 07/Oct/15 08:23
• Resolved: 23/Mar/15 15:43

Description

Page class can contain 2 conflicting pieces for displaying html table like that:

@Property(write=false)
private List<Item> items;
or
public GridDataSource getItems() {
....
}
This causes no error then these 2 constructs present in page class, but behaviour is unpredictable: either accessor for GridDataSource or property generated accessor can be used when page is generated. Restarting/redeploying application can change this behaviour to any of these 2 choices in unpredictable manner. More oftenly (as I noticed 90% data source accessor is used when table content is generated), but about ~10% is left on generated accessor. Tested under Tomcat 7.

It would be nice if exception will rise in such situaеions to prevent accidental programming error.

Issue Links

• is related to: TAP5-2508 Page activation method not always called since t54-beta33
• is related to: TAP5-1966 Plastic should throw an exception when it attempts to redefine an existing method unexpectedly