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:
Sent from the Drools: User forum mailing list archive at Nabble.com