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.
Difference between revisions of "EMF Compare/Specifications/MatchEngineExtension"
(New page: = Evolution Specification: Provide a match engine extension mechanism = Current status is '''DRAFT''' == Preamble == It enables to provide his own match engine implementation. * ==...) |
|||
| Line 12: | Line 12: | ||
== Introduction == | == 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. | |
| Line 19: | Line 19: | ||
We propose to provide a match engine extension mechanism. | We propose to provide a match engine extension mechanism. | ||
| − | Any extension will be able to contribute a match engine | + | 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. | 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. | 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. | ||
| Line 28: | Line 28: | ||
=== Metamodel Changes === | === Metamodel Changes === | ||
| + | |||
| + | N/A | ||
=== User Interface Changes === | === User Interface Changes === | ||
Revision as of 11:12, 12 March 2013
Evolution Specification: Provide a match engine extension mechanism
Current status is DRAFT
Preamble
It enables to provide his own match engine implementation.
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