-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
6.x.x
textAnnotation (= extends artifact) has to be located after flowElement nodes.
https://github.com/kiegroup/jbpm/blob/6.5.x/jbpm-bpmn2/src/main/xsd/Semantic.xsd#L1190-L1191
But in Process Designer may place a flowElement Node after textAnnotation. For example, with the steps:
1. Create a TextAnnotation
2. Then, create a ScriptTask
See attached org.jbpm.textAnnotationProcess.v1.0.bpmn2
It results in the following error.
16:42:38,209 ERROR [org.drools.core.xml.ExtensibleXmlParser] (EJB default - 5) Process Info: id:project2.textAnnotationProcess, pkg:org.jbpm, name:textAnnotationProcess, version:1.0 Node Info: id:_FD0C3245-20E4-4F02-B17A-0CAE813B38B6 name:S1 Parser message: (null: 20, 225): cvc-complex-type.2.4.a: Invalid content was found starting with element 'bpmn2:scriptTask'. One of '{"http://www.omg.org/spec/BPMN/20100524/MODEL":artifact, "http://www.omg.org/spec/BPMN/20100524/MODEL":resourceRole, "http://www.omg.org/spec/BPMN/20100524/MODEL":correlationSubscription, "http://www.omg.org/spec/BPMN/20100524/MODEL":supports}' is expected.
- is cloned by
-
RHBPMS-5102 [GSS] (6.4.z) "Invalid content was found starting with element" caused by textAnnotation ordering
- Closed
- relates to
-
JBPM-5344 Missing error-reports in case of failed XML validation
- Open