Minimal requirements for a custom EMF model implementation
Few months ago, I was playing with EMF models under Eclipse. It turns out that writing an EMF implementation without reusing EMF library is not an easy task. I even submit one bug ( #295581). I thought EMF Editors were assuming too much about EMF values’ types.
For instance, the reflexive interface, i.e. using eGet, on multi-instance references must return an EList! Don’t ask me why I found in the code it could be relaxed… Anyway, Dave Steinberg suggests to write a guide for custom EMF implementation. I have not written one but I can provide you some unit-tests!
While writing my own EMF implementation, I carefully wrote some generic unittests for EMF custom implementation. You can download and use them freely under BSD/X11 like license.
One more thing, a custom model that pass those tests can be opened by the reflexive EMF editor, but you may have some errors if there is no property “name”. It should be nice for the editor to look at a property that is tagged as an id instead…
Ecore implementation guide unittests (154)