Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-387

"Invalid content was found starting with element" caused by 'documentation' ordering

    XMLWordPrintable

Details

    • DR4
    • Hide

      1. Create a process in business-central
      2. Set some value to "documentation" property of StartEvent
      3. Create a ScriptNode and EndEvent
      4. Set some value to "name" and "script" property of ScriptNode
      5. Set some value to "documentation" property of ScriptNode
      6. Set some value to "name" property of SequenceFlow which is connected to EndEvent
      7. Set some value to "documentation" property of SequenceFlow
      8. Save
      9. Build&Deploy
      See server.log
      Step 4-7 are optional but explain it's reproducible with other elements.

      Show
      1. Create a process in business-central 2. Set some value to "documentation" property of StartEvent 3. Create a ScriptNode and EndEvent 4. Set some value to "name" and "script" property of ScriptNode 5. Set some value to "documentation" property of ScriptNode 6. Set some value to "name" property of SequenceFlow which is connected to EndEvent 7. Set some value to "documentation" property of SequenceFlow 8. Save 9. Build&Deploy See server.log Step 4-7 are optional but explain it's reproducible with other elements.
    • 2018 Week 07-08

    Description

      'documentation' has to be located before other elements.

      https://github.com/kiegroup/jbpm/blob/6.5.x/jbpm-bpmn2/src/main/xsd/Semantic.xsd#L93-L100

      But Process Designer may place a 'documentation' after other elements. For example, with the steps:

      1. Create a StartEvent
      2. Set some text in "documentation" property

      or

      1. Create a ScriptTask
      2. Set some text in "name" and "script" property
      3. Set some text in "documentation" property

      or

      1. Create a sequenceFlow
      2. Set some text in "name" property
      3. And then Set some text in "documentation" property

      See attached org.jbpm.documentationTest.v1.0.bpmn2

      It results in the following error.

      13:48:03,483 ERROR [org.drools.core.xml.ExtensibleXmlParser] (default task-19) (null: 10, 57): cvc-complex-type.2.4.a: Invalid content was found starting with element 'bpmn2:documentation'. One of '{"http://www.omg.org/spec/BPMN/20100524/MODEL":auditing, "http://www.omg.org/spec/BPMN/20100524/MODEL":monitoring, "http://www.omg.org/spec/BPMN/20100524/MODEL":categoryValueRef, "http://www.omg.org/spec/BPMN/20100524/MODEL":incoming, "http://www.omg.org/spec/BPMN/20100524/MODEL":outgoing, "http://www.omg.org/spec/BPMN/20100524/MODEL":property, "http://www.omg.org/spec/BPMN/20100524/MODEL":dataOutput, "http://www.omg.org/spec/BPMN/20100524/MODEL":dataOutputAssociation, "http://www.omg.org/spec/BPMN/20100524/MODEL":outputSet, "http://www.omg.org/spec/BPMN/20100524/MODEL":eventDefinition, "http://www.omg.org/spec/BPMN/20100524/MODEL":eventDefinitionRef}' is expected.
13:48:03,484 ERROR [org.drools.core.xml.ExtensibleXmlParser] (default task-19) (null: 19, 57): cvc-complex-type.2.4.a: Invalid content was found starting with element 'bpmn2:documentation'. One of '{"http://www.omg.org/spec/BPMN/20100524/MODEL":auditing, "http://www.omg.org/spec/BPMN/20100524/MODEL":monitoring, "http://www.omg.org/spec/BPMN/20100524/MODEL":categoryValueRef, "http://www.omg.org/spec/BPMN/20100524/MODEL":incoming, "http://www.omg.org/spec/BPMN/20100524/MODEL":outgoing, "http://www.omg.org/spec/BPMN/20100524/MODEL":ioSpecification, "http://www.omg.org/spec/BPMN/20100524/MODEL":property, "http://www.omg.org/spec/BPMN/20100524/MODEL":dataInputAssociation, "http://www.omg.org/spec/BPMN/20100524/MODEL":dataOutputAssociation, "http://www.omg.org/spec/BPMN/20100524/MODEL":resourceRole, "http://www.omg.org/spec/BPMN/20100524/MODEL":loopCharacteristics, "http://www.omg.org/spec/BPMN/20100524/MODEL":script}' is expected.
13:48:03,488 ERROR [org.drools.core.xml.ExtensibleXmlParser] (default task-19) (null: 39, 57): cvc-complex-type.2.4.a: Invalid content was found starting with element 'bpmn2:documentation'. One of '{"http://www.omg.org/spec/BPMN/20100524/MODEL":auditing, "http://www.omg.org/spec/BPMN/20100524/MODEL":monitoring, "http://www.omg.org/spec/BPMN/20100524/MODEL":categoryValueRef, "http://www.omg.org/spec/BPMN/20100524/MODEL":conditionExpression}' is expected.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBPM-6794 Invalid content was found starting with element caused by 'documentation' ordering

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. RHBPMS-5110 [GSS] (6.4.z) "Invalid content was found starting with element" caused by 'documentation' ordering

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              rhn-support-tsurdilo Tihomir Surdilovic (Inactive)
              rhn-support-tkobayas Toshiya Kobayashi
              Lubomir Terifaj Lubomir Terifaj
              Lubomir Terifaj Lubomir Terifaj
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: