[
https://issues.jboss.org/browse/DROOLS-159?page=com.atlassian.jira.plugin...
]
Andreas Volz edited comment on DROOLS-159 at 6/4/13 9:16 AM:
-------------------------------------------------------------
The attachment contains an eclipse project with a JUnit test case for reproducing the
bug.
was (Author: avo):
Contains eclipse project with JUnit test case to reproduce the bug.
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