Aug 21st, 2008, 06:07 AM
LocalJbpmConfigurationFactoryBean deploy of new version of process
When you use LocalJbpmConfigurationFactoryBean each time you deploy the application a new process definition is deployed (even if not changed).
Because of that jbpmtemplate.findProcessInstances() returns an empty list. (becasue the existing instances have a different definition version).
What is the reason for deployment on each application deploy?
Aug 26th, 2008, 10:04 PM
I also come to this problem now,after seeking the source code,I'm afraid that this has nothing to do with springmodel,it's jBPM itself that deploying the definition repeatedly.It seems jBPM is not 'clever' enough to find out the change of the definition.
But I have no good solution to this problem either,perhaps we need to modify the source code of org.jbpm.db.GraphSession's deployProcessDefinition method?Or we must write some more code to specify when to really deploy the process definition as a separate (spring aware) module.
Let's see if some one others could give a more ideal answer.
Aug 27th, 2008, 08:59 AM
I do not use jbpmtemplate.findProcessInstances() anymore.
findPooledTaskInstances and findTaskInstances seems to work ok.