Replacing eval( true) with Boolean( this == Boolean.TRUE ) results in a
different network configuration:
the former requires an EvalNode, the latter a JoinNode.
A few issues with EvalNode dynamic additions/removals have been found
and fixed over time,
including one that was found last week. Please do check with later versions.
p.s. there may be more robust ways to control which rules are enabled or
not at a given moment.
On 07/22/2013 11:37 AM, Wolfgang Laun wrote:
Try some later version. 5.2.0 was the version after a major rework,
and your problem might disappear using 5..0 etc.
If this doesn't help, consider posting the rule, after systematically
obfuscating app-specific names *without removing anything*.
On 22/07/2013, Sammi <sammi_ting(a)yahoo.com.hk> 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:
> Sent from the Drools: User forum mailing list archive at Nabble.com
> rules-users mailing list
rules-users mailing list