It's indeed a bug - a regression from 5.1.1.

Depending on the fact classes coming from Java or their being declared in DRL, different error scenarios can be reproduced - see JBRULES-3129 and JBRULES-3130, the latter being the issue reported by pamerida.

@pamerida: With 5.2.0, the only workaround that appears to cover all contigencies is to give the mvel-ish expression a wide berth and use

    eval( ((Three)list.get(0)).getA() == null )


On 12 July 2011 01:37, pamerida <elpamm@hotmail.com> wrote:
Hi.. sorry I didnt include all the information...
heres the class Im using

http://drools.46999.n3.nabble.com/file/n3160827/ruleInvoker.java
ruleInvoker.java

I use the method "invocarReglas"...

I dont modify any fact, the values I show there are set before I insert the
fact into the session...

Im using drools 5.2....

thanks for your help



--
View this message in context: http://drools.46999.n3.nabble.com/Drools-firing-wrong-rules-tp3160376p3160827.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users