You are looking at documentation for an older release. Not what you want? See the current release documentation.
CMIS uses specified JCR namespaces cmis and xcmis internally.
The following nodetypes are supported to expose the content of drives:
nt:file nodetype for representation of cmis:document.
nt:folder for representation of cmis:folder.
Since the CMIS specification does not allow having more root types except ones described above
(cmis:document and cmis:folder), the nt:file and nt:folder
nodetypes are mapped to CMIS types.
There are two more nodetypes which are used: cmis:policy and cmis:relationship which represent the corresponding CMIS types
(see Services description for details).
Additionally, nodetypes used in Content are mapped as follows:
nt:unstructured + extensions as cmis:folder.
exo:taxonomy + extensions as cmis:folder.
In other words, only nodetypes extending nt:file, nt:folder,
nt:unstructured and exo:taxonomy
will be exposed correctly via CMIS API.
The Content nodetype named exo:article is not supported by eXo CMIS
due to uncompliant structure to nt:file.