Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-5102

[GSS] (6.4.z) "Invalid content was found starting with element" caused by textAnnotation ordering

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 6.4.7
    • jBPM Designer
    • Hide

      1. Create a process in business-central
      2. Create a TextAnnotation associating to StartEvent
      3. Create a ScriptNode and EndEvent
      4. Save
      5. Build&Deploy
      See server.log

      Show
      1. Create a process in business-central 2. Create a TextAnnotation associating to StartEvent 3. Create a ScriptNode and EndEvent 4. Save 5. Build&Deploy See server.log

    Description

      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.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-376 "Invalid content was found starting with element" caused by textAnnotation ordering

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: