Details
-
Type:
Task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.0
-
Fix Version/s: 3.3
-
Component/s: ACE-Components, ICE-Components
-
Labels:None
-
Environment:JSF 2
-
Assignee Priority:P3
Description
http://java.net/jira/browse/JAVASERVERFACES-1929
It looks like MyFaces and Mojarra use different algorithms in their visitTree methods in regards to state saving. In our compat container components we have implemented versions of visitTree() which we should be sure conform with any possible changes introduced by Mojarra's jira for fixing their state saving.
It looks like MyFaces and Mojarra use different algorithms in their visitTree methods in regards to state saving. In our compat container components we have implemented versions of visitTree() which we should be sure conform with any possible changes introduced by Mojarra's jira for fixing their state saving.
2.1.18 isn't available, so I've reviewed 2.1.17 and found no obvious differences in the implementations of visitTree, or other base class functionality we've derived from and overridden, and the current implementations in UIData.