[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-657) ClarifycancelCheckout's proper behavior when doc was created in a checked outstate.
[ http://tools.oasis-open.org/issues/browse/CMIS-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19402#action_19402 ]
Jay Brown commented on CMIS-657:
--------------------------------
From the meeting this morning we had three different (distinct) implementations/interpretations as follows. (there may be more - if so please append and assign the next ordinal to you interpretation)
In our scenario we have a new doc that was created in a 'checked out' state. (Has never been checked in) Below please find the state of each of the interpretations after the initial creation and after the cancel/checkout.
State: Immediately after creation:
Interpretation 1:
Version = [not available] since it is not been checked in yet.
Interpretation 2:
Version = [not available] since it is not been checked in yet.
Interpretation 3:
Version = 1.0
State: After Cancel checkout operation on this document:
Interpretation 1:
Cancel checkout removes the reserved object, so the document is completely gone. No version and no reservation. Checkout is cancelled.
Interpretation 2:
Cancel checkout throws some sort of exception indicating this is not supported since there is no 1.0 version to return to. You must do an explicit delete to make this reservation go away.
Interpretation 3:
Cancel checkout leaves only version 1.0 in a checked in state.
State: Checking in a document after creation in a checked out state.
Interpretation 1:
Version = 1.0
Interpretation 2:
Version = 1.0
Interpretation 3:
Version = 1.1
> Clarify cancelCheckout's proper behavior when doc was created in a checked out state.
> -------------------------------------------------------------------------------------
>
> Key: CMIS-657
> URL: http://tools.oasis-open.org/issues/browse/CMIS-657
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Improvement
> Components: Domain Model
> Affects Versions: Committee Draft 06
> Environment: n/a
> Reporter: Jay Brown
> Assignee: Ethan Gur-esh
> Priority: Minor
>
> Spec says
> cancelCheckOut
> 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.
> We should be specific that if that is this command immediately follows the creation of a document in a checked-out state, this may effectively translate into deleting the doc's entire version series. (depending on the repository)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]