ICEfaces
  1. ICEfaces
  2. ICE-8840

icecore:refresh hitting multiple pages

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: EE-3.0.0.GA_P01, 3.2
          • Fix Version/s: EE-3.2.0.GA, 3.3
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            Tomcat 7.0.14, Firefox, Chrome, IE
          • Assignee Priority:
            P1

            Description

            To reproduce:
            1. uncomment icecore:refresh tag on start.xhtml page in attached source code
            2. run sample application
            3. Open for example start.xhtml in Chrome & start2.xhtml in IE or Firefox

            ISSUE: After some time specified in the interval parameter of the tag you should be able to see page refreshes in both browsers due to the presence of icecore:refresh tag on start.xhtml page. (request scoped beans will be re-initialized in both browsers)

            Setting interval="0" duration="0" for the tag does not stop this behavior

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Ted Goddard added a comment -

              Assigning to Jack (to work on after the ICEpush backoff and cloud push implementations).

              Show
              Ted Goddard added a comment - Assigning to Jack (to work on after the ICEpush backoff and cloud push implementations).
              Hide
              Permalink
              Ted Goddard added a comment -

              Please attach a .war file that runs on tomcat and assign back to me.

              Show
              Ted Goddard added a comment - Please attach a .war file that runs on tomcat and assign back to me.
              Hide
              Permalink
              Evgheni Sadovoi added a comment -

              Unzip case11783 file to get deployable .war file

              Show
              Evgheni Sadovoi added a comment - Unzip case11783 file to get deployable .war file
              Hide
              Permalink
              Ted Goddard added a comment -

              Both start.jsf and start2.jsf are being refreshed: this appears to be working as expected.

              Show
              Ted Goddard added a comment - Both start.jsf and start2.jsf are being refreshed: this appears to be working as expected.
              Hide
              Permalink
              Ted Goddard added a comment -

              The pages are as follows:

              • start.jsf contains an icecore:refresh tag
              • start2.jsf does not contain an icecore:refresh tag

              When start2.jsf is loaded after start.jsf (even in a different browser) start2.jsf will be automatically refreshed.

              Show
              Ted Goddard added a comment - The pages are as follows: start.jsf contains an icecore:refresh tag start2.jsf does not contain an icecore:refresh tag When start2.jsf is loaded after start.jsf (even in a different browser) start2.jsf will be automatically refreshed.
              Hide
              Permalink
              Ted Goddard added a comment -

              RefreshHandler is implemented as an Application Scope SystemEvent listener, causing it to be incorrectly applied to all pages once activated.

              Show
              Ted Goddard added a comment - RefreshHandler is implemented as an Application Scope SystemEvent listener, causing it to be incorrectly applied to all pages once activated.
              Hide
              Permalink
              Ted Goddard added a comment -

              The following fix is checked in: rather than add a JavaScript output component from a global SystemEventListener, the TagHandler for this feature is now adding a transient component directly to the ViewRoot. The TagHandler has been modified so that different instances should pick up different configuration parameters, but this suspected bug in the original implementation has not been confirmed or tested. The fixed implementation has been verified to work as desired with the provided test case.

              Show
              Ted Goddard added a comment - The following fix is checked in: rather than add a JavaScript output component from a global SystemEventListener, the TagHandler for this feature is now adding a transient component directly to the ViewRoot. The TagHandler has been modified so that different instances should pick up different configuration parameters, but this suspected bug in the original implementation has not been confirmed or tested. The fixed implementation has been verified to work as desired with the provided test case.

                People

                • Assignee:
                  Evgheni Sadovoi
                  Reporter:
                  Evgheni Sadovoi
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: