<?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 Re: Transaction handler in Activiti Engine in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/transaction-handler-in-activiti-engine/m-p/35455#M18625</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;When the process reaches a wait-state (eg. userTask) the process-variables and execution-state are stored in the DB and the DB-transaction is commited. When the user eventually completes the task, a new transaction is started and the process flows on in that transaction untill the next wait-state or process-end.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So the transaction doesn't run over the whole process if the process contains waitstates (or in the furture, asynchronous continuations).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hope this makes sense&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Mar 2011 09:55:28 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2011-03-09T09:55:28Z</dc:date>
    <item>
      <title>Transaction handler in Activiti Engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/transaction-handler-in-activiti-engine/m-p/35454#M18624</link>
      <description>Hi,I have a small question about how Activiti handles long transaction in the following case:The process enters a userTask and it waits for an action from the user. The question is&lt;IMG id="smileysad" class="emoticon emoticon-smileysad" src="https://migration33.stage.lithium.com/i/smilies/16x16_smiley-sad.png" alt="Smiley Sad" title="Smiley Sad" /&gt;1) Are the current process variables committed into the database automatically (for long running transaction and data</description>
      <pubDate>Mon, 07 Mar 2011 13:33:42 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/transaction-handler-in-activiti-engine/m-p/35454#M18624</guid>
      <dc:creator>ryu</dc:creator>
      <dc:date>2011-03-07T13:33:42Z</dc:date>
    </item>
    <item>
      <title>Re: Transaction handler in Activiti Engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/transaction-handler-in-activiti-engine/m-p/35455#M18625</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;When the process reaches a wait-state (eg. userTask) the process-variables and execution-state are stored in the DB and the DB-transaction is commited. When the user eventually completes the task, a new transaction is started and the process flows on in that transaction untill the next wait-state or process-end.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So the transaction doesn't run over the whole process if the process contains waitstates (or in the furture, asynchronous continuations).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hope this makes sense&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Mar 2011 09:55:28 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/transaction-handler-in-activiti-engine/m-p/35455#M18625</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2011-03-09T09:55:28Z</dc:date>
    </item>
  </channel>
</rss>

