<div><br></div><div> The difference in that area from 5.2 to 5.3 is that in 5.3 the interaction between Terminal Nodes and the agenda was refactored into a "listerner pattern" . This is required for future features we are working on. It seems the change introduced the regression. </div>
<div><br></div> This is probably enough info to recreate the problem and I bet the different agenda groups are really important in recreating it.<div><br></div><div> I am working in a couple tasks at the moment, but if you can meanwhile open a JIRA with this info I will fix it for the 5.3 final release. If you can, please try to isolate a test case with this scenario:</div>
<div><br></div><div>"If 021 fires to turn off the lookup AND 042B fires to turn on the lookup, then 022 gets and NPE."</div><div> </div><div> If you are unable to, no problem.</div><div><br></div><div> BTW, I liked Wolfgang's handler as well. If he would like to contribute the code, more than happy to add it to the codebase.</div>
<div><br></div><div> Edson</div><div><br><div class="gmail_quote">2011/10/4 Jamie <span dir="ltr"><<a href="mailto:jshaw@llbean.com">jshaw@llbean.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Thanks for all of the feedback. I haven't tried W's handler, but I'm<br>
planning to. I did take Edson's advice and was able to get some more info.<br>
<br>
It appears to involve the interaction between 3 rules. For background, this<br>
is a fraud detection application. Under certain conditions, we need to look<br>
up additional customer information. Some rules are run to determine whether<br>
the lookup is required and then another rule actually does the lookup. In<br>
this case:<br>
<br>
Rule 021 says if the order is small, set the lookup flag to false<br>
Rule 042B says if the order is from a 'bad' country, set the lookup flag to<br>
true<br>
Rule 022 says if the lookup flag is true, do the lookup<br>
<br>
If rule 021 fires alone, then 022 does not fire and all is well.<br>
If rule 042B fires alone, then 022 fires and all is well.<br>
If 021 fires to turn off the lookup AND 042B fires to turn on the lookup,<br>
then 022 gets and NPE.<br>
<br>
As Edson suspected, the item is null and the 'rule' variable points to rule<br>
021.<br>
<br>
I'm not sure if it matters, but each rules involved is in a different agenda<br>
group.<br>
<br>
As I mentioned, this works in 5.2.0.Final, but breaks in 5.3.0.CR1.<br>
<br>
Hope this helps pinpoint the issue.<br>
<font color="#888888"><br>
<br>
--<br>
View this message in context: <a href="http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flows-tp3390922p3393730.html" target="_blank">http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flows-tp3390922p3393730.html</a><br>
</font><div><div></div><div class="h5">Sent from the Drools: User forum mailing list archive at Nabble.com.<br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br> Edson Tirelli<br> JBoss Drools Core Development<br> JBoss by Red Hat @ <a href="http://www.jboss.com">www.jboss.com</a><br>
</div>