[#CMIS-118] Methods other than "updateProperties" should include the changeToken as input

OASIS Content Management Interoperability Services (CMIS) TC

Methods other than "updateProperties" should include the changeToken as input

Created: 06/Mar/09 06:57 PM Updated: 11/Jan/10 07:16 PM

Component/s:

Schema

Affects Version/s:

Draft 0.50, Draft 0.60

Fix Version/s:

Draft 0.62

Proposal:	« Hide Add the changeToken input to: - setContentStream - deleteContentStream Note: version 0.6 of Part I already has the changeToken in all the right places. Show » Add the changeToken input to: - setContentStream - deleteContentStream Note: version 0.6 of Part I already has the changeToken in all the right places.
Resolution:	Proposal accepted (on 4/20)

Description

« Hide

Currently, the only method in the domain model that requires a changeToken is the "updateProperties" method.

This is inconsistent. There are other methods that effectively "update" an object, and they should all take a ChangeToken input.

All

Comments

Change History

Sort Order:

[ Permalink | « Hide ]

Al Brown added a comment - 14/Apr/09 12:40 PM

Removed - - moveObject
- deleteObject
- deleteTree
- checkOut
- cancelCheckOut
- checkIn

[ Permalink | « Hide ]

Ethan Gur-esh added a comment - 20/Apr/09 12:53 PM

Will revise proposal as follows:

Add two new repository-level capabilities:
- ChangeTokenRequiredforProperties:
- ChangeTokenRequiredforContentStream

If the property is true for properties/contentstream, then the repository will emit AND require change tokens to be provided on update.

[ Permalink | « Hide ]

Ethan Gur-esh added a comment - 19/May/09 02:02 PM

Resolved a bit too quickly. Still need to add new optional capabilities for "ChangeTokenRequiredforProperties" and "ChangeTokenRequiredForContentStream".

[ Permalink | « Hide ]

Al Brown added a comment - 05/Jan/10 12:37 AM

JIRA Cleanup