[CMIS-399] Empty custom CMIS properties on custom document types result in faulty XML

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: OpenCMIS 0.4.0
• Component/s: python-cmislib
• Labels: cmis property python xml

Environment

This behaviour has been replicated on several systems including CentOS 5, Windows 7, Ubuntu 10.04 and Fedora 15.
python version 2.6
cmislib version 0.4.1

• Assignee: Jeffrey Taylor Potts
• Reporter: Bjarki Gudlaugsson
• Created: 12/Jul/11 13:45
• Updated: 06/Dec/11 00:02
• Resolved: 06/Dec/11 00:02

Description

When calling createDocument on CmisFolder and submitting an empty property (e.g. custom:custom_property) for a custom document type (e.g. custom:custom_document_type) the resulting xml looks like this:

<cmis:propertyId propertyDefinitionId="cmis:objectTypeId">
<cmis:value>D:custom:custom_document_type</cmis:value>
</cmis:propertyId>
<cmis:propertyString propertyDefinitionId="custom:custom_property">
<cmis:value></cmis:value>
</cmis:propertyString>

It is invalid and it results in the CMIS server (Alfresco in my case) not setting any of the submitted custom properties. It should look like this (and this is how the Java version does it):

<cmis:propertyId propertyDefinitionId="cmis:objectTypeId">
<cmis:value>D:custom:custom_document_type</cmis:value>
</cmis:propertyId>
<cmis:propertyString propertyDefinitionId="custom:custom_property" />

Issue Links

• is related to: CMIS-481 Cannot set a property to null