[richfaces-issues] [JBoss JIRA] (RF-12611) rich:dataTable doesn't call restoreState() on a row-level composite component
[
https://issues.jboss.org/browse/RF-12611?page=com.atlassian.jira.plugin.s...
]
Mark Cave-Ayland commented on RF-12611:
---------------------------------------
After a little bit of work, I've managed to set up a suitable development environment
on my workstation which is capable of building RichFaces from source.
I can now confirm that making the following change to requiresRowIteration() in
UIDataAdapter.java allows my embedded row-level composite component to function correctly
within rich:dataTable:
private boolean requiresRowIteration(FacesContext context) {
return true;
}
I'm not necessarily confident enough in this as a solution to submit a formal patch
(it may have other side-effects I am not aware of), but I thought I should document it
here anyway.
rich:dataTable doesn't call restoreState() on a row-level
composite component
-----------------------------------------------------------------------------
Key: RF-12611
URL: https://issues.jboss.org/browse/RF-12611
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-tables
Affects Versions: 4.2.3.Final
Environment: Debian Wheezy, Linux, amd64
Reporter: Mark Cave-Ayland
Attachments: RFStateBug1.tar.gz
I currently have a row-level composite component that works well within a h:dataTable
which I am looking to migrate to rich:dataTable for more flexibility with layout. However
when embedded within a rich:dataTable, the component state is not preserved during the
RESTORE_VIEW phase.
Further investigation with a debugger shows that the problem is within
UIDataAdapter::restoreState() in that requiresRowIteration() returns false during the
RESTORE_VIEW phase, and so the restoreState() function within the row-level composite
component is never called.
The related transcript from IRC can be found here:
http://transcripts.jboss.org/channel/irc.freenode.org/%23richfaces/2012/%....
Many thanks,
Mark.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira