Uploaded image for project: 'JBRULES'
  1. JBRULES
  2. JBRULES-3083

DecisionTable incorrectly parsed with 5.2.0.CR1

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • 6.0.0.Alpha1
    • 5.2.0.CR1, 5.4.0.Beta2
    • None
    • None

    Description

      5.2.0.CR1 creates incorrect drl from decision table. With 5.1.0.M1 the drl for the same decision table is correct.

      Wrong DRL from 5.2.0.CR1:
      rule "ProcessState"
      salience 65522
      ruleflow-group "CompleteSubOrder"
      activation-group "ProcessState"
      when
      $m:ModifiedMarker(processState==null, state ==null)
      $s:SubOrder
      then
      $m.setIsModified(true);
      $s.setProcessState(ProcessState.CREATED);

      end

      Correct DRL with 5.1.0.M1:
      rule "ProcessState"
      salience 65522
      ruleflow-group "CompleteSubOrder"
      activation-group "ProcessState"
      when
      $m:ModifiedMarker()
      $s:SubOrder(processState==null, state ==null)
      then
      $m.setIsModified(true);
      $s.setProcessState(ProcessState.CREATED);

      end

      The difference is that the constraints are put to $m instead of putting them to $s.
      The attached jpg contains the decision table snippet.

      The behaviour in 5.2.0.CR1 is the same for all decision tables in my project and prevents me from upgrading to newer drools versions.

      Attachments

        Activity

          People

            mproctor@redhat.com Mark Proctor
            kmelba Kara Melba (Inactive)
            Archiver:
            rhn-support-ceverson Clark Everson

            Dates

              Created:
              Updated:
              Archived:

              PagerDuty