| Summary: | Stereotypes applied to association member ends spanning multiple models lost after save | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] MDT.UML2 | Reporter: | Alexander Weickmann <alexander.weickmann> | ||||
| Component: | Core | Assignee: | UML2 Inbox <mdt-uml2-inbox> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P2 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Alexander Weickmann
Created attachment 204739 [details]
JUnit Plugin Test Case
I just tried this interactively with the UML editor and it worked as expected (correctly). Taking a look at your test case code, I see at least two problems: 1. You are creating more than one resource set; in order to properly create relations between two resources they must belong to the same resource set. 2. You are only saving model-2 after applying the stereotypes, whereas you must save both models because each of the navigable member ends of the association (which belong to classes in different resources) have been modified. Please feel free reopen this bug if you still have problems once you've corrected your code. |