Re: [rules-users] evaluating different aspects of the same event

cause if i would know that there hasnt been a change in the count of, for example, A.A, it shouldnt fire, that leads me to the next question: is an accumulate function excuted by more than one thread ? it rises if you think of storing such information in the context of the accumulate function directly. like a semaphore, which signals that this entry has already caused something fired in the example: the rule 1 accumulates over attributes of incoming objects (A.A) and also sets a flag if an entry has been changed (count ++) -- View this message in context: http://drools.46999.n3.nabble.com/evaluating-different-aspects-of-the-sam... Sent from the Drools: User forum mailing list archive at Nabble.com.