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

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade closed TAP5-2268.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 5.4

Thanks!

> @Property may generate a method that conflicts with an existing one, without error, and with unpredictable results
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-2268
>                 URL: https://issues.apache.org/jira/browse/TAP5-2268
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.7, 5.4
>            Reporter: Alexey Chalov
>            Priority: Minor
>             Fix For: 5.4
>
>         Attachments: 0001-TAP5-2268-add-test-to-verify-that-this-issue-is-no-l.patch, 0005-TAP5-2268-Property-may-generate-a-method-that-confli.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)