[
https://issues.apache.org/jira/browse/TRINIDAD-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209749#comment-13209749
]
Gabrielle Crawford commented on TRINIDAD-2217:
----------------------------------------------
One possible fix is to remove it from our tag handlers, but new components
added during restore view will be fully state saved due to the issue in
2285(see above).
Another possible fix is to continue to call markInitialState in our tag handler
but only during render response, and only if initialStateMarked returns false
(otherwise any deltas saved between restore view and render response may get
blown away). This still leaves the issue that if someone calls
clearInitialState on a component before render response, presumable because
they want to force full state saving on the component, then the tag handler
will call markInitialState again. Since calling clearInitialState is unusual
this is probably acceptable while waiting for the RI fix.
> when using partial state saving markInitialState called many times
> ------------------------------------------------------------------
>
> Key: TRINIDAD-2217
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2217
> Project: MyFaces Trinidad
> Issue Type: Bug
> Reporter: Gabrielle Crawford
>
> We have been calling markInitialState in our tagHandler since before JSF had
> partial state saving. In JSF 2 they support partial state saving, so the
> framework should always be the one calling markInitialState and we should
> remove it from our tag handlers, but there is a bug in the framework which
> means it doesn't always call markInitialState in render response, see
> http://java.net/jira/browse/JAVASERVERFACES-2285
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
