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

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.

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

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

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.

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.

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