Description of problem:
a) Being able to commit a transaction per node transition regardless of synchronous or asynchronous. Hopefully by configuration basis (not additional development effort by users)
b) Recovery support (continuing process instance execution) after JVM reboot (including JVM crash case). The key point is less development effort by users
Toshiya Kobayashi <email@example.com> made a comment on jira JBPM-3889
Attached an example, which demonstrates that commit per node transition with BRMS 5.3.0. The customer doesn't feel nice with it because it requires development on their side and more development if they consider recovery which is described in (b).
FYI : "jBPM5 Developer Guide" Chapter 11 suggests persisting BusinessEntity object to hold ksessionId/processInstanceId/workItemId relation in WorkItemHandler for async WorkItem but it has the same concern... Isn't it too much effort on application side? Can jBPM provide some help out-of-box?