[
https://issues.apache.org/jira/browse/TOMAHAWK-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302884#comment-17302884
]
Mike Kienenberger commented on TOMAHAWK-961:
--------------------------------------------
Unfortunately, the fix in TOMAHAWK-1552 t:dataList, t:dataTable ajax causes
other problems. Setting a rowKey fixes the delete problem, but breaks other
functionality (other field values are lost, buttons stop working, warnings
about non-submitted values), possibly because the derived client ids are too
long or perhaps they duplicate. In the end, I had to port my original 1.x fix
to 2.x in order to have a working system after upgrading the application from
JSF 1.x to JSF 2.x. I still don't know if my fix is good enough for a general
solution, but it works for the simple application that I have to maintain.
[^Tomahawk21-DataTableRowState.patch.txt]
> Deleting a row when t:dataList/t:dataTable preserveRowStates=true assigns
> submitted values to wrong row
> -------------------------------------------------------------------------------------------------------
>
> Key: TOMAHAWK-961
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-961
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: Data List, Extended Datatable
> Affects Versions: 1.1.7-SNAPSHOT
> Reporter: Mike Kienenberger
> Assignee: Leonardo Uribe
> Priority: Major
> Fix For: 1.1.11
>
> Attachments: Tomahawk21-DataTableRowState.patch.txt,
> preserveRowStates-2007-04-12-00.txt
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
