Bugzilla – Full Text Bug Listing
| Summary: | [Sequence Diagram] Message creation dialog creates element outside model, exceptions during save | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Ansgar Radermacher <ansgar.radermacher> |
| Component: | Core | Assignee: | Mathieu Velten <mathieu.velten> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | ||
| Version: | 0.7.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
can I have the example model just before you try to create the message ? Thanks ! fixed in rev 4756 |
The message creation dialog can either connect a message with an existing signal or operation or create a new one. The problem is that the default owner of the new element is a package outside the model hierarchy, in my case the profile (MARTE) GRM (the model applied some MARTE sub-profiles and imports the MARTE library). If the user accepts the default package without careful observation, the signal/operation is created in a package that is outside the user model. As a result, subsequent save operations fail with an exception ("object ... is not contained in a resource"). If the error log view is not active, the user does not even realize that the save has failed, except that the model remains marked as dirty.