[
https://issues.apache.org/jira/browse/TAP5-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1757:
---------------------------------
This issue has been last updated about 1.5 years ago and has no information
about the versions that are affected. That makes it hard to determine whether
it is still relevant.
If the issue still persists with the current stable version (5.3.7) or the most
recent development preview of Tapestry (5.4-beta-6), both of which are
available from Maven Central, please update it as soon as possible, adding the
respective version(s) to the issue's "Affects Version/s".
> 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.2#6252)
