<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Asynchronous continuation and BPMN transactions in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/asynchronous-continuation-and-bpmn-transactions/m-p/47085#M26614</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;This topic kind of follows this old one: &lt;/SPAN&gt;&lt;A href="http://forums.activiti.org/en/viewtopic.php?f=6&amp;amp;t=2605" rel="nofollow noopener noreferrer"&gt;http://forums.activiti.org/en/viewtopic.php?f=6&amp;amp;t=2605&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If I want to enclose multiple tasks in a single transaction, I should do it with BPMN transactions, like this:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://en.q-bpm.org/mediawiki/index.php/Transaction_%28BPMN%29" rel="nofollow noopener noreferrer"&gt;http://en.q-bpm.org/mediawiki/index.php/Transaction_%28BPMN%29&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Does it make sense for you?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Will asynchronous continuation still be necessary on the day that BPMN transactions are supported by Activiti? They seem to have the same purpose.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 15 Dec 2011 12:05:46 GMT</pubDate>
    <dc:creator>andregs</dc:creator>
    <dc:date>2011-12-15T12:05:46Z</dc:date>
    <item>
      <title>Asynchronous continuation and BPMN transactions</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/asynchronous-continuation-and-bpmn-transactions/m-p/47085#M26614</link>
      <description>This topic kind of follows this old one: http://forums.activiti.org/en/viewtopic.php?f=6&amp;amp;t=2605I’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 mult</description>
      <pubDate>Thu, 15 Dec 2011 12:05:46 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/asynchronous-continuation-and-bpmn-transactions/m-p/47085#M26614</guid>
      <dc:creator>andregs</dc:creator>
      <dc:date>2011-12-15T12:05:46Z</dc:date>
    </item>
    <item>
      <title>Re: Asynchronous continuation and BPMN transactions</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/asynchronous-continuation-and-bpmn-transactions/m-p/47086#M26615</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I understand your concerns, but Activiti just has another way of handling transactions.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;So automatic activities like service tasks run in a combined transaction and non-automatic activities will make the engine persist its state.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;With the async continuation support you still can do what you want. I don't think we'll change the default behavior to async.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 Dec 2011 09:48:55 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/asynchronous-continuation-and-bpmn-transactions/m-p/47086#M26615</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2011-12-17T09:48:55Z</dc:date>
    </item>
  </channel>
</rss>

