Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 338187

Summary: After dispose of a Node Shared Views can have null current controller
Product: [RT] Riena Reporter: Nobody - feel free to take it <nobody>
Component: UIAssignee: Nobody - feel free to take it <nobody>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: christian.campo
Version: unspecified   
Target Milestone: 3.0.0.M6   
Hardware: PC   
OS: All   
Whiteboard:

Description Nobody - feel free to take it CLA 2011-02-25 04:40:29 EST 
After dispose of a SubModuleNode in a shared view it is possible that the currentController of the view is null. Activation of a new node managed by the same view instance should lead to the creation of a new controller for the given node. If the currentController(null) == getControllerOfNode(null) there is no controller instance created.
Comment 1 Nobody - feel free to take it CLA 2011-02-25 04:41:43 EST 
SubModuleView#bind(final SubModuleNode node) doesn´t consider currentController == nulll && getController() == null after disposing a node and activating a new node instance
Comment 2 Nobody - feel free to take it CLA 2011-02-25 04:43:55 EST 
Fixed in SubModuleView#bind(final SubModuleNode node)