<?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 Long Java Service Task in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/long-java-service-task/m-p/186798#M139928</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have a java service task that takes a long time to execute. While the service task is executing, a get request using the REST api returns that the current activity is the last user task. Is there any call that I can make using the REST api to determine that the java service task is in the middle of execution.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Jun 2014 20:18:58 GMT</pubDate>
    <dc:creator>rschneidman</dc:creator>
    <dc:date>2014-06-11T20:18:58Z</dc:date>
    <item>
      <title>Long Java Service Task</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/long-java-service-task/m-p/186798#M139928</link>
      <description>I have a java service task that takes a long time to execute. While the service task is executing, a get request using the REST api returns that the current activity is the last user task. Is there any call that I can make using the REST api to determine that the java service task is in the middle o</description>
      <pubDate>Wed, 11 Jun 2014 20:18:58 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/long-java-service-task/m-p/186798#M139928</guid>
      <dc:creator>rschneidman</dc:creator>
      <dc:date>2014-06-11T20:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: Long Java Service Task</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/long-java-service-task/m-p/186799#M139929</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;If you would use a async Java service task, you can query and see that the current state is the service task execution.&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>Thu, 12 Jun 2014 08:11:31 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/long-java-service-task/m-p/186799#M139929</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2014-06-12T08:11:31Z</dc:date>
    </item>
    <item>
      <title>Re: Long Java Service Task</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/long-java-service-task/m-p/186800#M139930</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 think you can make service task asynchronous (it has other side effects too).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Martin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Jun 2014 08:14:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/long-java-service-task/m-p/186800#M139930</guid>
      <dc:creator>martin_grofcik</dc:creator>
      <dc:date>2014-06-12T08:14:23Z</dc:date>
    </item>
    <item>
      <title>Re: Long Java Service Task</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/long-java-service-task/m-p/186801#M139931</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I think that long running tasks (java or anything else, like shell tasks, with run times from few minutes to even hours) are better modeled by a task executed by an external actor. Following this line of thinking, what I&amp;nbsp; prefer to do is to model those tasks as a "Human Task", assigned to a particular group or user - a job runner group, for instance.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can choose a polling strategy (eg, using the REST api) or a task listener in order to kick off your tasks. This approach _will_ add extra complexity to your environment, but OTOH your jobs will be completely decoupled from the process, something that can be handy if you are reusing existing stuff link bash scripts or the like. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jun 2014 23:29:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/long-java-service-task/m-p/186801#M139931</guid>
      <dc:creator>pmsevestre</dc:creator>
      <dc:date>2014-06-20T23:29:30Z</dc:date>
    </item>
  </channel>
</rss>

