[
https://issues.apache.org/jira/browse/CMIS-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053954#comment-13053954
]
jay brown commented on CMIS-386:
--------------------------------
Good catch. Though the spec could still be more specific here. For example
if the sentence said either
If this is a base type, this value is not present.
or
If this is a base type, this element is not present.
But since it does not, then 'this' would be interpreted to mean this
xs:element.
We will look into changing our implementation eventually then, but we need to
make sure this does not break any of our internal clients. :)
I agree that the client should continue to permit both interpretations for
maximum compatibility.
> OpenCMIS TCK should consider empty cmis:parentId element as a "not set"
> attribute for base type definition
> ----------------------------------------------------------------------------------------------------------
>
> Key: CMIS-386
> URL: https://issues.apache.org/jira/browse/CMIS-386
> Project: Chemistry
> Issue Type: Bug
> Components: opencmis-tck
> Affects Versions: OpenCMIS 0.3.0
> Reporter: David Sanders
> Assignee: Florian Müller
> Priority: Minor
> Fix For: OpenCMIS 0.4.0
>
>
> The OpenTCK expects a base type's cmis:parentId attribute to be null. An
> empty element should also be accepted assuming that meets the spec's
> definition of "not set". That is, both TypeDefinition.getParentTypeId() ==
> null
> and TypeDefiniton.getParentTypeId().length() == 0 should be accepted.
> OpenCMIS TCK fails with
> FAILURE: Document type spec compliance. (AbstractCmisTest.java:114)
> FAILURE: Base type has parent type! (AbstractSessionTest.java:1357)
> The IBM FileNet CMIS provider returns the following for cmis:document and
> cmis:folder:
> <cmis:parentId></cmis:parentId>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
