tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Harner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1009) Sorting a Grid in multiple open windows scrambles the table data
Date Wed, 26 Dec 2012 20:00:13 GMT

    [ https://issues.apache.org/jira/browse/TAP5-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539663#comment-13539663

Bob Harner commented on TAP5-1009:

Since 5.1 the Grid documentation (http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/corelib/components/Grid.html)
describes the constraints better:

"For this reason, when using Grid and Form together, you should generally provide the Grid
with a ValueEncoder (via the encoder parameter), or use an entity type for the "row" parameter
for which Tapestry can provide a ValueEncoder automatically. This will allow Tapestry to use
a unique ID for each row that doesn't change when rows are reordered."

I'm closing this issue, since I think the code works as designed and the documentation provides
the appropriate guidance how to get the desired behavior.

If anyone feels a better behavior is possible and appropriate, please reopen and attach a
patch (hopefully including tests) with the proposed solution.
> Sorting a Grid in multiple open windows scrambles the table data
> ----------------------------------------------------------------
>                 Key: TAP5-1009
>                 URL: https://issues.apache.org/jira/browse/TAP5-1009
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.18
>            Reporter: Skow
> Steps to recreate:
> 1. Open Browser A to your T5 application.
> 2. Search for a record with an editable grid with more than one row.
> 3. Sort the grid by Column X.
> 4. Open Browser B (new tab/window on the same machine)
> 5. Search for the same record as step 2
> 6. Sort the grid by Column Y (any sort which gets the rows in a different order)
> 7. Save the record in Browser A (it has the original sort order).
> Tapestry saves the row data to the wrong objects and effectively 'scrambles' them.
> This issue is similar to issue:
> https://issues.apache.org/jira/browse/TAP5-34
> Please let me know if there are any issues recreating this issue or if additional information
is needed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message