Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336588 - CompletionComboRidget: NPE caused by "null" binding when Output Only is set
Summary: CompletionComboRidget: NPE caused by "null" binding when Output Only is set
Status: RESOLVED FIXED
Alias: None
Product: Riena
Classification: RT
Component: ridget (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: 3.0.0   Edit
Assignee: Elias Volanakis CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-08 02:42 EST by Elias Volanakis CLA
Modified: 2011-02-08 21:05 EST (History)
0 users

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 Elias Volanakis CLA 2011-02-08 02:42:48 EST 
When using a CompletionCombo / CompletionComboRidget the following code causes an NPE:

comboRidget.setOutputOnly(true);
comboRidget.updateFromModel();
// later
comboRidget.setOutputOnly(false);
comboRidget.updateFromModel(); // NPE because comboRidget#listBindingExternal == null

This is caused by a workaround we added earlier to handle some output-only edge case (351). Basically we are unbinding / rebinding internally. Will reconsider if we really need this.
Comment 1 Elias Volanakis CLA 2011-02-08 21:05:52 EST 
Resolved -- had to change the SelectionTypeEnforcer mechanism quite a bit. Tests and CComboSubModuleController seem to work ok though.