Asynchronous continuation and BPMN transactions

[andregs]

This topic kind of follows this old one: http://forums.activiti.org/en/viewtopic.php?f=6&t=2605

I’m rethinking here and I still argue that each user task, service task, call activity etc. should be executed in its own transaction. I mean, activiti:async="true" by default.

If I want to enclose multiple tasks in a single transaction, I should do it with BPMN transactions, like this:

http://en.q-bpm.org/mediawiki/index.php/Transaction_%28BPMN%29

Does it make sense for you?

Will asynchronous continuation still be necessary on the day that BPMN transactions are supported by Activiti? They seem to have the same purpose.

Regards,

[trademak]

Hi,

I understand your concerns, but Activiti just has another way of handling transactions.
So automatic activities like service tasks run in a combined transaction and non-automatic activities will make the engine persist its state.
With the async continuation support you still can do what you want. I don't think we'll change the default behavior to async.

Best regards,