Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.6.2, 1.7DR#3
-
Component/s: Sample Apps
-
Labels:None
-
Environment:Browser: all except Opera
-
Affects:Sample App./Tutorial
Description
Open application in two windows. Close one of the windows, asynchronous clock in other window stops working.
Behavior is seen cross browser, and it will affect Opera as well if you open application in IE/FF and Opera, close the IE/FF window and clock in Opera will stop. However, IE/FF does not get effected if you close the Opera window.
Behavior is seen cross browser, and it will affect Opera as well if you open application in IE/FF and Opera, close the IE/FF window and clock in Opera will stop. However, IE/FF does not get effected if you close the Opera window.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Please take a look. I suspect we'll need to setup this demo like auction monitor in that a request scope bean is responsible for the renderable calls.
Show
Patrick Corless
added a comment - Please take a look. I suspect we'll need to setup this demo like auction monitor in that a request scope bean is responsible for the renderable calls.
Fixed the issue by moving all the clock related methods to a new request scope bean similar to how it is done in the Auction Monitor application. The major problem was the performCleanup method, it was calling the dispose method for the IntervalRenderer which was getting rid of all the renderer's, thus making other windows loose their renderer. For proper cleanup the only method that needs to be called is the remove method, which removes the renderer associated with that instance but leaves other ones running.
Show
Arran McCullough
added a comment - Fixed the issue by moving all the clock related methods to a new request scope bean similar to how it is done in the Auction Monitor application. The major problem was the performCleanup method, it was calling the dispose method for the IntervalRenderer which was getting rid of all the renderer's, thus making other windows loose their renderer. For proper cleanup the only method that needs to be called is the remove method, which removes the renderer associated with that instance but leaves other ones running.
Does this issue exist in previous ICEfaces versions, such as 1.6.1?