Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Invalid
-
2.2.0-beta
-
None
-
None
-
None
Description
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?