chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Florian Müller (JIRA) <>
Subject [jira] [Commented] (CMIS-365) Workbench tool 'cancel checkout' will delete the entire version series (data loss)
Date Thu, 05 May 2011 19:37:03 GMT


Florian Müller commented on CMIS-365:

You are right that the PWC need not be filed and that's actually not the problematic part.
The "issue" is that the Workbench doesn't let you access any non-filed objects. So, in your
case, the PWC is not visible through the Workbench and therefore you neither can check it
in nor cancel the check out.

I don't think the original document should accept check-in and chancel-check-out requests.
The latter cannot be distinguished from a delete request... 

> Workbench tool 'cancel checkout' will delete the entire version series (data loss)
> ----------------------------------------------------------------------------------
>                 Key: CMIS-365
>                 URL:
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-workbench
>    Affects Versions: OpenCMIS 0.4.0
>         Environment: IBM P8 CMIS server implementation and latest OpenCMIS workbench.

>            Reporter: jay brown
>            Assignee: Florian Müller
>             Fix For: OpenCMIS 0.4.0
> While using OpenCMIS workbench:
> (Version: 0.4.0-SNAPSHOT / Build: 20110426-2129)
> Using the workbench to perform a 'cancel checkout' will delete the entire version series
in the following scenario (and perhaps others)
> (all steps performed with the workbench version above)
> (all steps include a refresh step in between to verify that object is current)
> -Create a doc. (as major) (refer to this as V1)
> -Checkout the doc.  
> -Checkin the doc.  (refer to this as V1)
> (you can now verify that there are two versions)
> -Checkout the doc. (refer to the working copy as 'pwc')
> -Cancel checkout on the doc. 
>   Performing a trace on this step shows that the workbench requests a delete on the id
for doc V2 instead of the id for the PWC.   This correctly results in deleting the entire
version series since there were no additional/optional parameters specified, resulting in
data loss that user would not expect.
> In our CMIS implementation (where this occurs) our PWC objects have a separate/unique
id than the version that preceded them.  Not sure if this is related but it is certainly spec
> If you would like to get access to the IBM server used in this scenario please let me
know.  It is the same one that we have used in the past for interop work.  

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message