|
| Re: Meaning of AddReferenceValue in EMF Compare [message #111535 is a reply to message #111493] |
Fri, 01 February 2008 00:23  |
|
This is a multi-part message in MIME format.
--------------040301000107080605020608
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Renata,
I can't really understand why we would detect differences in the
references... "AddReferenceValue" represent an addition to a
multi-valued reference. in this case, the first of the two you supplied
can be read as :
"<rightAddedTarget> has been added to the list of values of the
reference "supplier" in the Dependency <_amT65ZOiEdyH-dJfEVLHtA>".
This last unreadable thing is the XMI ID (or ID attribute if one is
defined in your models) of the element which we detected a change on.
This difference we detected could come from the way you've loaded the
two models that need be compared. We have often assumed the two models
would be loaded in the same resourceSet and have compared references
values with "Object#equals()" ... which should probably be changed in an
equality test between the two values' URIs.
For now, you should load both models to compare in the same resourceSet
(see the "load" methods we defined in
"org.eclipse.emf.compare.util.ModelUtils").
Cheers,
Laurent Goubet
Obeo
Renata Roginsky a
|
|
|
| Re: Meaning of AddReferenceValue in EMF Compare [message #615362 is a reply to message #111493] |
Fri, 01 February 2008 00:23 |
|
This is a multi-part message in MIME format.
--------------040301000107080605020608
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Renata,
I can't really understand why we would detect differences in the
references... "AddReferenceValue" represent an addition to a
multi-valued reference. in this case, the first of the two you supplied
can be read as :
"<rightAddedTarget> has been added to the list of values of the
reference "supplier" in the Dependency <_amT65ZOiEdyH-dJfEVLHtA>".
This last unreadable thing is the XMI ID (or ID attribute if one is
defined in your models) of the element which we detected a change on.
This difference we detected could come from the way you've loaded the
two models that need be compared. We have often assumed the two models
would be loaded in the same resourceSet and have compared references
values with "Object#equals()" ... which should probably be changed in an
equality test between the two values' URIs.
For now, you should load both models to compare in the same resourceSet
(see the "load" methods we defined in
"org.eclipse.emf.compare.util.ModelUtils").
Cheers,
Laurent Goubet
Obeo
Renata Roginsky a
|
|
|
Powered by
FUDForum. Page generated in 0.02581 seconds
] 
Search
Help
Register
Login
Home
