topic Transaction boundaries on errors. in Alfresco Archive

Transaction boundaries on errors.

bwd — Tue, 17 May 2011 20:24:36 GMT

Hi,I have a workflow that has a user task followed by a java service task. I ran a test where the task was completed, after which the java service task ran, which threw an exception (due to a data error on my part). My expectation was that the task itself would be complete (because it had to be co

Re: Transaction boundaries on errors.

bwd — Tue, 17 May 2011 20:39:09 GMT

I do see this in the FAQ: http://www.activiti.org/faq.html#WhatIsTheDifferenceBetweenProcessConcurrencyAndJavaConcurrency

"The behavior of Activiti Engine to calculate possibly multiple steps in a process until a wait state is reached is the default behavior. Asynchronous continuations will be introduced to allow for a more fine grained demarcation of transactions for those situations where it is needed."

Does this mean that we can rely on having a single transaction for a sequence of constructs that don't contain a wait construct? If so, is this the long-term behavior, or is it subject to change as the engine evolves?

Thanks,

BD

Re: Transaction boundaries on errors.

ronald_van_kuij — Tue, 17 May 2011 21:30:45 GMT

Does this mean that we can rely on having a single transaction for a sequence of constructs that don't contain a wait construct?

Yes

If so, is this the long-term behavior, or is it subject to change as the engine evolves?

Both, since it is a non-bpmn construct, it might be subject to (small) changes/improvements I think, but stable enough to rely on it for llong term