Service Registrations : Handle ambiguity caused by generated EMF "Impl" types
org.fortiss.af3.allocation.internal.AllocationService.EMFTypeMap
provides a base class to map an EMF type to a target type. For a given
EClass
Foo
, the
map considers the generated interface class Foo
and the corresponding
implementation class FooImpl
identical.
In the case of af3.allocation, this map was needed to correctly handle requests to the service via the API:
- During the setup phase of the service, typically the generated
interface class
Foo
is used. - When querying the during runtime based on a given model element,
typically the generated implementation class
FooImpl
is used.
In this ticked, it
- should be investigated if the approach is required for other services, and whether there are better implementation alternatives than comparing class names.
- should be checked if the issue because more relevant due to the API based service registration that has replaced the extension point based registration.
(from redmine: issue id 3319, created on 2018-03-06, closed on 2019-01-14)
- Relations:
- blocks #3337 (closed)