Re: [rules-users] Snapshot of drools engine's state

Thanks for your reply. The way you described this is actually how my proof-of-concept works. However, I implemented it using two timestamps. First I use the @timestamp annotation for the property of the event. This property is set by the event source. Second, I persist a second timestamp that reflects the timestamp of the session's pseudo clock when I inserted the event. From my naive feeling I need both for a reproducible replay starting with the last snapshot of the session. Thanks for the hint concerning the sliding window. This is the drawback of the approach of externally controlling the clock - it limits the time granularity of these not-event-B-after-A rules. But in my case I can live with this restriction that the rule might fire some seconds later. I wished there would exist a possibility to register for a kind of callback when to externally trigger the event engine again - however, I haven't found anything related to that. Thanks & best regards, Ingo -- View this message in context: http://drools.46999.n3.nabble.com/Snapshot-of-drools-engine-s-state-tp402... Sent from the Drools: User forum mailing list archive at Nabble.com.