Re: [rules-users] JPA persistence for Drools Flow

Marc, As Mauricio already pointed out, we have already have very concrete plans in adding separate persistence of process instance variables in the database. I expect this to be added to trunk in a few weeks time. This will allow pluggable persistence managers for all your variables based on the type of the variable (class or annotation). By default, we will include support for simply storing the value directly and support for JPA entities (as they are already stored separately), with the possibility to register other strategies. As you also noticed correctly, persistence is implemented orthogonally. This means it is indeed possible to completely replace the persistence with your own. We do however try to provide the most common feature requests out of the box, and you're lucky as separate variable persistence is one of them :) Another strategy that might be useful in a lot of use cases (not sure what yours is exactly so not sure it applies) is not querying on the runtime database but getting the information from the history logs. The drools-bam module for example shows how information about all running process instances (their state, which nodes were triggered, etc.) can be stored in a database. As this is implemented based on the generic listener interface, you can use this to create a persistent log of information using the model that suits your use cases. Notice that a history log is not only about completed process instances, but about currently executing ones as well. The advantage of this approach is that queries on the history log won't ever impact your running sessions and you can define what data to store yourself (and how), optimized to your use case. Kris ----- Original Message ----- From: "Marc Dzaebel" <mdzaebel(a)web.de&gt; To: <rules-users(a)lists.jboss.org&gt; Sent: Tuesday, April 07, 2009 12:30 AM Subject: [rules-users] JPA persistence for Drools Flow