[
https://issues.apache.org/jira/browse/TAP5-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade closed TAP5-1966.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.4
Fixed via TAP5-2268
> Plastic should throw an exception when it attempts to redefine an existing
> method unexpectedly
> ----------------------------------------------------------------------------------------------
>
> Key: TAP5-1966
> URL: https://issues.apache.org/jira/browse/TAP5-1966
> Project: Tapestry 5
> Issue Type: Improvement
> Components: plastic
> Affects Versions: 5.3.3
> Reporter: Andrei Arapov
> Labels: property
> Fix For: 5.4
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
