On 27/02/2013 9:13 AM, Matthias N wrote:
> I've two Ecore models: A.ecore and B.ecore
> A.ecore references some elements in B.ecore
> When I open A.ecore it automatically loads B.ecore as well, that's fine:
> Okay, now I copy those two ecore files into another location
> (new-folder) of my workspace and try to open them again:
It looks like A.ecore's serialization contains absolute URIs for its
references to B.ecore. That's not normally how EMF's tools serialize
models. Normally I would expect references to B.ecore to look like
"B.ecore#<fragment>" but probably you have
Is that the case?
> The path of B.ecore didn't get updated?!, Hence A.ecore can't load the
> model elements in B.ecore.
> Any ideas how to solve this?
Which tool did you use to edit/create these two models? If you edit
A.ecore and B.ecore with the Sample Ecore Editor (make some change and
then change it back so you can actually save the result), what do the
URIs in the serialization look like?
Be sure that you use an absolute URI for each resource you create. That
will ensure that when you save them, references between them will be
relative URIs whenever possible.
On 27/02/2013 11:55 AM, Matthias N wrote:
> Hi Ed,
> we generate the Ecore models:
> Below, there is a code snippet of A.ecore:
> I guess the URI of B.ecore should be sth like
> /B.ecore#// ?