[
https://issues.apache.org/jira/browse/MYFACES-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858529#comment-13858529
]
Xavier Cho commented on MYFACES-3840:
-------------------------------------
It happened during upgrading my project from MyFaces 2.1.12 + PrimeFaces 3.5 to
MyFaces 2.2.0-beta + PrimeFaces 4.0. It seems that switching between partial or
full state saving does not affect the issue.
I found that it can be reproducible even after I downgraded MyFaces, so it
could be caused by certain incompatibility of PrimeFaces 4.0 with MyFaces. It
seems there are lot of such problems with the combination, compared to
PrimeFaces 4.0 + Mojarra 2.2.4.
I don't think I had ever explicitly called getClientId() or createUniqueId()
methods on UIViewRoot myself, by the way.
Is there any hint how I could debug this problem? Thanks!
> UIViewRoot uses different id while saving and restoring states.
> ---------------------------------------------------------------
>
> Key: MYFACES-3840
> URL: https://issues.apache.org/jira/browse/MYFACES-3840
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.2.0-beta
> Reporter: Xavier Cho
>
> After I upgraded to 2.2.0-beta, every postback requests which requires
> @ViewScoped managed beans fails as they lose states after the initial request.
> I couldn't spend sufficient time to investigate so not perfectly sure if it's
> not caused by some misconfiguration on my end.
> Though, after a quick debugging, I found that in the
> DefaultFaceletsStateManagementStrategy class, state of an UIViewRoot instance
> is saved using its client ID in saveStateOnMapVisitTree:976, but it tries to
> restore it using its view ID in restoreView:301, thus failing to restore the
> state.
> Is this behavior normal? If so, what possible configuration could cause it to
> use different IDs between saving and restoring state?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
