What I did was to _not_ call firePropertyChange() multiple times. Instead, I concatenate all of my bean's old and new properties into two Strings, then compare them to see if any property has changed. If so, if call firePropertyChange() _once_, with a PropertyChangeEvent that has a null property name. This causes DefinstanceList.updateMultipleSlots() to be called within Jess, I believe --- in other words, Jess will properly do a single update of _all_ shadow fact slots.
So, is this problematic in some way? For this application, it seems to work. Of course, I only have one of these bean objects and shadow facts, and am not sure if there would be problems if multiple ones existed...
-- 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] --------------------------------------------------------------------
