[ http://issues.apache.org/jira/browse/MYFACES-331?page=comments#action_12316148 ]
Mike Kienenberger commented on MYFACES-331: ------------------------------------------- Your change isn't backward-compatible, but I do understand what you're trying to accomplish, and unfortunately, I don't yet have a better alternative to suggest. I guess I'll have to subclass UISelectBoolean and change how it performs saveState/restoreState since it's not possible for my indirect value and method bindings to save state (which was how they provided the flexibility I needed). To me, it feels incorrect to be saving/restoring state in setRowIndex() rather than saveState/restoreState. There's no user-hook to customize the save/restore behavior. I may also go the aliasbean route, but I really didn't want to have to start all over with another component and figure out all of the idiosyncrasies with it too. > 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
