[ http://issues.apache.org/jira/browse/MYFACES-331?page=comments#action_12316210 ]
Mathias Broekelmann commented on MYFACES-331: --------------------------------------------- Apparently we violate the spec if we use saveState/restoreState in UIData.setRowIndex to handle the component state. Even though IMO it´s better to do it with saveState/restoreState which is able to handle not only EditableValueHolder instances. We may change the current implementation for setRowIndex back to only save and restore the EditableValueHolder instances and reset the clientId through the shaky setId(getId()). > post-Mathias-Broekelmann x:dataTable doesn't work with dynamically-created > UIColumns data. > ------------------------------------------------------------------------------------------ > > Key: MYFACES-331 > URL: http://issues.apache.org/jira/browse/MYFACES-331 > Project: MyFaces > Type: Bug > Versions: Nightly Build > Reporter: Mike Kienenberger > Assignee: Mathias Broekelmann > Attachments: RowAndColumnRelationshipComponent.zip > > Mathias, I still have to use the BEFORE_SVN_REORG version as your new > dataTable code still isn't working with programmically-created > UIColumns elements -- they get lost after a page refresh, probably due > to a save/restore state issue. My programmically-created > footer-with-UICommand and UI-Column-with-UIOutput row header are saved and > restored properly, though. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
