That would be a good compromise for DROOLS, use at your own risk, but not out
of box. How do I turn it on?
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-mvel-consequence-if-logEnabled-discussion-disabled-if-statement-tp2816469p2820041.html
Sent from the Drools: User
I know I've seen other posts saying that if statement in consequence has been
disabled due to it being poor practice, but I see the use in logging.
Lets say in consequence I have a complicated rule with 5 conditions and an
action:
modify($score) {
value = $score.value + 1;
}
if
Oh I should've mentioned, this was in the top of drl file:
dialect mvel
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/Map-Accessor-not-allowing-using-a-parameter-gets-field-extractor-error-tp2776894p2779707.html
Sent from the Drools - User mailing list
Using Drools 5.1.1
Is there anything I can do except to make a method/property in my original
class to do the .get into map for me? According to drools specs this should
work.
This gets the error:
rule Find Lowest Score
salience 100
when
$aobject : DataObject($index:
As an additional note, I've also tried adjusting the events expiration time
and no change:
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
@expires(100s)
end
--
View this message in context:
I appreciate the responses. As you said, it does really limit the capability
of sliding windows lengths.
I have created a JIRA, hopefully it's good enough for your purposes:
https://jira.jboss.org/browse/JBRULES-2823
Thanks for the workaround also! Looking forward to it being updated
