Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-3976

Default sequenceFlow elements for Exclusive Gateway elements are (incorrectly) required to have a condition expression

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Critical Critical
    • jBPM 6.0.0.Beta5
    • jBPM 5.2, jBPM 6.0.0.Beta5
    • Runtime Engine
    • None
    • Medium

      The specification is fairly clear on this:

      p. 282, table 10.123: ExclusiveGateway Attributes & Model Associations

      Attribute Name Description/Usage
      default: SequenceFlow [0..] The Sequence Flow that will receive a token when none of the conditionExpressions on other outgoing Sequence Flows evaluate to true. The default Sequence Flow should not have a conditionExpression. Any such Expression SHALL be ignored.

      Currently, the attached bpmn2 file fails for both 5.2.x and 6.x.

      The test can be run easily by adding the following code to the StandaloneBPMNProcessTest in 6.x or the SimpleBPMNProcessTest in 5.2.x

          @Test
          public void testExclusiveSplitDefaultNoCondition() throws Exception {
              KieBase kbase = createKnowledgeBase("BPMN2-ExclusiveSplitDefaultNoCondition.bpmn2");
              KieSession ksession = createKnowledgeSession(kbase);
              ProcessInstance processInstance = ksession.startProcess(
                      "com.sample.test");
              assertTrue(processInstance.getState() == ProcessInstance.STATE_COMPLETED);
          }
      

              swiderski.maciej Maciej Swiderski (Inactive)
              marco.rietveld Marco Rietveld (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: