VersioningService cancelCheckout: How to unlock an object without purging it

ndegroff

To whom it may concern,

We're on the bleeding edge trying to implement the latest 6.7 version of CMIS with Documentum and ran into an issue concerning a definition of CMIS spec 1.0 and the implementation.  Because the 6.7 implementation of CMIS currently doesn't support PWC, when you check out an object, you are returned the identifier of the actual version.  If you have a need to "VersioningService.cancelCheckOut()", the CMIS spec defines it as:

Description: Reverses the effect of a check-out. Removes the private working copy of the checked-out document, allowing other documents in the version series to be checked out again

Since the ACTUAL ID is returned, a cancelCheckout actually removes the actual version and has the effect of DELETING the actual object rather than simply cancelling the checkout and unlocking the object.

Reading the CMIS spec, we also noted that for checkIn:

For repositories that do NOT support the optional capabilityPWCUpdatable" capability, the properties and contentStream input parameters MUST be provided on the checkIn method for updates to happen as part of checkIn.

This lead us to believe that if we called the VersioningService.checkIn() keeping properties and contentStream null, it would unlock it without versioning.  However, it still versioned the piece.

Any advice on how to unlock an object without purging it would be appreciated.

ndegroff

Just a follow up on my question.  The client I was using was OpenCMIS client 0.3.0.  We found after some investigation that the OpenCMIS client assumed that the PWC was being passed in so it grabbed the AtomPub URL linked to the "self" relationship and not "working-copy".  After talking with the OpenCMIS group, they modified the cancelCheckOut to always grab the "working-copy" and it seems to send the appropriate

HTTP DELETE

message for the checked out item.  This is going to be built into OpenCMIS 0.4.0 and later.