OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (CMIS-118) Methods other than"updateProperties" should include the changeToken as input

    [ http://tools.oasis-open.org/issues/browse/CMIS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10240#action_10240 ] 

Ethan Gur-esh commented on CMIS-118:

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. 

> Methods other than "updateProperties" should include the changeToken as input
> -----------------------------------------------------------------------------
>                 Key: CMIS-118
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-118
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Schema
>    Affects Versions: Draft 0.50, Draft 0.6
>            Reporter: Ethan Gur-esh
>            Assignee: Ethan Gur-esh
> 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.

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]