[ http://issues.apache.org/jira/browse/MYFACES-331?page=comments#action_12316078 ]
Mathias Broekelmann commented on MYFACES-331: --------------------------------------------- I´ve fixed the new uidata and uicolumns implementation. But that doen´t solve your problem. IMO the main reason is that new new uidata and uicolumns implementation uses the saveState and restoreState mothods to hold the state for each row (cell for uicolumns) while the iteration is done in the jsf-phases. Your custom value- and methodbindings don´t save their state which is the reason why your component is not working. Try to rewrite your component or create a plugable subview and use the aliasbean (which is the better solution IMO) to solve this issue. > 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
