[DIRSTUDIO-1047] No BrowserViewUniversalListener.connectionOpened null checks

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-M8 (2.0.0.v20130628)
• Fix Version/s: 2.0.0-M9 (2.0.0.v20150606-M9)
• Component/s: studio-ldapbrowser
• Assignee: Unassigned
• Reporter: Paul Richardson
• Created: 14/May/15 11:43
• Updated: 18/Apr/20 11:40
• Resolved: 26/May/15 20:59

Description

BrowserViewUniversalListener.connectionOpened is fired on the opening of a connection. In my case, the connection being opened comes from a wizard displaying the BrowserWidget rather than the BrowserView. In this use-case, the BrowserConnection used in the wizard is only temporary so not added to the BrowserCorePlugin ConnectionManager.

Consequently, opening a connection in the wizard while the BrowserView is also open, the latter's BrowserViewUniversalListener.connectionOpened() is fired and a NPE results.

A check can be added to assert that the BrowserConnection fetched from the ConnectionManager is not null. Only if not null should the BrowserView viewer be refreshed.