Look in your hibernate.cfg.xml file if your hbm2ddl is set to drop-create...
this may be the cause
Wouldn't "drop-create" drop all the tables and therefore I'd never see more than one instance?
You are right, I don't know why I put that...
tell me more about your scenario...
what do you mean when you said
a new version of a process
The JBPM Console has this:
Process ID Process Name Version 319 migration 4 241 migration 3 131 migration 2 1 migration 1
The process definition has not changed.
What class in the spring module are you using?
I'm using the JBPM Spring Module
Here's my definitions
<bean id="jbpmConfiguration" class="org.springmodules.workflow.jbpm31.LocalJbpmConfigurationFactoryBean"> <property name="sessionFactory" ref="mmSessionFactory" /> <property name="configuration" value="classpath:/jbpm.cfg.xml" /> <property name="processDefinitionsResources"> <list> <value>classpath:/foo/bar/migration/processdefinition.xml</value> </list> </property> </bean> <bean id="jbpmTemplate" class="org.springmodules.workflow.jbpm31.JbpmTemplate"> <constructor-arg index="0" ref="jbpmConfiguration" /> </bean>
if you google that class you will find this:
This tells you that the process definition will be deployed every time that you start up your server
Ok, it seems that manually deploying a process is the best solution unless it's a testing thing.
Yes, the sping jBPM template is also not very up to date. You miss jbpm 3.2 functionality and it is as usefull as the hibernate template (imo not useful at all). You can configure jBPM via spring afaik, but I'd ditch the template. It caused us (the company I worked for) more problems than it solved.