You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "Cedric Moitrier (Reopened) (JIRA)" <ji...@apache.org> on 2011/11/02 15:01:32 UTC

[jira] [Reopened] (CMIS-458) SetAndDeleteContentTest does not properly support repositories that only allow to update the current version of a document

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

Cedric Moitrier reopened CMIS-458:
----------------------------------


Still not working because setContentStream is not called on the latest version of the document.

In my scenario, the latest version would be the one whose identifier is returned by deleteContentStream, but the test does call setContentStream on the original document.
                
> SetAndDeleteContentTest does not properly support repositories that only allow to update the current version of a document
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CMIS-458
>                 URL: https://issues.apache.org/jira/browse/CMIS-458
>             Project: Chemistry
>          Issue Type: Bug
>          Components: tck
>    Affects Versions: OpenCMIS 0.5.0
>            Reporter: Cedric Moitrier
>            Assignee: Florian Müller
>             Fix For: OpenCMIS 0.6.0
>
>
> The specification states that a repository may create a new document version when a contentStream is deleted.
> SetAndDeleteContentTest does not handle this scenario, therefore if the repository does create a new version when a contentStream is deleted and does not support the update of a document that is not the current version, the test will fail (because setContentStream() will be called on a previous document version, the one prior to the deleteContentStream call).

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