5.4.1. Integration with Content

5.4.1.1. JCR namespaces and nodetypes
5.4.1.2. Content drives as CMIS Repositories
5.4.1.3. Content symlinks
5.4.1.4. Modifying Content via CMIS
5.4.1.5. CMIS search

Warning

You are looking at documentation for an older release. Not what you want? See the current release documentation.

The Content system provides CMIS access to its content storage features:

To expose Content drives as CMIS repositories, there is a special extension of CmisRegistry.

Working with CMIS is based on reference documents returned by services. Each CMIS service returns response containing links to other services describing the Document or operations on it. In most cases, a Document will be asked by its ID. Some services accept a Document path.

Note

Notes for use cases: To access the eXo CMIS services from the client side, use the Curl tool. The CMIS AtomPub binding which is based upon the Atom (RFC4287) and Atom Publishing Protocol (RFC5023) will be used.

SOAP binding is not implemented as of eXo Platform 4.0.

Copyright ©. All rights reserved. eXo Platform SAS
blog comments powered byDisqus