ICEfaces
  1. ICEfaces
  2. ICE-2815

GroupAsyncRenderer throws NullPointerException during dispose

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.7Beta1
          • Fix Version/s: 1.7RC1, 1.7
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            Any

            Description

            The GroupAsyncRenderer can throw a NullPointerException when DisposableBeans are used. This occurs when multiple beans are using the same renderer (e.g. clock) and the first call to dispose causes the internal reference to the RenderManager to be set to null. Subsequent calls to dispose of the renderer by DisposableBeans will cause the NPE.

              Activity

              Ascending order - Click to sort in descending order
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #15924 Tue Mar 04 14:32:17 MST 2008 deryk.sinotte ICE-2815: do not set renderManager reference to null or subsequent dispose calls will cause an NPE
              Files Changed
              Commit graph MODIFY /icefaces/trunk/icefaces/core/src/com/icesoft/faces/async/render/GroupAsyncRenderer.java
              Deryk Sinotte created issue -
              Deryk Sinotte made changes -
              Field Original Value New Value
              Assignee Deryk Sinotte [ deryk.sinotte ]
              Hide
              Permalink
              Deryk Sinotte added a comment -

              I've removed the statement that sets the renderManager reference to null in GroupAsyncRenderer.dispose. There's not really a strict need to do this and subsequent dispose() calls should do the right thing. Resolving as fixed.

              Show
              Deryk Sinotte added a comment - I've removed the statement that sets the renderManager reference to null in GroupAsyncRenderer.dispose. There's not really a strict need to do this and subsequent dispose() calls should do the right thing. Resolving as fixed.
              Deryk Sinotte made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Fix Version/s 1.7 [ 10080 ]
              Resolution Fixed [ 1 ]
              Ken Fyten made changes -
              Fix Version/s 1.7RC1 [ 10123 ]
              Fix Version/s 1.7 [ 10080 ]
              Ken Fyten made changes -
              Fix Version/s 1.7 [ 10080 ]
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]
              Assignee Deryk Sinotte [ deryk.sinotte ]

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Deryk Sinotte
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: