Try some later version. 5.2.0 was the version after a major rework, and your problem might disappear using 5.[345].0 etc.
If this doesn't help, consider posting the rule, after systematically obfuscating app-specific names *without removing anything*. -W On 22/07/2013, Sammi <[email protected]> wrote: > Version is 5.2.0.Final I am using. > > I am not able to reproduce the issue when I wrote a small test to simulate > the problem. But really by changing the line from "eval(...)" to > "Boolean(this == Boolean.TRUE)" then the issue was gone. > > The problematic programs are too complicated to be shown here, and it's not > appropriate as there are business logic in it. > > What might be the issue causing this? if anyone could shed some light It > would be greatly appreciated... > > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Change-Notification-doesn-t-work-with-eval-true-in-one-of-the-rules-tp4025067p4025069.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
