[OASIS Issue Tracker] (CMIS-774) AtomPub version of setContentStream service should return objectId

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

     [ https://issues.oasis-open.org/browse/CMIS-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Monks updated CMIS-774:
-----------------------------

    Proposal: To support efficient client implementations, the return value exceptions in the AtomPub binding (described in section 3.1.9) should be removed, and the domain model definition of these services (described in section 2.2.4) mandated instead.  (was: To support efficient client implementations, this exception in the AtomPub binding should be removed, and the domain model definition of this behaviour mandated instead.)

> AtomPub version of setContentStream service should return objectId
> ------------------------------------------------------------------
>
>                 Key: CMIS-774
>                 URL: https://issues.oasis-open.org/browse/CMIS-774
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: REST/AtomPub Binding
>    Affects Versions: V1.1 Errata
>            Reporter: Peter Monks
>
> Section 3.1.9 of the CMIS 1.1 specification states that the AtomPub version of the setContentStream service doesn't return the cmis:objectId of the new version of the document (note: this is an exception to the domain model, section 2.2.4.18.2).  This means that there is no efficient* way for a client application that uses this call to retrieve the new cmis:objectId value in a spec-compliant manner.
> * where "efficient" means "without further round trips to the CMIS server"



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)