<?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 Infinite onContentUpdate loop when a node is versionable in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/infinite-oncontentupdate-loop-when-a-node-is-versionable/m-p/183821#M136951</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Version: Alfresco Enterprise 3.0.0 (trial)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We have several policies that are registered to fire on the onContentUpdate event of some node types.&amp;nbsp; Each policy reads the node content and creates a property.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;These policies work fine for nodes that are not versionable.&amp;nbsp;&amp;nbsp; However, if we make a node versionable, we get into an infinite loop:&amp;nbsp; the onContentUpdate event just keeps firing.&amp;nbsp; The first time, newContent is false.&amp;nbsp; Every time after that, newContent is true.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It seems like the action of reading the node's content (done in each policy) is causing the onContentUpdate event to be triggered again - only when the node is versionable. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I did a bit of searching through the forums, but could not find a similar problem.&amp;nbsp; Has anyone else encountered this?&amp;nbsp; If so, how have you avoided it?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Dec 2008 21:29:53 GMT</pubDate>
    <dc:creator>dwarren</dc:creator>
    <dc:date>2008-12-12T21:29:53Z</dc:date>
    <item>
      <title>Infinite onContentUpdate loop when a node is versionable</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/infinite-oncontentupdate-loop-when-a-node-is-versionable/m-p/183821#M136951</link>
      <description>Version: Alfresco Enterprise 3.0.0 (trial)We have several policies that are registered to fire on the onContentUpdate event of some node types.&amp;nbsp; Each policy reads the node content and creates a property.These policies work fine for nodes that are not versionable.&amp;nbsp;&amp;nbsp; However, if we make a node version</description>
      <pubDate>Fri, 12 Dec 2008 21:29:53 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/infinite-oncontentupdate-loop-when-a-node-is-versionable/m-p/183821#M136951</guid>
      <dc:creator>dwarren</dc:creator>
      <dc:date>2008-12-12T21:29:53Z</dc:date>
    </item>
    <item>
      <title>Re: Infinite onContentUpdate loop when a node is versionable</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/infinite-oncontentupdate-loop-when-a-node-is-versionable/m-p/183822#M136952</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Found the problem:&amp;nbsp;&amp;nbsp; our policies were running on the previous version of a node (workspace://version2store) as well as the current version (workspace://SpacesStore).&amp;nbsp;&amp;nbsp; I put a check in the onContentUpdate() method of our policies to only do work if the node's Store is workspace://SpacesStore.&amp;nbsp; This fixed the issue.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Dec 2008 20:13:42 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/infinite-oncontentupdate-loop-when-a-node-is-versionable/m-p/183822#M136952</guid>
      <dc:creator>dwarren</dc:creator>
      <dc:date>2008-12-15T20:13:42Z</dc:date>
    </item>
  </channel>
</rss>

