[
http://jira.jboss.com/jira/browse/JBPM-961?page=comments#action_12412566 ]
joy wind commented on JBPM-961:
-------------------------------
Yes , in jbpm3.2.2, It's seemed no need to call jbpmContext.save(aProcessInstance).
The jbpmContext.close() method will save the process instance automaticly.
Am I wrong ? how can I close the jbpmContext but not save the process instance ?
Save not required on jbpmContext operations
-------------------------------------------
Key: JBPM-961
URL:
http://jira.jboss.com/jira/browse/JBPM-961
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2
Reporter: Jeff DeLong
Assigned To: Tom Baeyens
Priority: Minor
Save (or ForUpdate methods) do not appear to be required on jbpmContext operations.
In the javadocs for JbpmContext it says
...do your process operations...
// in case you update a process object that was not fetched
// with a .. ForUpdate method, you have to save it
jbpmContext.save(processInstance);
...
"All of the ...ForUpdate(...) methods will automatically save the loaded object at
jbpmContext.close();
I have verified through JUnit tests that indeed saving of ProcessInstance and
TaskInstance is not required, the state will still be persisted.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira