For the record: It was established in brief off-list exchange that 5.1.1 was
in use. The stated problem appears to be fixed in 5.2.0.
-W
2011/6/13 Nicolás Sanchez
> I have just tried it, but it doesn't fire. What is odd is that I have other
> rules, in the same drl, with time operators such as a
I have just tried it, but it doesn't fire. What is odd is that I have other
rules, in the same drl, with time operators such as after[] and they work
perfectly ok when using the @timestamp(callDateTime.getTime()) or
@timestamp(callDateTime).
Nicolas
--
View this message in context:
http://drool
The value of @timestamp is not just a field name but a method call on that
field.
Have you tried
@timestamp(callDateTime)
yet?
-W
2011/6/13 Nicolás Sanchez
> About the questions you asked, here are the answers:
>
> - Is Event declared properly in the DRL?
> Yes, it's been declared properly
>
About the questions you asked, here are the answers:
- Is Event declared properly in the DRL?
Yes, it's been declared properly
- Is the session run properly?
Yes
- Is the insert call correct?
Yes
What I forgot to mention, and excuse me for that omission, is that this
Event is declared inside th
What is the problem - I assume the rule is not firing?
Many things can go wrong here:
- Is Event declared properly in the DRL?
- Is the session run properly?
- Is the insert call correct?
In short, a full working example would be required, and the Drools version
you are using.
-W
2011
Hi,
I have written the next rule :
rule "Too many events in a short period of time"
dialect "mvel"
when
$user : User()
Number(intValue > 3) from accumulate($event : Event(userId == $user.id)
over window:time(1m) from entry-point Event , count($event))
then
//Java code...
end
And the
