[CMIS-737] TCK issue: adding charset in content stream mime type

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Invalid
• Affects Version/s: OpenCMIS 0.10.0
• Component/s: opencmis-tck
• Assignee: Unassigned
• Reporter: James Li
• Created: 27/Nov/13 08:52
• Updated: 09/Dec/13 06:06
• Resolved: 09/Dec/13 06:06

Description

Running TCK test against my repository, it got the following error:
Copy Test (ATOMPUB) (30773 ms)Creates two folders and a document and copies the document from one folder to the other. If the AtomPub binding is used, this test is skipped.
WARNING: New document object spec compliance (AbstractSessionTest.java:444) [stacktrace]
WARNING: Content MIME types don't match! (AbstractSessionTest.java:1352) [stacktrace]
INFO: expected: text/plain / actual: text/plain;charset=utf-8
WARNING: Copied document check. Id: + copytestdoc.txt (CopyTest.java:76) [stacktrace]
WARNING: Content MIME types don't match! (AbstractSessionTest.java:1352) [stacktrace]
INFO: expected: text/plain;charset=utf-8 / actual: text/plain;charset=utf-8;charset=utf-8
FAILURE: Content streams don't match! (CopyTest.java:80) [stacktrace]
FAILURE: MIME types don't match! (AbstractSessionTest.java:3192) [stacktrace]
org.apache.chemistry.opencmis.tck.impl.AbstractSessionTest.assertEquals(AbstractSessionTest.java:3192)
org.apache.chemistry.opencmis.tck.tests.crud.CopyTest.run(CopyTest.java:80)
org.apache.chemistry.opencmis.tck.impl.AbstractSessionTest.run(AbstractSessionTest.java:160)
org.apache.chemistry.opencmis.tck.impl.AbstractCmisTestGroup.run(AbstractCmisTestGroup.java:109)
INFO: expected: text/plain;charset=utf-8 / actual: text/plain;charset=utf-8;charset=utf-8

Actually, when the first doc is created, the mime type returned is
<cmis:propertyString queryName="cmis:contentStreamMimeType" displayName="Mime Type" localName="MimeType" propertyDefinitionId="cmis:contentStreamMimeType">
<cmis:value>text/plain</cmis:value>
</cmis:propertyString>

when the test code line is executed:
Document doc2 = doc1.copy(folder2, null, versioningState, null, null, null, SELECT_ALL_NO_CACHE_OC); The value in POST document is :
<cmis:propertyString queryName="cmis:contentStreamMimeType" displayName="Mime Type" localName="MimeType" propertyDefinitionId="cmis:contentStreamMimeType">
<cmis:value>text/plain;charset=utf-8</cmis:value>
</cmis:propertyString>

The TCK result is expected: text/plain;charset=utf-8 / actual: text/plain;charset=utf-8;charset=utf-8

I don't know when the charset=utf-8 is added to mime type, is this a TCK issue?