[news.eclipse.modeling.mdt.uml2] Re: Preserving uuid to xmi:id mapping c

[piergiuseppe.spinelli@xxxxxx (Piergiuseppe Spinelli)]

Kenn Hussey wrote:

Kenn, many thanks for your answer

> Piergiuseppe,

> Given that UUIDs are supposed to be globally unique (that's why they're 
> useful), I'm not sure it would be a good idea to assign the IDs of UML 
> elements to the resulting Ecore elements
Yes, I get your point. There could be different options here:
- setting in ecore alternative ids "generated" by the original ones in UML 
(i.e. adding a prefix) (at the end it is sufficient for the xmi:id to be 
unique in the document or in the context of use)
- do not use at all ids but URI fragments for mapping both the sides (as 
you sugest, if I undertend) .

The 2d options would be the most confortable one, but it seems to me it is 
a little sensible to some kinds of changes (i.e. how it behaves when e 
Class or Property is renamed, or a Class is moved to another package?)

(although it would be possible by 
> calling the conversion utility programmatically, using a custom resource to 
> load the Ecore model, and setting the XMI IDs of the Ecore elements based on 
> the UML element on which they were based). 

Could you address me to some doc or sample?

I would suggest producing a 
> mapping from UML element URI fragment (GUID) to Ecore element URI fragment 
> (name-based path) by processing the map that is returned after the 
> conversion and doing a reverse look-up to assign the desired IDs to UML 
> elements if/when the Ecore representation is ever converted back to UML...

Many thanks, I will do some test in this direction

> Kenn

> "Piergiuseppe Spinelli" <piergiuseppe.spinelli@xxxxxx> wrote in message 
> news:66dcd6dc89d0595eed9e551934c1185b$1@xxxxxxxxxxxxxxxxxx
> > Hi,
> >
> > I'm building an EMF based Eclipse application and I am currently using the 
> > existing UML to EMF converter from the ide.
> >
> > How can I preserve the uuids in the original uml file forcing them to be 
> > the xmi:id of the generated EClasses, and EStructuralFeatures?
> >
> > My UML tool assures to preserve the same uuid for the same element (even 
> > if it is, let's say, moved to another package) across different exports, 
> > so using uuids it is possible to perform more accurated comparisons of 
> > generated eCore models that, i.e., do not exange a moving operation for 
> > two unrelated operations (delete of the existing element and creation of a 
> > new one).
> >
> > Thank for any help