<?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: potentiality and limits of Activiti Engine in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/potentiality-and-limits-of-activiti-engine/m-p/104778#M73205</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The 'problem' you see is core to the Activiti engine. Indeed, the process you posted here will (sometimes) yield optimistic locking exceptions, if both&amp;nbsp; of them are set to be async=true. This is logical, as there will be two independent threads that try to continue the process. In this case, the solution is of course easy to see, but in general there is no good algorithm to figure out if we can safely join or not.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can set the exclusive to true, but you'd lose some of the concurrency you've introduced.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Nov 2012 00:13:55 GMT</pubDate>
    <dc:creator>jbarrez</dc:creator>
    <dc:date>2012-11-14T00:13:55Z</dc:date>
    <item>
      <title>potentiality and limits of Activiti Engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/potentiality-and-limits-of-activiti-engine/m-p/104777#M73204</link>
      <description>Hi all, I've some questions about Potentiality of Activiti Engine. The Problem that i'm going to show you is not for us just a simple technical trouble about Activiti but We need to know if is a Limitation of Activiti Engine or is our ProblemWe're going to develop a platform based on a BPMN Engine.</description>
      <pubDate>Fri, 09 Nov 2012 10:01:22 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/potentiality-and-limits-of-activiti-engine/m-p/104777#M73204</guid>
      <dc:creator>deepyou</dc:creator>
      <dc:date>2012-11-09T10:01:22Z</dc:date>
    </item>
    <item>
      <title>Re: potentiality and limits of Activiti Engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/potentiality-and-limits-of-activiti-engine/m-p/104778#M73205</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The 'problem' you see is core to the Activiti engine. Indeed, the process you posted here will (sometimes) yield optimistic locking exceptions, if both&amp;nbsp; of them are set to be async=true. This is logical, as there will be two independent threads that try to continue the process. In this case, the solution is of course easy to see, but in general there is no good algorithm to figure out if we can safely join or not.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can set the exclusive to true, but you'd lose some of the concurrency you've introduced.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Nov 2012 00:13:55 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/potentiality-and-limits-of-activiti-engine/m-p/104778#M73205</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2012-11-14T00:13:55Z</dc:date>
    </item>
    <item>
      <title>Re: potentiality and limits of Activiti Engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/potentiality-and-limits-of-activiti-engine/m-p/104779#M73206</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;As also discussed via e-mail, there's an opportunity here to leverage the Camel integration with Activiti.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I've created a unit test that shows how you can use SEDA (or JMS) queues in Camel in combination with a Camel service task and a receive task in Activiti to get your use case running.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You can find it here:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://github.com/Activiti/Activiti/blob/master/modules/activiti-camel/src/test/java/org/activiti/camel/route/AsyncCamelRoute.java" rel="nofollow noopener noreferrer"&gt;https://github.com/Activiti/Activiti/blob/master/modules/activiti-camel/src/test/java/org/activiti/camel/route/AsyncCamelRoute.java&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://github.com/Activiti/Activiti/blob/master/modules/activiti-camel/src/test/java/org/activiti/camel/AsyncProcessTest.java" rel="nofollow noopener noreferrer"&gt;https://github.com/Activiti/Activiti/blob/master/modules/activiti-camel/src/test/java/org/activiti/camel/AsyncProcessTest.java&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Nov 2012 07:56:56 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/potentiality-and-limits-of-activiti-engine/m-p/104779#M73206</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2012-11-14T07:56:56Z</dc:date>
    </item>
    <item>
      <title>Re: potentiality and limits of Activiti Engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/potentiality-and-limits-of-activiti-engine/m-p/104780#M73207</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;"The parallel gateway runs every task in sequence by default and this is by design".&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;And this sound's good for BPMN logic but if you need real parallelism the solution with Apache Camel is a elegant and refined solution.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks to all to clear my head about this doubth, Thanks expecially to Tijs Rademakers to all he did for Activiti community, first with his wonderfull book "Activiti in Action" and last but not least for the support that he give every day to the Activiti's users.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best Regards &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Gaetano.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Nov 2012 12:52:24 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/potentiality-and-limits-of-activiti-engine/m-p/104780#M73207</guid>
      <dc:creator>deepyou</dc:creator>
      <dc:date>2012-11-19T12:52:24Z</dc:date>
    </item>
    <item>
      <title>Re: potentiality and limits of Activiti Engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/potentiality-and-limits-of-activiti-engine/m-p/104781#M73208</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;And this sound's good for BPMN logic but if you need real parallelism the solution with Apache Camel is a elegant and refined solution.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, if you need 'true' parallelism. But I've seen very few cases where this was needed from a workflow and BPM engine. There are better frameworks to handle this, in my humble opinion (Camel being one of them). And that is exactly why we have the Camel integration &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Nov 2012 20:20:21 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/potentiality-and-limits-of-activiti-engine/m-p/104781#M73208</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2012-11-19T20:20:21Z</dc:date>
    </item>
  </channel>
</rss>

