All,
I isolated the problem and submitted a bug for the macro processing
engine. We shall have a fix soon.
Thanks for reporting.
Edson
2009/3/24 Edson Tirelli
>
>Wolfgang,
>
>Yes, Drools rewrites insert() to drools.insert() before compiling. It
> seems we have a problem in
Wolfgang,
Yes, Drools rewrites insert() to drools.insert() before compiling. It
seems we have a problem in the function that does the rewrite.
[]s
Edson
2009/3/24 Wolfgang Laun
> The RHS of a rule X winds up in some class Rule_X_0. Calls like insert(),
> retract(), etc. are, by def
The RHS of a rule X winds up in some class Rule_X_0. Calls like insert(),
retract(), etc. are, by definition, method calls of WorlingMemoryEntryPoint,
and the compiler ought to prefix them with the global reference to that
object, i.e., "drools". This fails within if statements, both branches.
If
This is odd, since this part of the code didn't changed much from drools
4 to 5 (assuming you are using java dialect for your consequence). Can you
open a JIRA with your test case plz?
[]s
Edson
2009/3/23 Jared Davis
> Hi,
>
> This rule (not the best style) compiles fine in 4.07. It gi
Hi,
This rule (not the best style) compiles fine in 4.07. It gives this error
message using 5.0 Snapshot. I changed some of the text to be generic so I could
post the code.
Rule Compilation error : [Rule name='A.B.inlet.mxb.first.link.20090216.01']
com/zz/yyy/awl/Rule_A_B_inlet_mxb_fi
