Following exception is seen when changing skins for the second time immediately after the first: Caused by: javax.faces.FacesException: Cannot remove the same component twice: pbG9dea276d_2dee9e_2d4150_2dad91_2d22255b5a57d2_j_id1:j_idt444 at com.sun.faces.context.StateContext$AddRemoveListener.handleAddRemoveWithAutoPrune(StateContext.java:489) [jsf-impl-2.1.13-redhat-1.jar:2.1.13-redhat-1] at com.sun.faces.context.StateContext$AddRemoveListener.handleRemove(StateContext.java:371) [jsf-impl-2.1.13-redhat-1.jar:2.1.13-redhat-1] at com.sun.faces.context.StateContext$AddRemoveListener.processEvent(StateContext.java:334) [jsf-impl-2.1.13-redhat-1.jar:2.1.13-redhat-1] at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) [jboss-jsf-api_2.1_spec-2.0.7.Final-redhat-1.jar:2.0.7.Final-redhat-1] Investigating this problem lead to determining that it was caused by the need for Portlet Bridge to retain the UIViewRoot from JSF between requests, and the list of ADDED/REMOVED components being retained between requests, making JSF believe it was removing a component for the second time when it fact it wasn't. This has been raised as http://java.net/jira/browse/JAVASERVERFACES-2609 against the Mojarra JSF implementation. There is also a tracker on AS7 jira to have the fix added when it's available: https://issues.jboss.org/browse/AS7-5970
So to make it clear there is nothing we can do with this issue at this point - until it gets fixed in EAP. This may need to be postponed after JPP 6
Stan Silvert <ssilvert> made a comment on jira AS7-5970 Are you guys satisfied that this is fixed now that JAVASERVERFACES-2609 is done? Upstream fix should be integrated now. Can we close this?
Ken Finnigan <ken> made a comment on jira AS7-5970 I don't see a problem with that. Safe to close from my perspective
Stan Silvert <ssilvert> updated the status of jira AS7-5970 to Resolved
According to JIRA/BZ this is resolved in EAP 6.1 Alpha