tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1757) Grid does not fully adhere to volatile="true"
Date Mon, 12 Jan 2015 08:10:57 GMT

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

Jochen Kemnade closed TAP5-1757.
--------------------------------
    Resolution: Invalid

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4
preview release), feel free to provide the necessary information and reopen.

> Grid does not fully adhere to volatile="true"
> ---------------------------------------------
>
>                 Key: TAP5-1757
>                 URL: https://issues.apache.org/jira/browse/TAP5-1757
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>            Reporter: Ville Virtanen
>         Attachments: grid_volatile.patch
>
>
> Tapestry omits the state saving of the grid if volatile parameter is set to true. However,
grid still invokes the setupdatasource during form postback even though it is (when volatile
is true) unneccassary. It also prevents us from using grid under some ajax circumstances with
form.
> The proposed patch simply changes the parameter "volatile" of gridrows to be promoted
as grid's parameter, and the gridrows inherits it. Now that Grid has the knowledge of the
parameter it is trivial to add it to the if that checks whether the grid is inside form or
not (when adding the setupdatasourceevent to formsupport).



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

Mime
View raw message