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

Florian Müller updated CMIS-720:
--------------------------------

      Component/s: opencmis-tck
    Fix Version/s: OpenCMIS 1.0.0
    
> TCK ChangeTokenTest doesn't work well about setContentStream because of an 
> CmisVersioningException
> --------------------------------------------------------------------------------------------------
>
>                 Key: CMIS-720
>                 URL: https://issues.apache.org/jira/browse/CMIS-720
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-tck
>    Affects Versions: OpenCMIS 0.10.0
>         Environment: Workbench version: "Version: 1.0.0-SNAPSHOT / Revision: 
> 1519696 / Build: 2013-09-03T16:33:20+0200".
>            Reporter: linzhixing
>            Assignee: Florian Müller
>            Priority: Minor
>             Fix For: OpenCMIS 1.0.0
>
>
> ChangeTokenTest#runContentTest executes tests of setContentStream.
> I found LINE132, the second call of setContentStream failed because of a 
> CmisVersioningException error, which is implemented in my CMIS server.
> The test intends to check whether the second call causes correctly an update 
> conflict error, not a versioning error.
> According to the specs 2.2.4.18, setContentStream service 
>     -MAY automatically create new document versions as part of this service 
> operations. Therefore, the objectId output NEED NOT be identical to the 
> objectId input.
>     -MAY throw versioning error if the object is a non-current document 
> version.
> Unfortunately, my server implements both feature, say, in the first call of 
> setContentStream a new document version is created(like version1.1) and the 
> old document(version1.0) changed to be non-current version. And then, in the 
> second call, setContentStream is called for the old document and raise the 
> versioning error.
> So I suppose that any care should be taken for this situation.

--
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

Reply via email to