I think Prof. Michael Stiber wrote:
What I tried was to put the firePropertyChange() calls into a synchronized method in my bean, and make all of the property accessors synchronized, too. This didn't work; I assume this just blocked the action of Jess until all the changes were fired, but the shadow fact's slots still updated "one at a time". Is there any way to block Jess during a sequence of firePropertyChange() calls, and then have it update slots en masse?
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. Will rules fire in between processing of these "accumulated" changes (after the lock as been release, that is)? Anyway, I guess this is still messier than coalescing the events (which I probably subconsciously remembered from X programming I did years ago).
-- Prof. Michael Stiber [EMAIL PROTECTED] Computing and Software Systems http://faculty.washington.edu/stiber University of Washington, Bothell tel: +1-425-352-5280 Box 358534, 18115 Campus Way NE fax: +1-425-352-5216 Bothell, WA 98011-8246 USA
-------------------------------------------------------------------- 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] --------------------------------------------------------------------
