Thanks Edison,
Looking forward to the update in Mvel.
Unfortunately, I tried the binding but still get an error where the bound
variable cannot be recognized. I should also mention that the Profile fact
is declared and not a pre generated POJO.
So here is the updated rule:
package com.uday.tar
Hi Uday,
Thanks for the report bellow. I was able to isolate this to an MVEL
regression that I submitted to Mike to fix:
http://github.com/etirelli/mvel/commit/55347b578f23184935c6d224323ff031805f1afe
This will be in MVEL 2.0.19, so as soon as Mike releases it you can
update your mvel j
Hi Edison,
Thanks for the tip, I realize how I can use Integer type now.
The following should hopefully be sufficient to reproduce the error that I
am experiencing. Please me know if you need further clarity. I'm continuing
to search through posts to and debug. I'll post back if I find the solut
Uday,
You don't need a new type:
Number( this daycompare[gt] 1 ) from profile.pageFreq["internet"]
I used the Number interface above, but you can use the Integer
class directly if you want. Also, you can use the field names like
"intValue" instead of using "this" if you want.
Now, I
Edison,
Thanks for your prompt reply!
I'm trying to incorporate the workaround that you've suggested but I keep
getting an error with the use of the from clause. I based this off of the
documentation provided on drools.org for drools expert on how to use the
from clause.
So I declared a cust
Uday,
The short answer is: Drools supports pluggable evaluators only for
direct fact attributes, with direct values as a second parameter. It
is not possible to use nested access or map access when using
pluggable operators. The workaround for now is to extract the value
from the map before
Hello,
I'm not sure if this is a bug, but I'd like to check with the Drools experts
to see if it is.
I noticed this when creating my custom operator, which doesn't appear to
recognize values from Maps, but works fine with non Map based values.
I have created a custom comparison operator which
