Summary
Matching connection ends to flow specification ends uses information from the declarative model which results in overly complicated code.
Expected behavior
The two methods isValidContinuation(...) should use information from the instance model, instead. Connections and flow specifications are instantiated before end to end flows, so everything needed is in the instance model, already.
Desktop (please complete the following information):
- OSATE Version: 2.9.1
- Operating System: LInux
Summary
Matching connection ends to flow specification ends uses information from the declarative model which results in overly complicated code.
Expected behavior
The two methods
isValidContinuation(...)should use information from the instance model, instead. Connections and flow specifications are instantiated before end to end flows, so everything needed is in the instance model, already.Desktop (please complete the following information):