<?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 Activiti service level optimistic locking in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/activiti-service-level-optimistic-locking/m-p/196258#M149388</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hey,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have a process variable that many users can modify simultaneusly via their user tasks. For example a list, and users can add and remove elements to it. User A and B both see v1 of variable on their screen, then A updates it. Using RuntimeService, the version information is lost for the variable, and user B can easily overwrite the process variable: no optimistic locking.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I there any way to enforce optimistic locking on process variables in service level like the @version annotation on a JPA entity?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The problem is that when using RuntimeService, TaskService, the version info is lost.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have 3 options:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Either try creating my own locks as process variables&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Store the same information for the different users in different process variables then somehow merge them together&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- I create a new service api for VariableInstanceEntity-s&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Pal&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 24 Nov 2014 16:28:51 GMT</pubDate>
    <dc:creator>pkonyves</dc:creator>
    <dc:date>2014-11-24T16:28:51Z</dc:date>
    <item>
      <title>Activiti service level optimistic locking</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-service-level-optimistic-locking/m-p/196258#M149388</link>
      <description>Hey,I have a process variable that many users can modify simultaneusly via their user tasks. For example a list, and users can add and remove elements to it. User A and B both see v1 of variable on their screen, then A updates it. Using RuntimeService, the version information is lost for the variabl</description>
      <pubDate>Mon, 24 Nov 2014 16:28:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-service-level-optimistic-locking/m-p/196258#M149388</guid>
      <dc:creator>pkonyves</dc:creator>
      <dc:date>2014-11-24T16:28:51Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti service level optimistic locking</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-service-level-optimistic-locking/m-p/196259#M149389</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Yes, that's a good point. We do store revisions for variable values so it would be possible to throw an optimistic locking exception. I think writing a API in RuntimeService to get a VariableInstance object instead of a plain name and value could solve this issue elegantly. Would you be willing to create a pull request for this?&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>Tue, 25 Nov 2014 10:09:09 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-service-level-optimistic-locking/m-p/196259#M149389</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2014-11-25T10:09:09Z</dc:date>
    </item>
  </channel>
</rss>

