State machines still a mess in XMI 2.1

[Frank Horn]

XMI 2.1 output for state machines ist still inconsistent.

1. Add a state machine diagram to a package, then a state machine, define two regions (menu "Advanced - Define Concurrent Substates"), and drag a new state to each region.

XMI 2.1 will contain a packagedElement node with attribute xmi:type="uml:StateMachine" and a pseudo-region "EA_Region1" containing both states. The regions defined via the menu will only appear in the extensions section of the xmi document.

2. Add a state machine to a class.

In XMI 2.1 the class node will have an ownedBehavior subnode with  attribute xmi:type="uml:StateMachine" and nothing more. The state machine itself will only appear in the extensions section, not as a packagedElement node at all. Regions will not be respected either.

In both cases, I can find no way of extracting from XMI 2.1 which state belongs to which region.

I sent a bug report about this about a year ago (mentioning that Visual Paradigm actually shows state regions as elements in the project browser, as it should), but never got an answer.

EA 7.5 hasn't changed anything in this respect.