Thank-you
09-08-2011 13:23 użytkownik Wolfgang Laun-2 [via Drools]
ml-node+3238607-487429483-420...@n3.nabble.com napisał:
Modules (=agenda-group and ruleflow-group) are fine for large-scale
rule flow control. First choice for fine-grained rule execution
control is - Logic.
Write your
Whenever a ruleflow-group becomes active [...], any rule within that group
that has lock-on-active set to true *will not be activated any more*.
(Emphasis added by me.)
Do you activate the ruleflow-group before you insert the Car fact?
-W
On 9 August 2011 11:05, bitter rgorz...@gmail.com
Do you activate the ruleflow-group before you insert the Car fact?
No, I don't think so.
This is body of my test class:
public class CarKnowledgeBaseTest {
@Test
public void shouldObtainPriceWhereSalienceIsBigger() throws Exception {
//given
KnowledgeBase kbase =
But when I use activation-group only one fact has price. I would like to
insert two facts (or more) and only one rule invoke per fact.Like in my test
class.
Could you look at use case that I attached in my first post? Thanks.
Wolfgang Laun-2 wrote:
You should use activation-group price or
Modules (=agenda-group and ruleflow-group) are fine for large-scale
rule flow control. First choice for fine-grained rule execution
control is - Logic.
Write your constraints so that only one rule fires, e.g., by testing
price == null.
Ideally, you should also avoid salience by fully describing
I have three rules:
rule First rule
salience 20
ruleflow-group rfs_1
lock-on-active true
when
$c: Car(color == red)
then
$c.setPrice(1);
update($c);
end
rule Second rule
salience 25
