Able to change tabs in ace-showcase animation, but the following Exception is seen and the animation does not return to initial state:

java.lang.IllegalStateException: Component ID _t29_windowviewid has already been found in the view.
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:820)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:804)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:804)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:804)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:804)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:804)
at com.sun.faces.application.StateManagerImpl.saveView(StateManagerImpl.java:129)
at javax.faces.application.StateManager.getViewState(StateManager.java:525)
at org.icefaces.impl.context.DOMPartialViewContext.renderState(DOMPartialViewContext.java:421)
at org.icefaces.impl.context.DOMPartialViewContext.processPartial(DOMPartialViewContext.java:195)

Above exception fixed for animation, but FileEntry problem appears to have a different cause. This is an interaction with autoid – the original value of the ID is being modified so the component is incorrectly determining that it is not already in the page.

In FireFox, fileEntry shows on the error console:

Warning: Form contains a file input, but is missing method=POST and enctype=multipart/form-data on the form. The file will not be sent.
Source File: http://localhost:8080/ace-showcase/fileEntry.jsf
Line: 0

Icefaces2 # 23643
Server: Tomcat6
Browser: FF3.6, IE8 & Opera10.60

Animation not working correctly. Try using fade animation tabs & then blind up/down animation tab a few time.
See attached screenshot-1 & screenshot-2.

File Entry works fine on all browser.
There is a known issue with Opera, the uploaded files table not being updated without reload. (This is present with or without partial state saving)

Recommend assigning this to the component team for animation failure – likely the animation behavior is not storing the current value of the opacity in a way that is compatible with partial state saving.

Branches, branches, everywhere branches. When partial-state-saving is true, when the tabset element is clicked and a lifecycle occurs, the initialStateMarked method returns true, and the paths taken through the UIComponentBase methods are vastly different. Even the main method does something quite considerably different in the BehaviorBase class:

public Object saveState(FacesContext context) {

if (context == null)

// If initial state has been marked, we don't need to
// save any state.
if (initialStateMarked())

// At the moment, the only state we need to save is our listeners
return UIComponentBase.saveAttachedState(context, listeners);
}

In the non-working case, the UIComponentBase.saveAttachedState(context, listeners) method is executed and in the partial state saving case, it is not. So it's likely safe to say that in the full state saving path the code isn't saving or restoring the structures exactly the same way as in the working path, however, determining exactly what structure is different is still in progress.

Code for this Jira is complete. At least I think it is, the outstanding issue is creating a test that exercises state saving of bindings in a way that shows in an obvious way that it works.