Description Ernesto Posse 2015-05-01 11:51:03 EDT

(This is mostly relevant to UML-RT, but the PapyrusRT bugzilla doesn't have components yet, so I'm reporting it here)

In UML-RT transitions cannot "cross state boundaries", this is, having a transitions whose source and target are not in the same region. However Papyrus allows you to do that. There should be a visual constraint on this.

This has another consequence: moving states to a different region results in an incorrect model, with the transitions remaining in the region they were before moving the states.

Steps to reproduce
------------------

1. Create a state machine diagram
2. Add three states State1, State2 and State3 in the top region (Region1), and a transition t1 from State2 to State3.
3. Add a region to State1 (State1.Region1)
4. Select State2 and State3.
5. Drag and drop State2 and State3 to State1.Region1.

Result
------

The model structure is

StateMachine1
+- Region1
   +- Transition t1 (from State2 to State3)
   +- State1
      +- Region1
         +- State2
         +- State3

Expected result
---------------

The model structure should be (at least in UML-RT)

StateMachine1
+- Region1
   +- State1
      +- Region1
         +- Transition t1 (from State2 to State3)
         +- State2
         +- State3


Testing environment
-------------------

  Papyrus UML	1.1.0.201503251607	org.eclipse.papyrus.sdk.feature.feature.group	Eclipse Modeling Project

on

Eclipse Modeling Tools

Version: Mars Milestone 6 (4.5.0M6)
Build id: 20150326-0744