Bug 541405 - Bpmn files not valid against OMG schema
Summary: Bpmn files not valid against OMG schema
Status: UNCONFIRMED
Alias: None
Product: MDT.BPMN2
Classification: Modeling
Component: Core (show other bugs)
Version: 1.3.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-21 09:55 EST by Grzegorz Abramczyk CLA
Modified: 2018-11-21 09:55 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Grzegorz Abramczyk CLA 2018-11-21 09:55:23 EST
OMG Schema (https://www.omg.org/spec/BPMN/20100501/Semantic.xsd) defines specific order of elements, for example for process

<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>

But the files generated by BPMN2-Modeler are not following the order - for example generating 'property' elements after 'flowElement' elements.

I'm trying to use bpmn files in a tool (Activiti) that apparently uses xsd based parser and I'm forced to manually fix process definitions to get them understood - and the order is broken after each save.

To verify add xsi:schemaLocation="http://www.omg.org/spec/BPMN/20100524/MODEL https://www.omg.org/spec/BPMN/20100501/BPMN20.xsd" to the process definition and validate it as xml in eclipse.