Hi, Working on adding support spring to flow, here you have an example app: http://www.plugtree.com/downloads/DroolsFlowSpring.tgz -- Baunax On Friday 21,May,2010 11:00 AM, xdirewolfx wrote:

The current implementation is based on JPA, so it's mandatory to use an EntityManagerFactory. Could you give us more detail on how are accessing the DB and which persistence mechanism are you using? Thanks, On Friday 21,May,2010 12:49 PM, xdirewolfx wrote:

If you don't want to change your app to use JPA. You still can switch to start using JTA as a transaction manager. Doing that would allow you use the same transaction in your code and in drools flow. I've never done that by myself but I'm 97% sure it is doable. On Saturday 22,May,2010 12:45 AM, xdirewolfx wrote:

Anyone managed to get drools flow persistence to be configured in a spring hibernate app? -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-Persisten... Sent from the Drools - User mailing list archive at Nabble.com.

hi there, we r already using Drools Flow + Spring 3.0 + Hibernate JPA it works fine in our case any help....will be very glad.... Drools at beginning has some clutters.....but as u come over it.....u'll what magnificent things they have in there Cheer's ----- Keep Working >> KiranP -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-Persisten... Sent from the Drools - User mailing list archive at Nabble.com.

@xdirewolfx, Well, there is always a choice, any Hollywood movie will tell you that :) It all really comes down to two things: 1. Transaction Management 2. Decoupling your persistence from Drools Flow persistence 1. Transaction Management If you already have Spring + Hibernate working app with all the AOP or annotational TX in place, that would mean that at run time you already have those proxies ( Spring TX ones ) that guard certain methods of your entities. Now you are plugging in the Drools Flow. You would still need to have a simple "persistence.xml" for Drools Flow tables ( 3 to 5 tables ), that has Hibernate as your provider + you would reuse your existing JTA transaction manager. Now we are smoothly transitioning to the second part.. 2. Decoupling your persistence from Drools Flow persistence The most interesting part about Drools Flow is of course suspending and resuming later functionality, or what "they" refer to as a "long running process". What really happens is, whenever you have a work item ( or an Activity, if we are talking BPMN2 ), it has a custom handler attached to it. Whenever a process ( flow ) get to this work item, it delegates its processing to this handler. Now, the handler have a choice to either complete this work item, or "let it be". And in case of the latter, since the work item is not completed, the process ( flow ) goes to sleep or.. suspends. There are certain Drools tables ( WorkItemInfo and ProcessInstanceInfo ) that will have a snapshot of this last alive point before the flow went to sleep. And here you have a dilemma.. If you have a strictly non-JPA policy, you can simply call your DAOs ( or the new, "cool" way to call them.. Repositories ) from within this handler, so everything that needs to be persisted will be. The only problem with this approach is resuming, since now when you reload the process, you need to restore that same state ( of your entities that Drools did not take a part in persisting ). But remember in order to resume the process, you need to COMPLETE that activity that is waiting to be completed, so what you can do you can reload those entities, and pass them back as a map ( "results" ) on this Activity completion. If you really want to get clever, you can hook up your persistence services to something that is called "variable persistence", where you write your own Drools Variable Persister, which calls your services to persist your entities automatically when the flow / process goes to sleep, and reloads them when the process resumes, but that is whole other can of worms :) The idea here was to give you a perspective, and to show that yes, you still have a choice :) /Anatoly -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-Persisten... Sent from the Drools - User mailing list archive at Nabble.com.