when I was testing the sliding windows, I was blocked becouse this concept
doesn't work for me, It's becouse of my misunderstanding of the concept, I
looking for the error which I do:
for exemple:
== the rule:
*/
rule sliding windows
when
$a : Event1() over
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:
Constraints restrict what you see through a window; they do not modify or
qualify the window. Thus, basically you see the last three CPUReportEvents,
and new activations are possible for each new event of this type. Other
patterns (such as ComEntity) create (in your case: two) alpha network nodes,
This is an interesting side effect. Sliding windows are applied to
the source pattern in Drools, meaning CPUReportEvent in your example.
So alpha constraints are applied before the sliding window, while beta
constraints are applied after. Now, for time-based windows, there is
no difference
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
Thanks.
2010/12/8 AberAber maryellenbe...@hotmail.com:
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
