Eclipse Community Forums: Compare » Compare nodes with different parent hierarchy

Help

Home

Home » Modeling » Compare » Compare nodes with different parent hierarchy

Show: Today's Messages :: Show Polls :: Message Navigator

Compare nodes with different parent hierarchy [message #1695786]

Tue, 19 May 2015 09:32

Kai Schreiber

Messages: 4
Registered: May 2015

Junior Member

Hi,

I try to compare two nodes where one node is additionally contained in another node.
Apart from this the two nodes and their sub-trees are equal and I expect to get no differences.
The reason seems to be the IEqualityHelper in the EditionDistance where the URI-distance is used.

Here is some sample code:

Document document1 = createDocument();
Document document2 = createDocument();

Project project = ModelFactory.eINSTANCE.createProject();
project.getDocuments.add(document1);

IEObjectMatcher matcher = DefaultMatchEngine.createDefaultEObjectMatcher(UseIdentifiers.NEVER);
IComparisonFactory comparisonFactory = new DefaultComparisonFactory(new DefaultEqualityHelperFactory());
IMatchEngine.Factory matchEngineFactory = new MatchEngineFactoryImpl(matcher, comparisonFactory);
matchEngineFactory.setRanking(20);
IMatchEngine.Factory.Registry matchEngineRegistry = new MatchEngineFactoryRegistryImpl();
matchEngineRegistry.add(matchEngineFactory);
EMFCompare comparator = EMFCompare.builder().setMatchEngineFactoryRegistry(matchEngineRegistry).build();
IComparisonScope scope = new DefaultComparisonScope(document1, document2, null);
Comparison result = comparator.compare(scope);

List<Diff> diffs = result.getDifferences();

assertEquals(0, diffs.size()); // Fails

Maybe I've missed something. Is there a setting to ignore the parent nodes?

Regards,
Kai

Report message to a moderator

Re: Compare nodes with different parent hierarchy [message #1696398 is a reply to message #1695786]

Tue, 26 May 2015 09:49

Andreas Mayer

Messages: 11
Registered: April 2014

Junior Member

Instead of calling DefaultMatchEngine.createDefaultEObjectMatcher(), create an IdentifierEObjectMatcher that delegates to an ProximityEObjectMatcher and give it an ID function that returns the same id (e.g. "root") for your two nodes and null for all other objects.

Thus configured, the IdentifierEObjectMatcher will add a match for your two nodes (without computing any edit distance, because they have the same id) and then delegate the matching of their children to the ProximityEObjectMatcher (because they have no ids).

Report message to a moderator