Re: [rules-users] Maintaining DB/Working Memory Synchronization

It can depend on how you want to use working memory as well. If you are working statelessly, you can load objects through some type of transactional framework, insert them into memory (or the ones relevant to you at that moment in time) let Drools evaluate the objects, make changes and then serialize those changes once rules have stopped firing. I do something like this using EJB and JPA. I've been interested in pushing this into the rules themselves; which I believe is now possible using the JPA support within Drools flow. This might work much better if you were using statefull and long running working memory process. Even in the event of catastrophic failure, your transactionally serialized changes would still remain in the database. So you could restart and pick up work from where you were last. You may wish to take a look at the following blog entries: http://blog.athico.com/2009/03/drools-50-cr1-new-and-noteworthy.html And the Drools flow documentation. I'm hoping to move our work in this direction so please do pass on your results; unless I'm completely misunderstanding how one can use flow, expert and JPA together with transactions. best wishes, Andrew On Sat, Nov 7, 2009 at 9:23 AM, ken.p <ken.annihilation(a)gmail.com&gt; wrote: -- +1 510 342 5693 PO Box 7775 #8750 San Francisco, California 94120-7775 "Warning: following standard input indefinitely is ineffective" - /bin/tail error message "Against logic there is no armor like ignorance." - Laurence J. Pete