ICEfaces
  1. ICEfaces
  2. ICE-5667

PushRenderer.removeCurrentSession has no effect

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 2.0-Alpha2
          • Fix Version/s: 2.0-Beta1, 2.0.0
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            ICEfaces 2.0
          • ICEsoft Forum Reference:
          • Workaround Exists:
            Yes
          • Workaround Description:
            Hide
            A workaround is to call addCurrentSession() with an otherwise unused group so that the session is always a member of at least one group (even if that group does not receive push updates).
            Show
            A workaround is to call addCurrentSession() with an otherwise unused group so that the session is always a member of at least one group (even if that group does not receive push updates).

            Description

            I'm having quite a time trying to get PushRenderer functionality to work properly. Specifically, when calling removeCurrentSession("group") to stop render updates to "group" it appears to do nothing.

              Activity

              Ascending order - Click to sort in descending order
              Ted Goddard created issue -
              Ted Goddard made changes -
              Field Original Value New Value
              Salesforce Case []
              Fix Version/s 2.0-Alpha3 [ 10032 ]
              Ted Goddard made changes -
              Assignee Ted Goddard [ ted.goddard ]
              Hide
              Permalink
              Ted Goddard added a comment -

              removeCurrentSession() is working as expected, however, "lazy" push initialization is removing itself too aggressively from the page and it may appear that the feature is not functional. For instance, in a simple test with "auction" removeCurrentSession() was invoked, but the push updates for the clock continued and the page appeared to blink briefly. This is caused by the push initialization JavaScript being removed from the page, resulting in a DOM diff that includes the HEAD or the BODY, causing a page reload. The page reload triggers the construction of a new ViewScope bean, adding the session to the "auction" group again.

              A workaround is to call addCurrentSession() with an otherwise unused group so that the session is always a member of at least one group (even if that group does not receive push updates).

              Show
              Ted Goddard added a comment - removeCurrentSession() is working as expected, however, "lazy" push initialization is removing itself too aggressively from the page and it may appear that the feature is not functional. For instance, in a simple test with "auction" removeCurrentSession() was invoked, but the push updates for the clock continued and the page appeared to blink briefly. This is caused by the push initialization JavaScript being removed from the page, resulting in a DOM diff that includes the HEAD or the BODY, causing a page reload. The page reload triggers the construction of a new ViewScope bean, adding the session to the "auction" group again. A workaround is to call addCurrentSession() with an otherwise unused group so that the session is always a member of at least one group (even if that group does not receive push updates).
              Ted Goddard made changes -
              Workaround Description A workaround is to call addCurrentSession() with an otherwise unused group so that the session is always a member of at least one group (even if that group does not receive push updates).
              Workaround Exists [Yes]
              Salesforce Case []
              Hide
              Permalink
              Ted Goddard added a comment -

              removeCurrentSession() should not result in page changes that require a full page update to apply.

              Show
              Ted Goddard added a comment - removeCurrentSession() should not result in page changes that require a full page update to apply.
              Ken Fyten made changes -
              Salesforce Case []
              Assignee Priority P1
              Assignee Ted Goddard [ ted.goddard ] Mircea Toma [ mircea.toma ]
              Ted Goddard made changes -
              Salesforce Case []
              Fix Version/s 2.0-Beta [ 10231 ]
              Fix Version/s 2.0-Alpha3 [ 10032 ]
              Hide
              Permalink
              Ted Goddard added a comment -

              This may be due to icepush.js being removed from the head immediately when no groups are present.

              Show
              Ted Goddard added a comment - This may be due to icepush.js being removed from the head immediately when no groups are present.
              Hide
              Permalink
              Mircea Toma added a comment -

              This issue was fixed by the resolution of ICE-5707. When push is enabled or disabled lazily it is not forcing a page reload anymore.

              Show
              Mircea Toma added a comment - This issue was fixed by the resolution of ICE-5707 . When push is enabled or disabled lazily it is not forcing a page reload anymore.
              Mircea Toma made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              Ken Fyten made changes -
              Fix Version/s 2.0.0 [ 10230 ]
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]
              Assignee Priority P1

                People

                • Assignee:
                  Mircea Toma
                  Reporter:
                  Ted Goddard
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: