ScrollableDataTable. Selection over RowKey instead of index.
------------------------------------------------------------
Key: RF-6688
URL: https://jira.jboss.org/jira/browse/RF-6688
Project: RichFaces
Issue Type: Bug
Components: ScrollableDataTable
Affects Versions: 3.3.0
Environment: richfaces-api-3.3.1-20090204
Tomcat 6.0.18
Reporter: Alexander Buttau
ScrollableDataTable uses row indexes to store selection on client side, this
causes a problem if bound data changes (new rows added or removed by another
parallel transaction).
For example.
First user opens a page. ScrollableDataTable has 3 records.
In a parallel transaction inserts a second user a new record (as a first row =
on index 0)
First user selects first row and execute some action. Selection object on the
server-side returns a row, which was added by the secon user, and not the row
which was realy selected by first user.
i also added a test-project: simple page with SDT and two buttons "Selection"
(shows current selection) and "Add Row" (inserts a new row on position 0)
to reproduce a bug select a row, click "add row" and then "selection", you'll
see that selection is wrong.
selection must be saved not as indexes on client side, but as rowkeys(which can
be defined as a real IDs of records in DB).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
