(using jbpm-jpdl-3.2.GA) This raises a point I could use some clarification on.
We ended up removing the unique constraint: | unique (KEY_, PROCESSDEFINITION_) | from the JBPM_PROCESSINSTANCE table because it was causing a key violation when we started multiple processes using: | jbpmContext.newProcessInstance(String processDefinitionName) | We don't understand why we had to do that. If the key must be unique, I would expect to see the key as a parameter in "newProcessInstance(..)" -- in fact, how do you even set the key?! But in answer to tom_goring's question, he could do what we did, remove the unique constraint, then get the ProcessInstance with the highest version number for that key (or maybe there is another field that indicates that a process is not ended). I'd like to learn more how this "KEY" is intended to be used, set, etc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140240#4140240 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140240 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
