[jboss-jira] [JBoss JIRA] (DROOLS-159) Wrong execution order when explicitly setting SalienceConflictResolver
[
https://issues.jboss.org/browse/DROOLS-159?page=com.atlassian.jira.plugin...
]
Davide Sottara commented on DROOLS-159:
---------------------------------------
Confirmed (and easily fixed), but you are still using Drools-4 and earlier methods and
classes.
The SalienceConflictResolver can be omitted since the engine manages salience natively.
They may be removed/refactored in 6+, so I would recommend to upgrade to the Drools 6
public APIs.
Thanks,
Davide
Wrong execution order when explicitly setting
SalienceConflictResolver
----------------------------------------------------------------------
Key: DROOLS-159
URL: https://issues.jboss.org/browse/DROOLS-159
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.5.0.Final, 6.0.0.Beta2
Environment: Windows 7, JDK 1.6.26
Reporter: Andreas Volz
Assignee: Mark Proctor
Labels: conflictResolver, salience
Attachments: wrong-firing-order.zip
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:
{code}RuleBaseConfiguration rbc = new RuleBaseConfiguration();
rbc.setConflictResolver(SalienceConflictResolver.getInstance());
RuleBaseFactory.newRuleBase(rbc);{code}
When the rule base is created without setting the conflict resolution strategy to
Salience the execution order of the rules is correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira