<?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: HistoryManager in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/historymanager/m-p/178738#M131868</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;1)b) I see that the docs are wrong there. But we can't change that now, that would break too many installations.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;3) Why do you believe it is not used? The way I read it, it is used.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;4) Why would DAO be the best way forward? Cause it used to be a best practice in the get-as-many-layers-as-possible-java? Activiti has to cater for many different environments and the current architecture is an evolution reflecting that. I'm not saying you're wrong, I'm just saying that Activiti is 5 years old and has been used in many (many!) different environments and has grown like that because of it.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Mar 2015 08:36:43 GMT</pubDate>
    <dc:creator>jbarrez</dc:creator>
    <dc:date>2015-03-17T08:36:43Z</dc:date>
    <item>
      <title>HistoryManager</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/historymanager/m-p/178737#M131867</link>
      <description>Hi,I'm using activiti 5.14 and I want to ask some questions about HistoryManager implementation..1- HistoryManager implementation is different from manual (activity vs audit).1.a) Although it says controlling ACTIVITY level, implementation controls ACTIVITY, as:&amp;nbsp; /**&amp;nbsp;&amp;nbsp; * Record a variable has been u</description>
      <pubDate>Tue, 10 Mar 2015 13:52:22 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/historymanager/m-p/178737#M131867</guid>
      <dc:creator>baivs</dc:creator>
      <dc:date>2015-03-10T13:52:22Z</dc:date>
    </item>
    <item>
      <title>Re: HistoryManager</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/historymanager/m-p/178738#M131868</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;1)b) I see that the docs are wrong there. But we can't change that now, that would break too many installations.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;3) Why do you believe it is not used? The way I read it, it is used.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;4) Why would DAO be the best way forward? Cause it used to be a best practice in the get-as-many-layers-as-possible-java? Activiti has to cater for many different environments and the current architecture is an evolution reflecting that. I'm not saying you're wrong, I'm just saying that Activiti is 5 years old and has been used in many (many!) different environments and has grown like that because of it.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Mar 2015 08:36:43 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/historymanager/m-p/178738#M131868</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2015-03-17T08:36:43Z</dc:date>
    </item>
  </channel>
</rss>

