|
|
|
|
|
|
|
Re: [Xcore] Reference properties are always unique in Ecore derived from Xcore [message #1789947 is a reply to message #1789942] |
Fri, 01 June 2018 06:57 |
Ed Merks Messages: 33140 Registered: July 2009 |
Senior Member |
|
|
I prefer not to go in circles on this subject. I've already pointed you at https://bugs.eclipse.org/bugs/show_bug.cgi?id=89325 which hightlights the fact that in no case is a non-unique EReference supported, i.e., not in the generator, not at runtime (even for dynamic models), and not in any of the downstream frameworks which assume uniqueness. Have you looked at this?
So at this point, the value of the unique feature on an EReference is actually kind of pointless, and as you note, the unique keyword on an XReference is also pointless. It's only really meaningfully implemented and supported for EAttributes and even there it's pointless unless the upper bound is > 1.
Ecore is intended to support its own runtime and the generator is designed to support this runtime as well. If you want to use Ecore for some other purpose (that doesn't use the EMF runtime) you can of course add your own arbitrary annotations (XAnnotations that map to EAnnotations) to capture any additional/different information you need/want in order to generate something unrelated to EMF/Ecore. Best you not expect Ecore to change at this point in its long life to conform to some other ideal that you might imagine...
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.02906 seconds