[TAP5-1966] Plastic should throw an exception when it attempts to redefine an existing method unexpectedly

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.3.3
• Fix Version/s: 5.4
• Component/s: plastic
• Labels: property
• Assignee: Unassigned
• Reporter: Andrei Arapov
• Created: 04/Jul/12 13:00
• Updated: 20/Aug/15 07:19
• Resolved: 20/Aug/15 07:19

Description

For example, we have page class; page shows "select" component on corresponsing page :

public class FooPage {
...

// now let's define Property "organizations"

@Property
private List<Organization> organizations;

// we create method for getting SelectModel class for "select" component

public SelectModel getOrganizations() {
... blablabla
}

...
}

And on page:

...
<t:select t:id="organization" model="getOrganizations" value="user.organization" encoder="getValueEncoder()"/>
...

Ok. What's happen now? The behaivour of this situation is not defined. Tapestry can invoke "SelectModel getOrganizations()" or "List<Organization> getOrganizations()" in arbitrary order (it is clear why).

It would be good, if Plastic throws an exception, when it redefines getter which already exists.

Issue Links

• relates to: TAP5-2268 @Property may generate a method that conflicts with an existing one, without error, and with unpredictable results