0

规则：

rule "Accounting_11" dialect "mvel" 
//For any value of l except given in Accounting_12
salience 1 
activation-group "Group l"  
auto-focus true
lock-on-active
no-loop true 
when $iv:Invoice(x in ("D20","D21","D22", "D23", "D24","D25"),y =="E20",z =="F20",a =="G20") 
then modify($iv) { sg.setA("ALL l"), sg.setB("C20")} 
end

rule "Accounting_12"  dialect "mvel" 
//Exceptions of l
salience 2  
activation-group "Group l" 
auto-focus true
lock-on-active
no-loop true 
//Pattern is similar to Accounting_11 with additional constraint "l in (....)"
when $iv:Invoice(l in ("C20","C21","C22", "C23", "C24","C25") , x in ("D20","D21","D22", "D23", "D24","D25"),y =="E20",z =="F20",a =="G20") 
then modify($iv) { sg.setA("Sepcific l"), sg.setB("C20")} 
end

在循环中在工作记忆中插入 2 个事实。

  • 发票(l="C20", x="D20", y= "E20", z="F20",", a="G20")
  • 发票(x="D20", y= "E20", z="F20", a="G20")

调用 fireAllRules().3 激活按预期创建。

==>[ActivationCreatedEvent: getActivation()=[[ Accounting_11 active=false ] [ [fact 0:2:4445234:4445234:2:DEFAULT:NON_TRAIT:org.cpg.poc.drools.keloy.domain.Invoice@43d432] ] ], getKnowledgeRuntime()=org.drools.core.impl.StatefulKnowledgeSessionImpl@1743ccd]
    ==>[ActivationCreatedEvent: getActivation()=[[ Accounting_11 active=false ] [ [fact 0:1:2489285:2489285:1:DEFAULT:NON_TRAIT:org.cpg.poc.drools.keloy.domain.Invoice@25fbc5] ] ], getKnowledgeRuntime()=org.drools.core.impl.StatefulKnowledgeSessionImpl@1743ccd]
    ==>[ActivationCreatedEvent: getActivation()=[[ Accounting_12 active=false ] [ [fact 0:2:4445234:4445234:2:DEFAULT:NON_TRAIT:org.cpg.poc.drools.keloy.domain.Invoice@43d432] ] ], getKnowledgeRuntime()=org.drools.core.impl.StatefulKnowledgeSessionImpl@1743ccd]

预期的激活之一被触发

==>[BeforeActivationFiredEvent:  getActivation()=[[ Accounting_12 active=false ] [ [fact 0:2:4445234:4445234:2:DEFAULT:NON_TRAIT:org.cpg.poc.drools.keloy.domain.Invoice@43d432] ] ], getKnowledgeRuntime()=org.drools.core.impl.StatefulKnowledgeSessionImpl@1743ccd]

但它取消了所有其他激活。

==>[ActivationCancelledEvent: getCause()=CLEAR, getActivation()=[[ Accounting_11 active=false ] [ [fact 0:2:4445234:4445234:2:DEFAULT:NON_TRAIT:org.cpg.poc.drools.keloy.domain.Invoice@43d432] ] ], getKnowledgeRuntime()=org.drools.core.impl.StatefulKnowledgeSessionImpl@1743ccd]
==>[ActivationCancelledEvent: getCause()=CLEAR, getActivation()=[[ Accounting_11 active=false ] [ [fact 0:1:2489285:2489285:1:DEFAULT:NON_TRAIT:org.cpg.poc.drools.keloy.domain.Invoice@25fbc5] ] ], getKnowledgeRuntime()=org.drools.core.impl.StatefulKnowledgeSessionImpl@1743ccd]

它不应该只取消为相同的事实句柄 (Invoice@43d432) 创建的激活，即 l=C20 的激活吗？

为什么它取消了为Invoice@25fbc5创建的激活，第二个“l”值为空？

注意：当我在每次插入事实后触发规则时，我会得到预期的结果。

4

1 回答 1

0

使用规则属性 no-loop 和 lock-on-active 被宣传为简化规则创作，这在一定比例的用例中是正确的。然而，它始终是避免严格应用逻辑（规则条件的基础）的一种方式。尽管向规则条件添加完整的逻辑可能需要更多的工作，但它肯定会创建一个健壮的逻辑，从而产生您真正想要的规则执行。

也就是说，由于插入的规则，我看不出会发生什么。显然，Accounting_11 和 Accounting_12 的约束是重叠的，Accounting_12 的限制更大。这总是一个可疑的情况：您希望两种后果都发生还是只发生一种？Accounting_12 具有更高的异化性，因此将是首选（与 field 的值无关l）。如果没有规则属性，我希望其他激活保持活动状态，但是使用lock-on-active, 激活会被取消。

正如我所说：在基本约束中描述所需的逻辑是可取的。

例如，如果不应该为l集合定义的范围内的值激活规则 `("C20", "C21", "C22", "C23", "C24", "C25")，请添加此约束：

$iv:Invoice(l not in ("C20", "C21", "C22", "C23", "C24", "C25"),...)
于 2015-06-03T13:14:40.750 回答