Re: [cmis-comment] spec V1.1: 2.2.4.17 deleteTree

[David Choy <david.choy500@gmail.com>]

Thank your for your well-intended suggestion.

DeleteTree is a rather drastic operation. Its precise behavior varies from one repository to another depending on the implementation (such as tree-traversal algorithm, transactional/recovery logic, performance considerations, etc). It is therefore by design that each CMIS repository is allowed to set its own conditions for deleteTree to succeed/fail that are appropriate for that specific repository. Most vendors would do their best given the constraint of their underlying implementation. Prescribing precise behavior for deleteTree beyond the most obvious, even though seemingly logical on the surface, could create a compliance challenge for many vendors.

On Fri, Oct 5, 2012 at 2:08 PM, me <dave8435@gmail.com> wrote:

Suggestion:   State the behavior of unfileObjects=unfile when capabilityUnfiling=false.

For example, should deleteTree succeed if all documents are multi-filed or there are no documents?   Should an exception be thrown and no objects deleted when there is at least one single-filed document?