<?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 simulating receivetask + signal activiti (step) in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/simulating-receivetask-signal-activiti-step/m-p/90847#M61929</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Goal: to be able to run multiple instances of a call-activiti or subprocess is a separate java thread.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I observed the following issue with async-continuation + call-activiti loop:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;start -&amp;gt; serviceTask1 -&amp;gt; loop Call-Activiti -&amp;gt; end&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The above does not result into "multiple-threads" when call-activiti has more than one instances.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;workarounds:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1- if I remove serviceTask1: async-continuation (multithreading) works as expected where each instance of call-activiti is executed is a separate thread2&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2- if I insert a wait state (eg receive task) "before" call-activiti such as: start -&amp;gt; serviceTask1 -&amp;gt; receiveTask -&amp;gt; loop Call-Activiti -&amp;gt; end&amp;nbsp;&amp;nbsp;&amp;nbsp; ===&amp;gt; async-continuation (multithreading) works as expected&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Now, I cannot use the first workaround.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;For the second workaround, is there a way to automatically add a wait state e.g. receiveTask + signal in front of a call-activiti? Can I achieve this, for example, using custom Bpmn parser or using listener?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thoughts, comments appreciated.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;pdt&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 14 Aug 2012 00:58:38 GMT</pubDate>
    <dc:creator>workflowuser2</dc:creator>
    <dc:date>2012-08-14T00:58:38Z</dc:date>
    <item>
      <title>simulating receivetask + signal activiti (step)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/simulating-receivetask-signal-activiti-step/m-p/90847#M61929</link>
      <description>Goal: to be able to run multiple instances of a call-activiti or subprocess is a separate java thread.Hi,I observed the following issue with async-continuation + call-activiti loop:start -&amp;gt; serviceTask1 -&amp;gt; loop Call-Activiti -&amp;gt; endThe above does not result into "multiple-threads" when call-</description>
      <pubDate>Tue, 14 Aug 2012 00:58:38 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/simulating-receivetask-signal-activiti-step/m-p/90847#M61929</guid>
      <dc:creator>workflowuser2</dc:creator>
      <dc:date>2012-08-14T00:58:38Z</dc:date>
    </item>
    <item>
      <title>Re: simulating receivetask + signal activiti (step)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/simulating-receivetask-signal-activiti-step/m-p/90848#M61930</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;Automatically adding a wait state would be something you could do in a custom pre or post BpmnParseListener.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;For an example you can look at the HistoryParseListener implementation, in the Activiti Engine source code.&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>Wed, 15 Aug 2012 07:40:34 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/simulating-receivetask-signal-activiti-step/m-p/90848#M61930</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2012-08-15T07:40:34Z</dc:date>
    </item>
    <item>
      <title>Re: simulating receivetask + signal activiti (step)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/simulating-receivetask-signal-activiti-step/m-p/90849#M61931</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi trademark&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thanks for the reply.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I looked at the HistoryParseListener&amp;nbsp; and saw that we can attach Execution Listeners to the activities.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Could you explain a bit more on how to "add" a new step (activiti) in a custom parse listener. Since wait state is not in the process bpmn20.xml definition file, how can we automatically add it thorugh parse listener or execution listener?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;pdt&lt;/SPAN&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;Automatically adding a wait state would be something you could do in a custom pre or post BpmnParseListener.&lt;BR /&gt;For an example you can look at the HistoryParseListener implementation, in the Activiti Engine source code.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2012 17:30:41 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/simulating-receivetask-signal-activiti-step/m-p/90849#M61931</guid>
      <dc:creator>workflowuser2</dc:creator>
      <dc:date>2012-08-15T17:30:41Z</dc:date>
    </item>
  </channel>
</rss>

