Hi all,<div>I'm dealing with a set of rules having the lock-on-active attribute and I'm not getting the (at least what I understand as) expected results.</div><div><br></div><div>I've created an isolated JUnit test. I'm attaching it to this email.</div>
<div><br></div><div>Basically, I have 2 rules:</div><div><br></div><div><br></div><div><div>rule "init"</div><div>lock-on-active true</div><div>when</div><div> $d: DataSample()</div><div>then</div><div> System.out.println("Setting predefined value");</div>
<div> modify($d){</div><div> addValue(Parameter.PARAM_A, 10.0)</div><div> }</div><div>end</div><div><br></div><div>rule "Rule 1"</div><div>lock-on-active true</div><div>when</div><div> DataSample($v: values[Parameter.PARAM_A] < 20)</div>
<div>then</div><div> System.out.println("Rule 1: "+$v);</div><div>end</div></div><div><br></div><div><br></div><div>DataSample is a Java class containing a Map<Parameter, Double> where Parameter is an enum.</div>
<div>In the test I'm creating a ksession and inserting an empty DataSample object. </div><div>I understand that as soon as the object is inserted, both rules are evaluated and the result is going to be an activation of rule "init"; and this is what is actually happening. So far so good.</div>
<div>Now, after I call fireAllRules() I expect that 'Rule 1' becomes active because of the modification of the fact in "init". Well, this is not the case. I don't see any activation for "Rule 1".</div>
<div>My understanding about lock-on-active is that a rule that WAS ACTIVATED is not going to be re-activated until the current agenda group is switched. The odd thing here is that I never had an activation for "Rule 1" so I don't see why it activation after "init" is executed should be prevented.</div>
<div>So my question is: Is my understanding wrong? What is the expected behavior of lock-on-active in this situation? I read the documentation but I couldn't get any hint:</div><div><br></div><div>"<a id="d0e5148" style="color:rgb(51,51,51);font-family:'Lucida Grande',Geneva,Verdana,Arial,sans-serif;font-size:12px;line-height:18px;text-align:justify"><dd style="margin:0em 0em 0em 2em;padding-top:0em;display:inline!important">
<p style="display:inline!important">Whenever a ruleflow-group becomes active or an agenda-group receives the focus, any rule within that group that has lock-on-active set to true<b> will not be activated any more</b>; irrespective of the origin of the update, the activation of a matching rule is discarded. This is a stronger version of no-loop, because the change could now be caused not only by the rule itself. It's ideal for calculation rules where you have a number of rules that modify a fact and you don't want any rule re-matching and firing again. Only when the ruleflow-group is no longer active or the agenda-group loses the focus those rules with lock-on-active set to true become eligible again for their activations to be placed onto the agenda."</p>
</dd></a></div><div><br></div><div>Best Regards,</div><div> </div><div><br>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br><br>Esteban Aliverti<br>- Blog @ <a href="http://ilesteban.wordpress.com" target="_blank">http://ilesteban.wordpress.com</a><br>
</div>