Polymorphic events are used in SM without the correct mapping to UML integration exists

[gbatori1]

The EATF model (sent to Akos, Abel earlier) contains polymorphic events but there is no mapping defined for them in the UML Integration. The expected outcome of using the EATF model is an error from the Mode Compiler but by checking the UML Integration and CPP model I realized that the polymorphic events are mapped to normal XTClassEvents and used in subtype State Machines which is wrong behavior of the Model Compiler.

Example:
CallLeg21Established defined in the CallLeg Class and it is used for example in the subtype CircuitSwitchLeg Class.

Until the polymorphic events are introduced when only those XTClassEvents, which have corresponding UML Signals, are allowed to be assigned to a transition of a State Machine which have a corresponding UML Reception defined in the same UML Class as the State Machine. So during transformation the UML Signal, UML SignalEvent, UML Reception should be taken into consideration.

[abelhegedus]

@gbatori1 What is the expected behavior here?

We can either:

• transform the transition but not set the trigger
• ignore the transition altogether

In both cases, the output XTUML can be used for code generation. In my opinion the correct behavior would be to validate this on the UML model level, but no such validation is available.

[gbatori1]

The model was correct so UML validation won't show error. The problem is that the mentioned Signal, Reception, SignalEvent should be translated to a XTClassEvent + XTPolimorphicEvent instead of a single XTClassEvent. As this mapping is not yet implemented the expected behavior would be a transition without the trigger set.