Andrei Arapov created TAP5-1966:
-----------------------------------
Summary: It would be good, if Plastic throws an exception, when it
is redefining getter which already exists
Key: TAP5-1966
URL: https://issues.apache.org/jira/browse/TAP5-1966
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core, tapestry-ioc
Affects Versions: 5.3.3
Reporter: Andrei Arapov
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 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
