DestroyLinkAction.endData type is not properly redefined about uml2

[khussey]

Thanks for issue report, @jerome-obeo .

It's been a while since I looked closely at this part of the code, but as I recall there are two ways that "duplicates" are processed when converting a UML model to an Ecore model - one detects cases where there is an explicit refines constraint in the metamodel and another which detects cases where there isn't such a constraint but a property is effectively redefined (typically because the type is being refined).

The classifier hierarchy is different for DestroyLinkAction and DurationConstraint. In the former case, there is an explicit redefinition only, whereas in the latter case there's both an implicit and explicit redefinition. The added complexity (and order in which explicit and implicit redefinitions are processed) for the latter case results in the intended type for property being located in an additional annotation whereas in the former case, the intended type is reflected in the duplicate eReference itself:

<contents xsi:type="ecore:EReference" name="endData" ordered="false" lowerBound="2" upperBound="-1" eType="#//LinkEndDestructionData" containment="true">

[jerome-obeo]

Thanks for the explanations.
We will then have to look at each duplicates annotation to check all of them.