This rule fires once for every RequestCtx in WM. Therefore, should it fire at all, it will fire (at least) twice for every ID duplication; thrice for every triplication, and so on.
I'm inclined to think that this sort of problem is best solved with an accumulate CE over all you have in the window. This accumulat should count every RequestCtx according to its ID; then more CEs can analyze the result. -W On 7 July 2011 14:59, Andre <morpheusan...@web.de> wrote: > here im again , cause im not really sure i matched the goal i wanted with > this combination: > does it really checks, whether in time window 1m are the same 2 events with > the same name ? > when > $actual: RequestCtx() > > ArrayList( size >= 2 ) > from collect( $expected : RequestCtx( > DroolsUtils.requestsMatchesforSubjectID($expected,$actual, > "urn:oasis:names:tc:xacml:1.0:subject:subject-id") ) over window:time(1m) > my tests results are looking strange und im would say that theres something > missing , which connects the the LHS parts, to ensure that not the same > event instance will also trigger the second part > > -- > View this message in context: > http://drools.46999.n3.nabble.com/sliding-window-combination-tp3132340p3148104.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > rules-users@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users >
_______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
