[
https://jira.jboss.org/jira/browse/RF-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shaikovsky resolved RF-6450.
---------------------------------
Resolution: Rejected
according to design all such questions should be solved using external sorting.
Built-in sorting designed for simpliest cases. B.t.w. it could be used together
with a4j:queue in order no to sent concurent requests.
> DataTable: add ajax sort event/request customization
> ----------------------------------------------------
>
> Key: RF-6450
> URL: https://jira.jboss.org/jira/browse/RF-6450
> Project: RichFaces
> Issue Type: Feature Request
> Affects Versions: 3.2.2
> Environment: JSF Sun RI 1.2_12, RichFaces 3.2.2
> Reporter: Gerrit Brehmer
> Assignee: Konstantin Mishin
> Fix For: 3.3.1
>
>
> We need the common RichFaces ajax-request parameters like ajaxSingle or
> onSubmit for column sorting feature. Otherwise we get thread-safety problems,
> because if i click sort icon on one column and right after that (before
> response from first click arrived) click on another column-sort-icon. Because
> we have input fields in some columns, the values will be set to the wrong
> entries, because generated client-ids which will be sent by the second
> request are generated before response and new ids of the first request are
> applied to the table on client side. But during the second request, the table
> is already sorted (first column) in the backend. If we can drop applying
> table values or show a modalPanel on submit, we could avoid this
> thread/concurrent request related problems.
--
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
