This week's book giveaway is in the Reactive Progamming forum. We're giving away four copies of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams and have Adam Davis on-line! See this thread for details.
When first time I saw IBM implemented CMIS for IBM content repository, I was a little confused by its name. Even if I have been working in CMS for many years, but never got change to work on CMIS so my knowledge is so limited that I want to learn from you expert guys, especially you are writing a BOOK about it. I am very excited to see and read this book. Do I understand it correctly? I hope so.
So my first question about CMIS is this: is CMIS a industrial standard to access all types of repository including sharepoint, filenet, alfresco etc?
My second question is: is CMIS based on REST webservices?
I do not know on third and I am sure I will have a lot to ask later on.
Yes, CMIS is an industry standard that let's you work with repositories like Alfresco, SharePoint, FileNet, and many others.
Regarding REST, the CMIS specification requires that CMIS-compliant servers support both a RESTful AtomPub binding and a SOAP-based Web Services binding. If you are writing an application that consumes CMIS you can choose the binding that is appropriate for your particular needs. In CMIS 1.1, a third binding is added--it's JSON-based and is called the browser binding.
You can use the bindings directly if you want. But most people get tired of parsing the responses themselves. That's one of the nice things about using a client library. For Java developers, the most popular client library for CMIS is OpenCMIS, which is part of Apache Chemistry. But there are client libraries available for many other languages. In addition to Java, Apache Chemistry includes client libraries for Python, PHP, and C#. Client libraries for other languages can be found around the net.
posted 7 years ago
Thank you for your reply, Jeff.
This is a very exciting book for me and I want to learn more once it is published.
There’s no place like 127.0.0.1. But I'll always remember this tiny ad: