Dirk, it should be OK. As when you assert a fact with a change listneer (a dymanic fact) it should call the sync'ed modifyObject just like you would form the outside. <br><br><div><span class="gmail_quote">On 2/21/07,
<b class="gmail_sendername">Dirk Bergstrom</b> <<a href="mailto:dirk@juniper.net">dirk@juniper.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This horse has been beaten pretty hard<br>(<a href="http://thread.gmane.org/gmane.comp.java.drools.user/3557/focus=3585">http://thread.gmane.org/gmane.comp.java.drools.user/3557/focus=3585</a>), but I<br>have a newish angle on it.
<br><br>My app has a big collection of business objects (1000 of type X, 10,000 of type<br>Y, 200 of type Z, etc) asserted into a single working memory. These objects<br>need to be updated from external sources periodically. Because each object type
<br>has a different source, I'd like to parallelize the updates in separate threads.<br><br>Some of the updates involve retraction of expired objects or assertion of new<br>ones, but most are just changing fields on already-asserted objects (all fields
<br>have PropertyChangeListener (PCL) support).<br><br>I think that using a SynchronisedWorkingMemory will handle the assert/retract<br>updates. Will it be "happy" in the face of PCL changes as well, or do I need to
<br>do something more?<br><br>--<br>Dirk Bergstrom <a href="mailto:dirk@juniper.net">dirk@juniper.net</a><br>_____________________________________________<br>Juniper Networks Inc., Computer Geek<br>
Tel: 408.745.3182 Fax: 408.745.8905<br>_______________________________________________<br>rules-users mailing list<br><a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-users">
https://lists.jboss.org/mailman/listinfo/rules-users</a><br></blockquote></div><br>