Activating and deactivating rules in batches (i.e., groups of one sort
or other) cannot be imitated by salience.
If you leave a group, no rule from that group stands a chance to
become active again. But a high-salience rule that isn't activated
before 0:12:34.567 may (after some firings of low-salience rules)
become activated at 0:12:34.567, after its LHS has finally made the
match point.
I have used agenda groups to achieve a flow of rule batches --- no
problem in 5.1.
-W
On 23 February 2011 17:34, elitwin <eric.litwin(a)pnmac.com> wrote:
elitwin wrote:
>
> There are two issues posted in Jira about this.
>
>
https://issues.jboss.org/browse/JBRULES-2718
>
https://issues.jboss.org/browse/JBRULES-2728 (duplicate of 2718)
>
> I am not sure if/when there is any plan to fix this in 5.1.x.
>
> I may have to revert back to 5.0.1.
> I was also going to try 5.2.0.M1 to see if it works, but a 5.2 FINAL
> release is probably pretty far off, so I don't think that is a realistic
> alternative.
>
>
I decided to try using salience instead of RuleFlow to try to control the
order in which the rules fire. It is not ideal, but I thought I could get it
to work. However, I am seeing rules with higher salience firing after rules
with much lower salience. It doesn't consistently happen, but it seems that
salience is not very reliable across a large number of rules.
Still curious to know if there are plans to address the above issues (2718)
in 5.1.1. It seems like this is fairly important functionality.
Eric
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/RuleFlow-only-calling...
Sent from the Drools - User mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users