Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.1, EE-3.0.0.GA_P01
-
Fix Version/s: EE-3.0.0.GA_P01, 3.2
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 3.1.0 BETA2 06282012, ICEfaces 3.1.0, ICEfaces 3.2.0 BETA1
Description
Upon closing an ace:dialog which executes and all render, the page becomes unresponsive since the javax.faces.ViewState is null.
Test Case scenario:
A page includes two forms, one that includes an inputText field and a commandButton. This input field takes in a int value which will load an ace:dataTable with the entered in number of rows. This form also includes another commandButton that will open up an ace:dialog. This dialog is located in a different form. The dialog contains another input field which will update the underlying input field when the Ok button is clicked.
Initial testing found that this issue isn't seen with the ICEfaces EE 3.0.0 GA release.
Test Case scenario:
A page includes two forms, one that includes an inputText field and a commandButton. This input field takes in a int value which will load an ace:dataTable with the entered in number of rows. This form also includes another commandButton that will open up an ace:dialog. This dialog is located in a different form. The dialog contains another input field which will update the underlying input field when the Ok button is clicked.
Initial testing found that this issue isn't seen with the ICEfaces EE 3.0.0 GA release.
Generate random text/comment along the view state fixing code rendered by FixViewState.ScriptWriter. This forces the DOM diffing to send the code for non-ICEfaces requests since the client side view state fixing is not executed. The random comment is appended only when non-ICEFaces requests are detected.