tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Skow (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-1009) Sorting a Grid in multiple open windows scrambles the table data
Date Tue, 02 Mar 2010 18:07:27 GMT

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

Skow commented on TAP5-1009:

Creating a custom PrimaryKeyEncoder and specifying it as the 'encoder' on each Grids seems
to work around the problem. It looks like the row-based updating that the Grid does is a shortcut
'feature', but can cause data corruption. Other than adjusting the documentation to include
a warning, I'm not sure what else can be done to actually 'fix' this issue since the answer
seems to just be not to use the default behavior of Grid.

This issue can probably be closed, but I'm leaving it open to raise awareness of the issue
so it doesn't get overlooked by the project maintainers.

> 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.
You can reply to this email to add a comment to the issue online.

View raw message