[
http://issues.apache.org/jira/browse/MYFACES-1048?page=comments#action_12363561
]
Martin Marinschek commented on MYFACES-1048:
--------------------------------------------
Don't think so.
See this code:
public void encodeBegin(FacesContext context) throws IOException
{
if (!isRendered())
return;
if (_isValidChildren && !hasErrorMessages(context))
{
_preservedDataModel = null;
}
> t:dataTable preserveModel has no option to refresh model before render
> ----------------------------------------------------------------------
>
> Key: MYFACES-1048
> URL: http://issues.apache.org/jira/browse/MYFACES-1048
> Project: MyFaces
> Type: Improvement
> Reporter: Simon Kitching
>
> Currently, t:dataTable's preserveDataModel "permanently" preserves the model.
> This nicely ensures that the contents of the datamodel used at render time is
> the same at the following validation phase - critical for correct behaviour.
> However it *keeps* the same data through to the next render phase too. This
> means that once a dataTable is initialised with data,
> it never changes (the data gets "stale"). It would be nice to have an extra
> option for the data to be preserved between render and
> postback, but then discarded before the next render so that fresh (non-stale)
> data can be fetched.
> In other words, the problem is that without preserveDataModel, dataTable has
> two fetches: at validate then at render.
> The preserveDataModel reduces this to zero fetches. However having *one*
> fetch [before each render phase but not before validate phase) is also useful.
--
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
