Re: [rules-users] Error in MVEL execution (optimization?)

This is even more interesting. MVEL allows straight Java syntax (e.g. getField() rather than just field). I can leave the dialect defaulting to MVEL, and as long as I use the Java syntax in the rule it still works right (all three rules - no double call to the utilityMethod). It is only with MVEL syntactic sugar that there is a problem. -- View this message in context: http://drools.46999.n3.nabble.com/Error-in-MVEL-execution-optimization-tp... Sent from the Drools: User forum mailing list archive at Nabble.com.