Description Peter Cigehn 2015-03-10 12:23:28 EDT

Created attachment 251435 [details]
Example UML-RT model

If you validate a UML-RT model then a number of run-time exceptions gets generated. This has been reported in bug 461853. It then became clear that there seem to be a name mismatch of one of the constraints.

When validating the model, it is both logged in the error log and the in model validation view, that a constraint named "All operations of a capsule are sequential" is claimed to be disable (due to the runtime exceptions reported in bug 461853).

But when checking the latest version of the profile the constraint is actually named "All operations of a capsule are guarded" indicating some mismatch between which constraints are actually executed versus which constraints are defined in the profile.

Maybe some tooling related to constraints has not been generated/updated based on the latest version of the UML-RT profile.

Steps to reproduce:

1) Import the attached model and validate it
2) Check the error log and the model validation view for a message refering to a constraint named "All operations of a capsule are sequential".
3) Now import the UML-RT profile into this model to be able to check the constraints actually defined in the profile
4) Check the stereotype "Capsule" and its constraints. There the constraint is named "All operations of a capsule are guarded".

This name change was made in the latest version of the profile, so it seem like something has been missed to generate/update when it comes to the constraints.