|Re: Controlling eSuperTypes URI in XMI Serialization [message #431901 is a reply to message #431891]
||Tue, 28 July 2009 23:11
| Ed Merks
Registered: July 2009
Be sure that the URI of every Resource is always absolute. E.g.,
Derek Palma wrote:
> I am serializing an ecore model generated dynamically. (I am not sure
> if this is even relevant)
> For the resource I set the URI to model/instance.ecore which is
> relative to my project in Eclipse.
> When I lookin the file I see
> eSuperTypes="model/instance.ecore#MyClass" even though MyClass is
> defined as an EClassifier in the same file.
> I am wondering why the serialization needs to include the whole
> relative path. It causes trouble when I load the model with different
> relative paths. I presume I need to have relative path agnostic URIs
> and I should somehow tell the serialization not to do this or to use
> the NS URI of the file containing the EClassifier. However, my current
> situation seems to represent the trivial case since the EClassifier is
> contained in the same file.
> What is the right why to address this issue? I would think any kind of
> relative path would not be good.
Professional Support: https://www.macromodeling.com/
Powered by FUDForum
. Page generated in 0.01844 seconds