Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Date: Thu, 3 Nov 2011 01:49:32 +0000 (UTC)
From: =?utf-8?Q?Florian_M=C3=BCller_=28Resolved=29_=28JIRA=29?=
 <jira@apache.org>
To: dev@chemistry.apache.org
Message-ID: 
 <1285649600.53985.1320284972298.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <425246097.24910.1319725832126.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CMIS-458) SetAndDeleteContentTest does not
 properly support repositories that only allow to update the current version
 of a document
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Florian M=C3=BCller resolved CMIS-458.
---------------------------------

    Resolution: Fixed
   =20
> 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=C3=BCller
>             Fix For: OpenCMIS 0.6.0
>
>
> The specification states that a repository may create a new document vers=
ion when a contentStream is deleted.
> SetAndDeleteContentTest does not handle this scenario, therefore if the r=
epository does create a new version when a contentStream is deleted and doe=
s 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 do=
cument 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 administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira