Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
5.3.7, 5.4
-
None
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.