ST6RI-863 Actions in a case will cause a crash of the visualization (PlantUML) by himi · Pull Request #667 · Systems-Modeling/SysML-v2-Pilot-Implementation
Since VCase cannot handle actions properly, the model below causes a crash.
case c1 {
first start;
then action a;
}
This PR fixes this issue and lets the visualizer properly render actions as well as cases.
seidewitz
changed the title
Actions in a case will cause a crash of the visualization (PlantUML)
ST6RI-863 Actions in a case will cause a crash of the visualization (PlantUML)
Opps, it is because UseCases::UseCase::start redefines Actions::Action::start and the current code uses:
return "Actions::Action::start".equals(f.getQualifiedName());
Is there any good utility function to check if the element belongs to start or done? If not, I will simply compare the qualified name with UseCases::UseCase::start as well.
Opps, it is because
UseCases::UseCase::startredefinesActions::Action::startand the current code uses:return "Actions::Action::start".equals(f.getQualifiedName());Is there any good utility function to check if the element belongs to
startordone? If not, I will simply compare the qualified name withUseCases::UseCase::startas well.
If f is a Type, then you can check f.specializesFromLibrary("Actions::Action::start").
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters

