Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1-Beta2
-
Component/s: None
-
Labels:None
-
Environment:Tomcat 7.0.4 and/or Tomcat 7.0.12
Icefaces 2.0.0 or/and Icefaces 2.0.1
Mojarra 2.0.4 or/and Mojarra 2.1.0
-
Assignee Priority:P1
-
ICEsoft Forum Reference:
Description
A navigation from a view rendering via Ajax request, does not trigger the "busy" indicator used by the component outputConnectionStatus.
Test to reproduce: (JSF2.0)
page 1 => page 2 with configuration <navigation-case>
<from-outcome>navTopage2</from-outcome>
<to-view-id>/page2.xhtml</to-view-id>
<redirect/>
</navigation-case>
then page 2 => page 3: outputConnectionStatus woks well
without "redirect" option, outputConnectionStatus does not triggered
Test to reproduce: (JSF2.0)
page 1 => page 2 with configuration <navigation-case>
<from-outcome>navTopage2</from-outcome>
<to-view-id>/page2.xhtml</to-view-id>
<redirect/>
</navigation-case>
then page 2 => page 3: outputConnectionStatus woks well
without "redirect" option, outputConnectionStatus does not triggered
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
This issue is triggered during navigation when a html/body level update is applied to the document. The overlay rendered by the "blockUIOnSubmit" feature is erased by the update, an error is thrown when the orphaned overlay element is used causing the submit notification to fail.
The fix just ignores the exception thrown when "blockUIOnSubmit" feature tries to remove the orphaned overlay element (the element was removed already).