Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-159

Wrong execution order when explicitly setting SalienceConflictResolver

XMLWordPrintable

    • Hide

      Import the attached eclipse project into your workspace. The project contains a JUnit test case that reproduces the bug.

      Show
      Import the attached eclipse project into your workspace. The project contains a JUnit test case that reproduces the bug.

      When setting the conflict resolution strategy to Salience the execution order of the rules is incorrect: the rule with the lowest salience value is fired first.
      The Salience conflict resolution strategy is set by defining it in the RuleBaseConfiguration:

      RuleBaseConfiguration rbc = new RuleBaseConfiguration();
      rbc.setConflictResolver(SalienceConflictResolver.getInstance());
      RuleBaseFactory.newRuleBase(rbc);

      When the rule base is created without setting the conflict resolution strategy to Salience the execution order of the rules is correct.

              mfusco@redhat.com Mario Fusco
              avo_jira Andreas Volz (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: