Java Interface Realization and Generalization is sometimes not propagated to UML

[SofiaAnanieva]

When propagating changes into a Java model, in some cases, the interface realization and generalization elements are not correctly propagated to UML.
The propagation works when the referenced Java class (or interface) already has a corresponding UML element (i.e., their creation change has already been applied).
It does not work when the referenced Java class (or interface) does not yet have a corresponding UML element (i.e., their creation change will be executed later).

A simple reproducing example would be two Java classes A and C that both extend class B. Assuming the classes are parsed and their creation propagated in alphabetical order, the result will be that in UML the class C correctly extends B but class A incorrectly does not extend B.

A fix would be to let the reaction create a stub UML class (or interface) and add it as a correspondence to the referenced Java class (or interface) in cases where it does not exist yet.