JBoss Community

Yes, this is an issue because the OMG Semantic.xsd defines a specific sequence for the process element

<xsd:complexType name="tProcess">

        <xsd:complexContent>

            <xsd:extension base="tCallableElement">

                <xsd:sequence>

                    <xsd:element ref="auditing" minOccurs="0" maxOccurs="1"/>

                    <xsd:element ref="monitoring" minOccurs="0" maxOccurs="1"/>

                    <xsd:element ref="property" minOccurs="0" maxOccurs="unbounded"/>

                    <xsd:element ref="laneSet" minOccurs="0" maxOccurs="unbounded"/>

                    <xsd:element ref="flowElement" minOccurs="0" maxOccurs="unbounded"/>

                    <xsd:element ref="artifact" minOccurs="0" maxOccurs="unbounded"/>

                    <xsd:element ref="resourceRole" minOccurs="0" maxOccurs="unbounded"/>

                    <xsd:element ref="correlationSubscription" minOccurs="0" maxOccurs="unbounded"/>

                    <xsd:element name="supports" type="xsd:QName" minOccurs="0" maxOccurs="unbounded"/>

                </xsd:sequence>

                <xsd:attribute name="processType" type="tProcessType" default="None"/>

                <xsd:attribute name="isClosed" type="xsd:boolean" default="false"/>

                <xsd:attribute name="isExecutable" type="xsd:boolean"/>

                <xsd:attribute name="definitionalCollaborationRef" type="xsd:QName" use="optional"/>

            </xsd:extension>

        </xsd:complexContent>

eclipse.bpmn2 on the other hand cannot follow this sequence as defined. Bypassing Semantic.xsd fixes the issue :)