[Issue 6196] Edits of messages on Sequence diagrams lead to exported XMI files with errors

http://argouml.tigris.org/issues/show_bug.cgi?id=6196






------- Additional comments from [email protected] Mon Oct 31 21:33:08 -0700 2011 -------
1. Download the attachment (id=2158) uploaded on Apr 23
2. Open the file "0.zargo" with ArgoUML 0.32
3. Double-click on untitledModel -> unattachedCollaboration -> Sequence Diagram
4. After the execution of message nextElement(), create a new call action 
starting from and ending to customer's lifeline (self-message). Make sure to 
move all messages after getMovie() a little bit lower to create the required 
space. The newly created message should be between messages nextElement() and 
getMovie().
5. Go to untitledModel -> Class Diagram and add a new operation named 
getCharge() to class Customer.
6. Go back to the Sequence diagram, right-click on the newly added message and 
select getCharge() as operation.
7. Export the diagrams into XMI.

By inspecting the XMI file, the activator of message getMovie() has remained the 
same despite the fact that the new message getCharge() was added before it (thus 
the return of the new message should be the activator of getMovie() message)
In other words, the xmi.idref references the return message of nextElement() as 
in the original version of the Sequence diagram. Its value should have been 
updated according to the new order of messages.
Such inconsistencies also appear when your re-order or delete existing messages.

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=448&dsMessageId=2869914

To unsubscribe from this list, e-mail: [[email protected]].
Please do not reply to this mail. Instead, add your comments in the issue.