<?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 Best practice for managing version of external resources? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/best-practice-for-managing-version-of-external-resources/m-p/181933#M135063</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am new to Activiti and have spent the better part of the last two weeks reading and working through the basics. I have a working development and deployment environment and have developed several simple workflows that use external resources. I have been using Activiti Explorer to deploy the workflow definitions and copying the supporting JAR file to activiti-explorer/WEB-INF/lib. When re-deploying, Activiti takes care of versioning of the workflow (and so any in-process workflows use the right version and new worflows use the latest).&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;After working with deployment/re-deployment, I now realize that if the supporting business logic in the JAR file changes then I need to be able to address the issue of version there as well (so the workflow version matches the backing logic). It doesn't appear that this capability is built-in to Activiti (but please correct me if that's inaccurate - I'd be happy to be wrong &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My question is - what is considered best practice for managing versions of external resources?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Bruce.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Nov 2014 13:01:00 GMT</pubDate>
    <dc:creator>dbrucegrant</dc:creator>
    <dc:date>2014-11-11T13:01:00Z</dc:date>
    <item>
      <title>Best practice for managing version of external resources?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/best-practice-for-managing-version-of-external-resources/m-p/181933#M135063</link>
      <description>I am new to Activiti and have spent the better part of the last two weeks reading and working through the basics. I have a working development and deployment environment and have developed several simple workflows that use external resources. I have been using Activiti Explorer to deploy the workflo</description>
      <pubDate>Tue, 11 Nov 2014 13:01:00 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/best-practice-for-managing-version-of-external-resources/m-p/181933#M135063</guid>
      <dc:creator>dbrucegrant</dc:creator>
      <dc:date>2014-11-11T13:01:00Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for managing version of external resources?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/best-practice-for-managing-version-of-external-resources/m-p/181934#M135064</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have checked a number of posts and don't yet have a concrete answer.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Nov 2014 20:06:44 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/best-practice-for-managing-version-of-external-resources/m-p/181934#M135064</guid>
      <dc:creator>dbrucegrant</dc:creator>
      <dc:date>2014-11-19T20:06:44Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for managing version of external resources?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/best-practice-for-managing-version-of-external-resources/m-p/181935#M135065</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;No this is not build-in. You will need to version the logic yourself, either by different class names/packages/etc..&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Nov 2014 08:45:29 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/best-practice-for-managing-version-of-external-resources/m-p/181935#M135065</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2014-11-20T08:45:29Z</dc:date>
    </item>
  </channel>
</rss>

