I think Prof. Michael Stiber wrote: > > > > Synchronize on the activation lock (retrieved from > > Rete.getActivationLock()) to prevent rules from firing during a block > > of code. > > > > Just to make sure I understand, this won't fix the incremental shadow > fact slot update, right? It will prevent rules from firing in between > the firePropertyChange() calls, but there will still be multiple > modifications of the shadow fact seen in Jess.
Yes. > Will rules fire in between processing of these "accumulated" changes > (after the lock as been release, that is)? No. The final list of activations for a given set of facts is "path invariant" -- those "in-between" activations will be gone by the time you release the lock, never having had the chance to fire. > Anyway, I guess this is still messier than coalescing the events > (which I probably subconsciously remembered from X programming I did > years ago). --------------------------------------------------------- Ernest Friedman-Hill Science and Engineering PSEs Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 PO Box 969, MS 9012 [EMAIL PROTECTED] Livermore, CA 94550 http://herzberg.ca.sandia.gov -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
