[CMIS-720] TCK ChangeTokenTest doesn't work well about setContentStream because of an CmisVersioningException

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: OpenCMIS 0.10.0
• Fix Version/s: OpenCMIS 0.12.0
• Component/s: opencmis-tck

Environment

Workbench version: "Version: 1.0.0-SNAPSHOT / Revision: 1519696 / Build: 2013-09-03T16:33:20+0200".

• Assignee: Florian Müller
• Reporter: linzhixing
• Created: 12/Sep/13 16:37
• Updated: 13/Aug/14 22:51
• Resolved: 16/Sep/13 08:41

Description

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.