chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Potts (Commented) (JIRA)" <>
Subject [jira] [Commented] (CMIS-399) Empty custom CMIS properties on custom document types result in faulty XML
Date Thu, 01 Dec 2011 00:31:41 GMT


Jeff Potts commented on CMIS-399:

What version of Alfresco are you using for this? I cannot recreate the problem using either
cmislib 0.4.1 or cmislib head against Alfresco 4.0b Community.
> Empty custom CMIS properties on custom document types result in faulty XML
> --------------------------------------------------------------------------
>                 Key: CMIS-399
>                 URL:
>             Project: Chemistry
>          Issue Type: Bug
>          Components: python-cmislib
>    Affects Versions: OpenCMIS 0.4.0
>         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
>            Reporter: Bjarki Gudlaugsson
>            Assignee: Jeff Potts
>              Labels: cmis, property, python, xml
> 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
> <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" />

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message