Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338187 - After dispose of a Node Shared Views can have null current controller
Summary: After dispose of a Node Shared Views can have null current controller
Status: RESOLVED FIXED
Alias: None
Product: Riena
Classification: RT
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.0.0.M6   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-25 04:40 EST by Nobody - feel free to take it CLA
Modified: 2011-05-03 10:16 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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)