[rules-users] Writing a pattern in which each event constraint depends on the previous event

[Greg Barton]

Yes, the accumulate function itself should maintain the sort internally.
@OlliSee : See the thread titled "How to write a rule that fires when it matches against specific facts in working memory."
--- On Sun, 1/30/11, Wolfgang Laun <wolfgang.laun at gmail.com> wrote:

From: Wolfgang Laun <wolfgang.laun at gmail.com>
Subject: Re: [rules-users] Writing a pattern in which each event constraint depends on the previous event
To: "Rules Users List" <rules-users at lists.jboss.org>
Date: Sunday, January 30, 2011, 10:25 AM



On 30 January 2011 12:55, OlliSee <o.roess at seeburger.de> wrote:



@Wolfgang: I guess you are referring to the list I use. Of course I expect

them to be ordered by timestamp.


You sure do, but the question is whether you get them in this order during processing by accumulate. There is no documentation that accumulate passes through a set of selected facts in the order they were inserted. It could just as well be the (random) order of some hash key, or reverse, or whatever.


-W

 
--

View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Writing-a-pattern-in-which-each-event-constraint-depends-on-the-previous-event-tp2370165p2383235.html


Sent from the Drools - User mailing list archive at Nabble.com.

_______________________________________________

rules-users mailing list

rules-users at lists.jboss.org

https://lists.jboss.org/mailman/listinfo/rules-users




-----Inline Attachment Follows-----

_______________________________________________
rules-users mailing list
rules-users at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20110130/1d010f55/attachment.html