[
https://issues.apache.org/jira/browse/CMIS-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053762#comment-13053762
]
Florian Müller commented on CMIS-386:
-------------------------------------
Another look at the CMIS schema revealed this:
{code:xml}
<xs:element name="parentId" type="xs:string" minOccurs="0" maxOccurs="1">
<xs:annotation>
<xs:documentation>
This is the id for the parent type definition. If this is a base type,
this is not present.
</xs:documentation>
</xs:annotation>
</xs:element>
{code}
I'm not going to revert the code changes to keep it interoperable, but the
intention of the spec is that this tag should be absent for base types rather
than empty.
> 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
