Describe the bug
When component-instances of the SystemComponentArchitecture model are changed from their ComponentDefinition name to a custom name, then the startstop hooks of these components are not properly deployed and triggered.
To Reproduce
Steps to reproduce the behavior:
Create a System with SystemComponentArchitecture model (as well as the TargetPlatform and Deployment models)
Instantiate at least one component in this model
Change the component-instance name to a different value
Deploy and execute the system
Error: the startstop hooks of the component with a custom name are not triggered
Expected behavior
Startstop hooks must use the component-instance names instead of the component-definition names.
Screenshots
If applicable, add screenshots to help explain your problem.
Toolchain version (and other specific settings) that you are using:
SmartMDSD Toolchain v3.7
Open JDK 8
Ubuntu Linux 16.04
...
Additional context
Add any other context about the problem here.
alex-lotz
commented
5 years ago
Describe the bug When component-instances of the SystemComponentArchitecture model are changed from their ComponentDefinition name to a custom name, then the startstop hooks of these components are not properly deployed and triggered.
To Reproduce Steps to reproduce the behavior:
Expected behavior Startstop hooks must use the component-instance names instead of the component-definition names.
Screenshots If applicable, add screenshots to help explain your problem.
Toolchain version (and other specific settings) that you are using:
Additional context Add any other context about the problem here.