[ 
https://issues.apache.org/jira/browse/CMIS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263867#comment-13263867
 ] 

Chris Hubick commented on CMIS-528:
-----------------------------------

It would appear that this issue also exists in other methods, such as 
DocumentImpl.setContentStream(ContentStream contentStream, boolean overwrite, 
boolean refresh).
                
> AbstractCmisObject.updateProperties newObjectId handing when refresh=true
> -------------------------------------------------------------------------
>
>                 Key: CMIS-528
>                 URL: https://issues.apache.org/jira/browse/CMIS-528
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-client
>    Affects Versions: OpenCMIS 0.7.0
>            Reporter: Chris Hubick
>            Priority: Minor
>
> There is a method: public ObjectId 
> AbstractCmisObject.updateProperties(Map<String, ?> properties, boolean 
> refresh) for which the Javadoc (on CmisObject) says:
> @param refresh indicates if the object should be refresh after the update
> @return the object id of the updated object (a repository might have created 
> a new object)
> One would logically expect then, if you supply refresh=true, that when the 
> update operation upon this object has completed, that it will then contain 
> those property values just set.  This would imply that if a new object id 
> *is* returned for the object containing those updated values, that the 
> AbstractCmisObject object will be updated to point to that new id?
> That does not appear to be the case within the method implementation, which 
> appears to refresh the object with the property values from the *old* object 
> id.
> Even if it's intended that the AbstractCmisObject *not* be pointed to the 
> updated id, it would then seem prudent to check if a new id was issued, and 
> skip the refresh call in that case?
> 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

        

Reply via email to