|UML profiles and MIWG Test Case 3 [message #628515]
||Mon, 14 June 2010 09:57
| Thomas Neustupny
Registered: October 2009
I'm playing with profiles and profile applications for some time, and it works quite well. But in my XMI files I have those xmi:Extension nodes that result from calling define() on a profile which adds ecore elements to the xmi files. Can this be avoided? Or, are there plans to make this obsolete and conform to the MIWG test case 3?
See: http://www.omgwiki.org/model-interchange/doku.php?id=test_ca se_3_revision_1
My first approach was to save profiles without define()ing them and to call define after loading them. This way I only have xmi extensions in my model and not in my profile xmi. But I consider this risky, because my models refer to ecore elements for the applied profiles. So if for the profile other xmi.ids are generated after loading them the next time, then my model that applies that profile will fail to load, because the ecore element references cannot be resolved anymore. This didn't happen so far, but I feel unsecure. Shall I better save a profile after calling define() instead?
Thanks for any hints!
Powered by FUDForum
. Page generated in 0.02369 seconds