Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364816

Summary: [Sequence Diagram] - Combined fragments and gates
Product: [Modeling] Papyrus Reporter: Chokri Mraidha <Chokri.Mraidha>
Component: CoreAssignee: Chokri Mraidha <Chokri.Mraidha>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: yves.yang
Version: 0.9.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Bug fix
none
Correction sebastien.gerard: iplog+

Description Chokri Mraidha CLA 2011-11-25 05:52:32 EST 
A different gate is created for each message that have a combined fragment as source or destination. This is incompatible with the UML standard. The first gate should be used as a source by the second message. A dialog box allowing the selection of an existing gate on a combined fragment would allow the reuse of that gate.
Comment 1 Yves YANG CLA 2012-03-05 12:18:17 EST 
Created attachment 212083 [details]
Bug fix
Comment 2 Yves YANG CLA 2012-04-09 03:03:27 EDT 
Created attachment 213740 [details]
Correction
Comment 3 Chokri Mraidha CLA 2012-04-23 06:26:40 EDT 
I haven't succeded to model a message going from a combined fragment to a lifeline. Could you please describe how should I proceed?
Comment 4 Yves YANG CLA 2012-04-23 07:16:10 EDT 
Allow to model two messages(one that comes from the environment and created a gate on the combined fragment (done) and another one that reuses this gate to go to a lifeline). A dialog box for selecting an existing gate when creating a message from outside or a message starting with a combined fragment to go to a lifeline is required.

Before this patch, a new gate is created for the second message.
Comment 5 Chokri Mraidha CLA 2012-04-23 10:53:55 EDT 
Changes committed on the trunk r.7965
Comment 6 Chokri Mraidha CLA 2012-04-24 08:36:05 EDT 
Sharing gates problem is fixed. A problem for drawing messages from a combined fragment to a lifeline remains. It will be handled in https://bugs.eclipse.org/bugs/show_bug.cgi?id=377501