Allow x:dataTable to store its data model in the component tree
---------------------------------------------------------------
Key: MYFACES-98
URL: http://issues.apache.org/jira/browse/MYFACES-98
Project: MyFaces
Type: New Feature
Versions: 1.0.7 beta, 1.0.8 beta
Reporter: sean schofield
Priority: Minor
I'm proposing a new attribute (saveModel) for x:dataTable that can be
true/false (default is false).
When "true", the bean that is associated with the "value" attribute would be
stored in the component tree. I'm going to look to the <x:saveState> tag for
guidance on this, but the idea would be that you do not have to use
<x:saveState> tag for this purpose once the feature is implemented.
The saved value of the data model would be restored during the Restore View
phase. Among other things, this would allow actions to be applied to the
component with the row index corresponding to the one the user clicked even if
the data store used has since changed. Just before the Render Response phase,
the component could use the binding expression combined with the bean
management facility to create an updated version of the data model which is
then saved to the client state and rendered.
This way you have the best of both worlds. You can have value change and
action events based on a comparisson of the same data that was used for the
original response and the user will still see the latest data when the response
is encoded.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
