[
https://issues.apache.org/jira/browse/CMIS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738775#comment-13738775
]
Jeff Potts commented on CMIS-703:
---------------------------------
I am happy to do that, but what *should* the client be doing? My thought is
that if the CDATA isn't in the spec then the client should not be including it.
> cmislib fails to query InMemory 0.9 due to CDATA
> ------------------------------------------------
>
> Key: CMIS-703
> URL: https://issues.apache.org/jira/browse/CMIS-703
> Project: Chemistry
> Issue Type: Bug
> Components: python-cmislib
> Affects Versions: cmislib 0.5.1
> Reporter: Jeff Potts
> Assignee: Jeff Potts
>
> cmislib 0.5.1 cannot successfully query OpenCMIS InMemory repository 0.9
> because the query that gets posted wraps the cmis:statement in a CDATA. This
> used to work fine but something must have changed on the server side.
> Early query examples must have shown a CDATA being used. But it is definitely
> not part of the spec now so it should probably get taken out of the client.
> This is how cmislib 0.5.1 formats the query that gets posted. This will not
> work against inmemory 0.9:
> <?xml version="1.0" encoding="utf-8"?>
> <query xmlns="http://docs.oasis-open.org/ns/cmis/core/200908/";>
> <statement><![CDATA[select * from cmis:document where cmis:name like
> 'test%.txt']]></statement>
> </query>
> This is what apparently needs to get posted to InMemory 0.9:
> <?xml version="1.0" encoding="utf-8"?>
> <query xmlns="http://docs.oasis-open.org/ns/cmis/core/200908/";>
> <statement>select * from cmis:document where cmis:name like
> 'test%.txt'</statement>
> </query>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
