Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Date: Fri, 27 Apr 2012 18:42:48 +0000 (UTC)
From: "Chris Hubick (JIRA)" <jira@apache.org>
To: dev@chemistry.apache.org
Message-ID: 
 <2038315439.3873.1335552168769.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (CMIS-529) Allow simultaneous/atomic update of
 both document properties+content without PWC requirement.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Chris Hubick created CMIS-529:
---------------------------------

             Summary: Allow simultaneous/atomic update of both document properties+content without PWC requirement.
                 Key: CMIS-529
                 URL: https://issues.apache.org/jira/browse/CMIS-529
             Project: Chemistry
          Issue Type: Wish
          Components: opencmis-client
    Affects Versions: OpenCMIS 0.7.0
            Reporter: Chris Hubick
            Priority: Minor


There exists a method Document.checkIn(boolean major, Map<String, ?> properties, ContentStream contentStream, String checkinComment); which is used to simultaneously update *both* the properties and content for the private working copy. Very handy.

However, if one is not modifying a private working copy, then they must perform *two* separate method calls: CmisObject.updateProperties(Map<String, ?> properties, boolean refresh); and Document.setContentStream(ContentStream contentStream, boolean overwrite, boolean refresh);

If a CMS implementation performs automatic version incrementing upon modifications, this will then result in *two* version increments, instead of only one when using a private working copy.  That is less than ideal.

It would be nice if the CMIS protocol had an atomic operation for this, and if anyone from the Chemistry project is in contact with the CMIS working group, it would make a nice feature for CMIS 1.1 :)  (I can't file this enhancement request in the OASIS JIRA, as it isn't really public)

With the hope that such a protocol feature might be added in the future, or even without such support, it could still be a nice feature for the OpenCMIS client API to provide programmers an easy way to combine those two method calls into one, perhaps by adding a method like:

ObjectId Document.update(Map<String, ?> properties, ContentStream contentStream, boolean overwrite, boolean refresh);

Thanks.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira