ICEfaces
  1. ICEfaces
  2. ICE-6815

outputConnectionStatus does not work after ajax request

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1-Beta2
    • Fix Version/s: 3.0.RC1, 3.0
    • 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

      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

        Activity

        Grosbe Begr created issue -
        Ken Fyten made changes -
        Field Original Value New Value
        Salesforce Case []
        Fix Version/s 2.1 [ 10241 ]
        Assignee Priority P1
        Affects Version/s 2.1-Beta2 [ 10294 ]
        Assignee Mircea Toma [ mircea.toma ]
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #26344 Mon Nov 14 04:27:31 MST 2011 mircea.toma ICE-6815 Ignore exception thrown when the overlay element was previously removed from the document by a html/body level update.
        Files Changed
        Commit graph MODIFY /icefaces2/trunk/icefaces/core/src/main/javascript/blockui.js
        Hide
        Mircea Toma added a comment -

        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).

        Show
        Mircea Toma added a comment - 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).
        Mircea Toma made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Fix Version/s 3.0.RC1 [ 10300 ]
        Fix Version/s 3.0 [ 10241 ]
        Ken Fyten made changes -
        Fix Version/s 3.0 [ 10241 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Grosbe Begr
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: