Eclipse Community Forums: Papyrus » Sequence Diagram, messages as ordered set

Home » Modeling » Papyrus » Sequence Diagram, messages as ordered set

Sequence Diagram, messages as ordered set [message #1006572]

Thu, 31 January 2013 15:24

Eclipse User

I have noticed that when changing the sequence of messages in an sequence diagram, the changes in the diagram are not reflected in the messages order within the model. Thus I guess that, during a possible transformation, I will not get the messages in the order specified in the diagram. The same thing holds for the message occurrence specifications in the Interaction.fragment

what am I missing?

I am using

Eclipse Modeling Tools

Version: Juno Service Release 1
Build id: 20120920-0800

with

Papyrus 0.9.1.v201209290809

On a Mac Os 10.7.5

Re: Sequence Diagram, messages as ordered set [message #1006623 is a reply to message #1006572]

Fri, 01 February 2013 04:07

Eclipse User

Hello Andrea,

A lot of work is being done on the sequence diagram currently. I haven't checked the whole list of Bugzilla tasks related to this diagram, but it may have been fixed in the last Juno builds.

Regards,
Camille

Re: Sequence Diagram, messages as ordered set [message #1006848 is a reply to message #1006572]

Sat, 02 February 2013 15:40

Eclipse User

Andrea,

the order of the message is completely irrelevant in sequence diagrams. They
are ordered by the MessageOccurrenceSpecifications that cover the lifelines
and combine the messages; these are eventually ordered through
Interaction.fragment on purpose.

>The same thing holds for the message occurrence specifications in the
>Interaction.fragment

This confuses me; I just tried it with the last Papyrus version 0.9.1 and
the order in Interaction.fragments is updated, when I moved messages in the
diagram. Be aware that the current implementation of sequence diagrams in
Papyrus only react on moving OccurrenceSpecifications and its subclasses
(like MessageOccurrenceSpecification). If you, e.g., move CombinedFragments
or StateInvariants, the order of fragments will not correspond to the
diagram. Fortunately, the correct order is recalculated every time you touch
an OccurrenceSpecification. So, when you wildly move things in the sequence
diagram, just touch an OccurrenceSpecification before running your
transformation.

Regards,
Marc-Florian

"Andrea Sindico" schrieb im Newsbeitrag
news:keejtl$cgn$1@xxxxxxxxe.org...

I have noticed that when changing the sequence of messages in an sequence
diagram, the changes in the diagram are not reflected in the messages order
within the model. Thus I guess that, during a possible transformation, I
will not get the messages in the order specified in the diagram. The same
thing holds for the message occurrence specifications in the
Interaction.fragment

what am I missing?

I am using

Eclipse Modeling Tools

Version: Juno Service Release 1
Build id: 20120920-0800

with

Papyrus 0.9.1.v201209290809

On a Mac Os 10.7.5
--
Follow me on Twitter https://twitter.com/andreasindico

Re: Sequence Diagram, messages as ordered set [message #1006964 is a reply to message #1006848]

Sun, 03 February 2013 04:21

Eclipse User

Hi,
the problem is that, at least in my configuration, changes to the diagram are not reflected in the message occurrence specifications order in the model.
I am now using the 0.9.1.v201210051358 Papyrus version

[Updated on: Sun, 03 February 2013 04:22] by Moderator

Re: Sequence Diagram, messages as ordered set [message #1007956 is a reply to message #1006964]

Fri, 08 February 2013 08:37

Eclipse User

the same example works (the message occurrences order is updated in the interaction fragment within the model) when executed with the same configuration (Eclipse Juno + Papyrus)on Windows. I therefore guess the problem may be related to the Mac Os environment.

Re: Sequence Diagram, messages as ordered set [message #1008576 is a reply to message #1007956]

Wed, 13 February 2013 02:20

Eclipse User

Andrea,

okay, that's good to know and reassures me.

As I said, be aware that only the shifting of OccurrenceSpecifications
update the order; if you move CombinedFragments or StateInvariants, the
Interaction.fragments list won't be updated ever. In such a case, simply
touch a OccurrenceSpecification by touching and slightly moving a message
and the list order we be recalculated.

Regards,
Marc-Forian

"Andrea Sindico" schrieb im Newsbeitrag
news:kf2v2a$sbo$1@xxxxxxxxe.org...

the same example works (the message occurrences order is updated in the
interaction fragment within the model) when executed with the same
configuration (Eclipse Juno + Papyrus)on Windows. I therefore guess the
problem may be related to the Mac Os environment.
--
Follow me on Twitter https://twitter.com/andreasindico

Re: Sequence Diagram, messages as ordered set [message #1019071 is a reply to message #1008576]

Thu, 14 March 2013 21:32

Eclipse User

Hello,

I'm using Papyrus on Indigo. I'm also having a problem with the order of MessageOccurenceSpecification fragments in a combined fragment (seq). Was this a bug in Indigo that was fixed on Juno?

Visually, my sequence diagram has a several synchronous messages, in order top to bottom. However, the MessageOccurenceSpecification fragments are not in the corresponding order.

Any ideas? I can email the relevant files (.di, .notation, .uml) to anyone who is willing to look into this. Any help would be appreciated.

Regards,

-Steve Solomon
stev.solomon@gmail.com

Re: Sequence Diagram, messages as ordered set [message #1019126 is a reply to message #1019071]

Fri, 15 March 2013 00:53

Eclipse User

I also tried it under Juno MDT, build 0.9.2.v201302131112.

Same issue. Fragments of type MessageOccurenceSpecification are not in diagram order in the .uml file.

Please see the attached .uml, .di, and .notation files.

Thanks,

-Steve Solomon

Attachment: model.di
(Size: 0.67KB, Downloaded 303 times)
Attachment: model.notation
(Size: 24.28KB, Downloaded 293 times)
Attachment: model.uml
(Size: 10.11KB, Downloaded 293 times)
Attachment: .project
(Size: 0.22KB, Downloaded 340 times)

Previous Topic:	Information of the Diagram Generation Component
Next Topic:	Problem loading UML file in Papyrus

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 22 14:23:46 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter