[OASIS Issue Tracker] Commented: (CMIS-126) Should"deleteAllVersions" have "continueOnFailure" semantics like "DeleteTree"does?

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Florent Guillaume commented on CMIS-126:
----------------------------------------

DeleteTree is allowed to do partial deletes presumably because a transactional behavior would be hard to maintain for some repositories on big trees.

But DeleteAllVersions can probably more easily do this in an all-or-nothing manner (including the PWC) so I'm for saying that it MUST delete nothing if there's an error.


> Should "deleteAllVersions" have "continueOnFailure" semantics like "DeleteTree" does?
> -------------------------------------------------------------------------------------
>
>                 Key: CMIS-126
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-126
>             Project: OASIS Content Management Interoperability Services TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.52
>            Reporter: Ethan Gur-esh
>            Assignee: Ethan Gur-esh
>
> Currently, there are 2 CMIS methods that attempt to delete >1 object at a time.
> - DeleteTree: Deletes all objects in a folder tree.
> - DeleteAllVersions: Deletes all documents in a folder series.
> DeleteTree includes semantics/parameters for how the Repository should behave if for any reason it CANNOT delete one of the objects in the Folder Tree.
> Should we add the same semantics for DeleteAllVersions?

-- 
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