Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.2
-
Fix Version/s: EE-3.3.0.GA_P01, 4.0.BETA, 4.0
-
Component/s: ACE-Components, Sample Apps
-
Labels:None
-
Environment:Icefaces3 trunk revision# 31223
-
Assignee Priority:P2
-
Affects:Compatibility/Configuration
-
Workaround Exists:Yes
-
Workaround Description:Use Mojarra JSF 2.1.6.
Description
The following sample apps tests started failing when using the PartialStateSavings disabled:
1) Component-showcase (all browsers):
Panel - Dynamic Tabset - Server Internal Error on tab switch:
Oct 1, 2012 1:36:12 PM com.sun.faces.application.view.FaceletViewHandlingStrategy handleRenderException
SEVERE: Error Rendering View[/showcase.xhtml]
java.lang.IllegalStateException: Component ID iceform:icePnlTbSet:0 has already been found in the view.
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:832)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:816)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:816)
This test started failing after switching from 3.0.x-maintenance branch to IF3/trunk.
2) Showcase - CheckBox Button:
When the checkboxButton is unselected, reselecting the checkboxButton causes Network Connection Interrupted message.
Server side errors:
1-Oct-2012 1:05:32 PM com.sun.faces.application.view.FaceletViewHandlingStrategy handleRenderException
SEVERE: Error Rendering View[/showcase.xhtml]
java.lang.IllegalStateException: Component ID frm:menuLinks has already been found in the view.
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:832)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:816)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:816)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:816)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:816)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:816)
at com.sun.faces.util.Util.checkIdUniqueness(Util.java:816)
This test started failing after switching from 3.0.x-maintenance branch to IF3/trunk.
3) Showcase:
3.1) DataTable - Grouping - Network Connection Interrupted message when sorting, server error:
1-Oct-2012 1:17:19 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [Faces Servlet] in context with path [/showcase] threw exception
java.lang.IllegalStateException: CDATA tags may not nest
at com.sun.faces.renderkit.html_basic.HtmlResponseWriter.startCDATA(HtmlResponseWriter.java:664)
at javax.faces.context.ResponseWriterWrapper.startCDATA(ResponseWriterWrapper.java:172)
at javax.faces.context.PartialResponseWriter.startError(PartialResponseWriter.java:342)
..........
3.2) DataTable - Multi Row Header: Network Connection Interrupted message when sorting, same server errors as above.
3.3) DataTable - Row Expansion: Network Connection Interrupted message when sorting, same server errors as above.
3.4) DataTable - Table Configuration: Sorting in the table, and renaming columns in configurator not working, Network Connection Interrupted popup message when saving changes in the configurator, similar errors visible in Tomcat log.
All these dataTable failures started to occur after upgrading to Mojarra 2.1.13-PATCH on the trunk; last successful revision was #30870.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
A couple of notes as I kick off the investigation:
1) This appears to be constrained to Mojarra as the same components work fine with MyFaces.
2) I made a simple change to the Checkbox example where I modified the ace:ajax attributes and changed the render attribute from the id of another component on the page to @form and it stopped having a problem:
<ace:ajax execute="@this" event="activate" render="valueDescription"/>
However, not all the failing components have an ace:ajax component so this might not mean much.
Show
Deryk Sinotte
added a comment - - edited A couple of notes as I kick off the investigation:
1) This appears to be constrained to Mojarra as the same components work fine with MyFaces.
2) I made a simple change to the Checkbox example where I modified the ace:ajax attributes and changed the render attribute from the id of another component on the page to @form and it stopped having a problem:
<ace:ajax execute="@this" event="activate" render="valueDescription"/>
However, not all the failing components have an ace:ajax component so this might not mean much.
These issues are believed to be related to Mojarra state-saving regressions. There is a Mojarra JIRA that is related:
http://java.net/jira/browse/JAVASERVERFACES-2636
We will wait for resolution of that issue and re-test.
Mojarra JIRA has been pushed back to 2.1.24, so we will revisit prior to 3.4 release.
Most of these are related to Mojarra 2.1.13 update.