<?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 Deploying current version of classes with process definition in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/deploying-current-version-of-classes-with-process-definition/m-p/44534#M24559</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Our usecase is, that after delivery of new release of our system we would like to be able to finish old process instances. We are going to have couple specialized service tasks. Their implementation may change with the future software releases. What we would like to achieve could be:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - process instances that are still running should use the previous version of service task implementation classes&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - all newly started instances would use current (provided by software release) classes&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Main idea is to deploy classes with process definition or inside our bpm component and load proper version during process instance runtime. Is there any mechanism in the engine that would allow to do that? Or maybe you have some other solution to this issue?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 08 Nov 2011 13:33:41 GMT</pubDate>
    <dc:creator>pgadecki</dc:creator>
    <dc:date>2011-11-08T13:33:41Z</dc:date>
    <item>
      <title>Deploying current version of classes with process definition</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/deploying-current-version-of-classes-with-process-definition/m-p/44534#M24559</link>
      <description>Our usecase is, that after delivery of new release of our system we would like to be able to finish old process instances. We are going to have couple specialized service tasks. Their implementation may change with the future software releases. What we would like to achieve could be: - process insta</description>
      <pubDate>Tue, 08 Nov 2011 13:33:41 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/deploying-current-version-of-classes-with-process-definition/m-p/44534#M24559</guid>
      <dc:creator>pgadecki</dc:creator>
      <dc:date>2011-11-08T13:33:41Z</dc:date>
    </item>
    <item>
      <title>Re: Deploying current version of classes with process definition</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/deploying-current-version-of-classes-with-process-definition/m-p/44535#M24560</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;there has been a lot of discussion on classloader scoping. Search the forum for more info (might also be in the dev forum)&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Nov 2011 16:26:36 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/deploying-current-version-of-classes-with-process-definition/m-p/44535#M24560</guid>
      <dc:creator>ronald_van_kuij</dc:creator>
      <dc:date>2011-11-08T16:26:36Z</dc:date>
    </item>
  </channel>
</rss>

