Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EMF Compare/Specifications/MatchEngineExtension
Evolution Specification: Provide a match engine extension mechanism
Current status is DRAFT
Preamble
It enables to provide his own match engine implementation.
- Bug 403055 - Provide a match engine extension mechanism
Introduction
The actual mechanism to provide his own match engine is not very flxible. An extension point mechanism will be useful to alllow users to provide their own match engines.
Detailed Specification
We propose to provide a match engine extension mechanism.
Any extension will be able to contribute a match engine. The match engine registry will be queried each time a match engine will about to be performed. A match engine contribution will provide its own predicate that will need to be verified before it is considered to be a valid candidate to execute the comparison. It will also have a ranking in order to choose over multiple possible match engine.
Standard match engine operations will be rewritten with the lowest ranking in order to be overrideable.
Backward Compatibility and Migration Paths
Metamodel Changes
N/A
User Interface Changes
Documentation Changes
This documentation will have to be updated:
- New and Noteworthy
- Developer Guide
Tests and Non-regression strategy
Implementation choices and tradeoffs
N/A