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 Mon, 01 Mar 2010 17:29:05 GMT

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

Skow commented on TAP5-1009:

I believe the issue is related to keeping the sort column and order in the user's session
verses encoding it into the Form data itself.  When CollectionGridDataSource.getRowValue is
called, the order of the list coming off the form is different than the newly created sort
order based off the values in the session. 

Although this issue may seem like a little used use-case, I think there are other ways for
the issue to manifest itself.  This particular instance of recreating the issue is just a
fairly straight forward way of seeing the problem.

> 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