Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
substitution group parsing is broken #119
Code generated from BPMN 2.0 xsds does not compile
Using scalaxb via the maven plugin version 0.6.6 and scala 2.9.1 against the BPMN 2.0 xsds (the five listed under normative which I'll attach after this is raised if I can) generates code which does not compile.
The compile errors are here.
A copy of the maven pom used is here - it's structured to generate scala code back into the source tree every time eclipse triggers a build.
On 15 November 2011 12:27, Brian Smith
Not that it solves your problem, but you might be interested in the
Update site: http://martiell.github.com/m2e-scalaxb/update
This means you can leave the outputDirectory set to
I created the reproduction sample is here: https://github.com/eed3si9n/scalaxb-sample/tree/bpmn/bpmn
The error seems to be coming from handling of substitution group:
<xsd:complexType name="tActivity" abstract="true"> <xsd:complexContent> <xsd:extension base="tFlowNode"> <xsd:sequence> <xsd:element ref="ioSpecification" minOccurs="0" maxOccurs="1"/> <xsd:element ref="property" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="dataInputAssociation" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="dataOutputAssociation" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="resourceRole" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="loopCharacteristics" minOccurs="0"/> </xsd:sequence> ... </xsd:extension> </xsd:complexContent> </xsd:complexType>
In the above
There's something buggy about the handling of substitution group.
0.6.7-SNAPSHOT is out with the fix.
The sample I created uses sbt-scalaxb: https://github.com/eed3si9n/scalaxb-sample/tree/bpmn/bpmn