[jboss-jira] [JBoss JIRA] Closed: (JBPM-961) Save not required on jbpmContext operations

[Tom Baeyens (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBPM-961?page=all ]

Tom Baeyens closed JBPM-961.
----------------------------

    Resolution: Won't Fix

i have seen situations where an object loaded through hibernate got modified and didn't get persisted automatically.  but that might have been a bug on my side as max said that should never be the case.

still it's not possible because saving a process instance does more then just delegating to the hibernate save.  also the logs are inserted and other operations are executed.  there is actually a configurable list of SaveOperations that can be configured.

> 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