Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Alpha2
-
Component/s: Framework
-
Labels:None
-
Environment:ICEfaces 2.0
-
ICEsoft Forum Reference:
-
Workaround Exists:Yes
-
Workaround Description:
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.
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).