<?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 Lock/Unlock and Checkout/Checkin cooperation in Nuxeo Forum</title>
    <link>https://connect.hyland.com/t5/nuxeo-forum/lock-unlock-and-checkout-checkin-cooperation/m-p/321979#M8980</link>
    <description>&lt;P&gt;&lt;A href="https://jira.nuxeo.com/browse/NXP-9260"&gt;NXP-9260&lt;/A&gt; was a first step towards improving the integration between the Lock/Unlock and Checkout/Checkin operations in Nuxeo for both Web and CMIS clients. However, problems remain. My immediate concern is that patch NXP-9260 did not include code to properly calculate the Nuxeo CMIS property cmis:isVersionSeriesCheckedOut (see &lt;A href="https://jira.nuxeo.com/browse/NXP-10659"&gt;NXP-10659&lt;/A&gt;). Currently, this property reports if Nuxeo considers a specific document checked-out and not whether Nuxeo CMIS considers it checked-out (Nuxeo CMIS considers a document checked-out if it is locked or checked-out). Rather than trying to band-aid a patch for this problem, I thought a more comprehensive solution might be appropriate. This would involve making minor changes to the semantics of the core Nuxeo lock, unlock and checkin operations. A summary of the proposed changes follows:&lt;/P&gt;
&lt;P&gt;*lock() - checkOut document if it is versioned and not already checked out&lt;/P&gt;
&lt;P&gt;*unlock() - cancelCheckOut document if it is the latest version&lt;/P&gt;
&lt;P&gt;checkOut() [no changes]&lt;/P&gt;
&lt;P&gt;*checkIn() - if document is locked and versioned, perform checkOut after checkIn&lt;/P&gt;
&lt;P&gt;*cancelCheckOut() [new operation] - restore latest version if it differs from live document&lt;/P&gt;
&lt;P&gt;cmisCheckOut() [no changes] - lock &amp;amp; checkOut document&lt;/P&gt;
&lt;P&gt;cmisCheckIn() [no changes] - checkIn &amp;amp; unlock document&lt;/P&gt;
&lt;P&gt;cmisCancelCheckOut() [no changes] - cancelCheckOut &amp;amp; unlock document&lt;/P&gt;
&lt;P&gt;Is it appropriate to couple the Nuxeo Locking and Versioning mechanisms in such a manner? Is it preferred to implement this type of integration in the web-tier via actions? Do you have other ideas about fixing NXP-10659 in a performant manner?&lt;/P&gt;
&lt;P&gt;Thanks in advance for your feedback.&lt;/P&gt;</description>
    <pubDate>Sat, 29 Dec 2012 14:31:18 GMT</pubDate>
    <dc:creator>ron_1</dc:creator>
    <dc:date>2012-12-29T14:31:18Z</dc:date>
    <item>
      <title>Lock/Unlock and Checkout/Checkin cooperation</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/lock-unlock-and-checkout-checkin-cooperation/m-p/321979#M8980</link>
      <description>&lt;P&gt;&lt;A href="https://jira.nuxeo.com/browse/NXP-9260"&gt;NXP-9260&lt;/A&gt; was a first step towards improving the integration between the Lock/Unlock and Checkout/Checkin operations in Nuxeo for both Web and CMIS clients. However, problems remain. My immediate concern is that patch NXP-9260 did not include code to properly calculate the Nuxeo CMIS property cmis:isVersionSeriesCheckedOut (see &lt;A href="https://jira.nuxeo.com/browse/NXP-10659"&gt;NXP-10659&lt;/A&gt;). Currently, this property reports if Nuxeo considers a specific document checked-out and not whether Nuxeo CMIS considers it checked-out (Nuxeo CMIS considers a document checked-out if it is locked or checked-out). Rather than trying to band-aid a patch for this problem, I thought a more comprehensive solution might be appropriate. This would involve making minor changes to the semantics of the core Nuxeo lock, unlock and checkin operations. A summary of the proposed changes follows:&lt;/P&gt;
&lt;P&gt;*lock() - checkOut document if it is versioned and not already checked out&lt;/P&gt;
&lt;P&gt;*unlock() - cancelCheckOut document if it is the latest version&lt;/P&gt;
&lt;P&gt;checkOut() [no changes]&lt;/P&gt;
&lt;P&gt;*checkIn() - if document is locked and versioned, perform checkOut after checkIn&lt;/P&gt;
&lt;P&gt;*cancelCheckOut() [new operation] - restore latest version if it differs from live document&lt;/P&gt;
&lt;P&gt;cmisCheckOut() [no changes] - lock &amp;amp; checkOut document&lt;/P&gt;
&lt;P&gt;cmisCheckIn() [no changes] - checkIn &amp;amp; unlock document&lt;/P&gt;
&lt;P&gt;cmisCancelCheckOut() [no changes] - cancelCheckOut &amp;amp; unlock document&lt;/P&gt;
&lt;P&gt;Is it appropriate to couple the Nuxeo Locking and Versioning mechanisms in such a manner? Is it preferred to implement this type of integration in the web-tier via actions? Do you have other ideas about fixing NXP-10659 in a performant manner?&lt;/P&gt;
&lt;P&gt;Thanks in advance for your feedback.&lt;/P&gt;</description>
      <pubDate>Sat, 29 Dec 2012 14:31:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/lock-unlock-and-checkout-checkin-cooperation/m-p/321979#M8980</guid>
      <dc:creator>ron_1</dc:creator>
      <dc:date>2012-12-29T14:31:18Z</dc:date>
    </item>
    <item>
      <title>Re: Lock/Unlock and Checkout/Checkin cooperation</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/lock-unlock-and-checkout-checkin-cooperation/m-p/321980#M8981</link>
      <description>&lt;P&gt;Based on this &lt;A href="https://jira.nuxeo.com/browse/NXP-10659?focusedCommentId=130823&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-130823"&gt;comment&lt;/A&gt;, it appears the recommended solution to the CMIS/Nuxeo UI versioning/locking impedence mis-match is to replace the standard web-tier Lock/Unlock actions with Lock &amp;amp; CheckOut/Unlock &amp;amp; CancelCheckOut actions. A possible future enhancement would be to make the web-tier Lock/Unlock action behavior configurable so customers using CMIS would have a solution that works out-of-the-box.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Jan 2013 13:23:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/lock-unlock-and-checkout-checkin-cooperation/m-p/321980#M8981</guid>
      <dc:creator>ron_1</dc:creator>
      <dc:date>2013-01-07T13:23:51Z</dc:date>
    </item>
    <item>
      <title>Re: Lock/Unlock and Checkout/Checkin cooperation</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/lock-unlock-and-checkout-checkin-cooperation/m-p/321981#M8982</link>
      <description>&lt;P&gt;Tickets is [NXP-10734](https&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jan 2013 15:21:21 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/lock-unlock-and-checkout-checkin-cooperation/m-p/321981#M8982</guid>
      <dc:creator>Florent_Guillau</dc:creator>
      <dc:date>2013-01-15T15:21:21Z</dc:date>
    </item>
  </channel>
</rss>

