[jira] [Commented] (CMIS-675) OpenCMIS server's checkOut does not return PWC but the checked out document atom entry

["Florian Müller (JIRA)" <ji...@apache.org>]

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

Florian Müller commented on CMIS-675:
-------------------------------------

Not sure I understand the problem. The parameter {{objectId}} of the {{checkout()}} method is a {{Holder}} object. The server implementation must set the id of the PWC before it leaves the method. If this id is correct, OpenCMIS returns the correct Atom entry.
                
> OpenCMIS server's checkOut does not return PWC but the checked out document atom entry
> --------------------------------------------------------------------------------------
>
>                 Key: CMIS-675
>                 URL: https://issues.apache.org/jira/browse/CMIS-675
>             Project: Chemistry
>          Issue Type: Bug
>    Affects Versions: OpenCMIS 0.9.0 beta 1
>            Reporter: linzhixing
>
> On the sever side via Atompub, VersioningService#checkOut creates objectInfo after checking out a document and cretring PWC(Line:66). But this objectInfo seems to be remain as the checked out document, not PWC. Alhough the objectInfo has "workingCopyOriginalId" property and I confirm that it has the correct PWC id value, objectInfo is created without it as follows:
> service.getObjectInfo(repositoryId, checkOutId.getValue())
> where checkOutId still indicates the document which was checked out.
> The client receives only "via" atom link as PWC id.
> According to CMIS spec, 2.2.7.1.2, output objectId must be PWC id, and on the sever side server.impl.atompub.VersioningService#checkOut is a void type method, so I can't create objectInfo of PWC by myself.
> How should I do? 
> As a consequence, I got errors in Versioning Smoke Test's checkOut test in TCK. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira