Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313440 - NullPointerException when invalid default value literal of EENum type
Summary: NullPointerException when invalid default value literal of EENum type
Status: CLOSED WORKSFORME
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.core (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL: http://bugs.eclipse.org/bugs/show_bug...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-18 16:50 EDT by Stefan Winkler CLA
Modified: 2010-06-29 09:20 EDT (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 Stefan Winkler CLA 2010-05-18 16:50:47 EDT 
see Bug 306998

the Testcase of this bug fails with the MemStore as well. 

Maybe it would be a good idea to check for invalid default literals on the client side or at some other more central place. Either that or the same bug has to be fixed in the MEMStore as well.

I've disabled the TestCase for the MemStore for now and added a FIXME comment.
Comment 1 Stefan Winkler CLA 2010-05-18 17:00:12 EDT 
argh. One shouldn't open bugs hastily before analyzing the real error.
The MemStore handles invalid literals by silently assigning NULL, which is ok. It's just not what the testcase exepected.

So the behavior is ok. Removed the FIXME comment from the code - the skipConfigs remain in place - and resolving this bug as worksforme.
Sorry for the mess :-(
Comment 2 Eike Stepper CLA 2010-06-29 04:44:24 EDT 
Closing