Uploaded image for project: 'Spring Roo'
  1. Spring Roo
  2. ROO-1310

Stopping an ActivityManager from a PlaceChangeEvent might cause an NPE

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Deferred
    • Affects Version/s: 1.1.0.M3
    • Fix Version/s: None
    • Component/s: GWT
    • Labels:
      None

      Description

      "Stopping" an ActivityManager, by calling setDisplay(null), from a PlaceChangeEvent.Handler will cause an NPE in the ActivityManager's own PlaceChangeEvent.Handler, if it hasn't already be called. This is because unregistering the handler (in updateHandlers, called from setDisplay) will take effect only after the current event has been dispatched to all the handlers; and ActivityManager doesn't check that display is non-null in onPlaceChange. The current activity should probably be "correctly" stopped, and no new activity be started (ideally not even asking the ActivityMapper).

        Activity

        Hide
        rchandia@google.com Rodrigo Chandia added a comment -
        Show
        rchandia@google.com Rodrigo Chandia added a comment - Moved to GWT Issue Tracker at http://code.google.com/p/google-web-toolkit/issues/detail?id=5375

          People

          • Assignee:
            rjrjr@google.com Ray Ryan
            Reporter:
            t.broyer Thomas Broyer
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 0.25d
              0.25d
              Remaining:
              Remaining Estimate - 0.25d
              0.25d
              Logged:
              Time Spent - Not Specified
              Not Specified