[
https://issues.apache.org/jira/browse/CMIS-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047257#comment-13047257
]
Florian Müller commented on CMIS-386:
-------------------------------------
I think I had that this discussion with Jay before. There are different
interpretations of "not-set".
The parent id MUST NOT be set for base types and MUST be set for all other
types.
The XSD says this:
<xs:element name="parentId" type="xs:string" minOccurs="0" maxOccurs="1">
It explicitly defines 'minOccurs="0"' which can only be valid for base types.
My conclusion is that "not-set" means "not existing" and an empty string is
actually a value.
Therefore I'm a bit reluctant to change the TCK. Thoughts?
> 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.4.0
> Reporter: David Sanders
> Priority: Minor
>
> 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
