|Re: expected behaviour of EMFCompare when Compare two UML models [message #1775446 is a reply to message #1775259]
||Mon, 30 October 2017 09:20
|| Philip Langer
Registered: March 2015
Location: Vienna, Austria
EMF Compare uses XMI:ID-based matching if those IDs are available. In Papyrus models those are available by default. So the expected behavior would be that they are matched if their IDs are exactly the same. If they aren't the same, e.g., because you have deleted the edge and created a new edge with exactly the same values, EMF Compare would show a deletion and an addition instead.
Is the XMI:ID of the edge goToEnd2 in version 1 the same as in version 2?
If the XMI:ID is different and "just" the model elements' values are the same -- because you deleted and recreated this element, EMF Compare would have to do a content-based match to be able to correctly match those elements, which EMF Compare doesn't do by default, mainly because it would significantly slow down the comparison for larger models. If you require that, you can implement your own matcher that tries to re-match unmatched elements based on their contents and select this matcher in the EMF Compare preferences instead of the default one.
Get professional Eclipse developer support:
[Updated on: Mon, 30 October 2017 09:21]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01665 seconds