Ah right, that's good to know.
--
View this message in context:
http://drools.46999.n3.nabble.com/Can-get-not-equal-to-work-but-not-equal-in-LHS-tp4022074p4022087.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
___
rules-use
Are you setting the focus on the agenda group appropriately?
Remember that, with lock-on-active, you'll also have to TOGGLE the focus
I tested the rules on 5.5.1-snapshot and everything seems to work,
which version are you using?
Davide
On 02/05/2013 09:50 AM, BenjaminWolfe wrote:
> Backgroun
Okay … well, without seeing what's been inserted as an Autopolicy in the first
place, I reckon the best plan is to debug it. It's probably worth changing to
something like this:
when
$autoPolicy : Autopolicy($ruleFlowId: ruleFlowId)
then
logger.de
Going by the example provided, the code is a constraint on the left hand side …
so it's valid to use == or !=. It's not Java code, it's MVEL and is
automatically converted to use the appropriate .equals("") method on the Java
objects.
You would only need to use .equals("") inside an eval or in
It may be because in Java you have to compare strings using .equals("");
So in your case it would be:
ruleFlowId.equals("test") == true
It's because Strings are objects, and == tests to see if the String is
literally the same object as the other String, not just a String with the
same value. !
