This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes Other Open Source Projects and the fly likes CMIS interfaces: why more than one? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » Other Open Source Projects
Bookmark "CMIS interfaces: why more than one?" Watch "CMIS interfaces: why more than one?" New topic
Author

CMIS interfaces: why more than one?

Nikes Shah
Ranch Hand

Joined: Jul 18, 2007
Posts: 133
Hello,

Are there any business use cases which can justify when to use which type of CMIS interface (WebServices, REST etc.)

In other words, why more than one interfaces?

Thanks in advance.

Regards,
Nikesh
Florian Mueller
Author
Greenhorn

Joined: Sep 24, 2012
Posts: 6
Hi Nikesh,

CMIS defines multiple bindings to increase the adoption. When you design a new interface or standard today, you probably would go for a RESTish interface. And that's why there is the CMIS AtomPub binding. But, it is a fact that many companies spent a ton of money a few years ago into a Web Services infrastructure. That includes security services, identity services, auditing services, and so on. The effort to incorporate a REST interface into this environment would be huge. But, if CMIS would only define a Web Services interfaces, most modern systems would not touch it - for technical and ideological reasons.

So CMIS leaves the CMIS client the choice of what fits better into the IT infrastructure. And on top of that, Apache Chemistry hides all those low-level details.
If you, for example, implement against Apache Chemistry OpenCMIS, you implement against a Java interface. Which binding is finally used in the production environment (almost) doesn't matter.


Regards,

Florian
Nikes Shah
Ranch Hand

Joined: Jul 18, 2007
Posts: 133
Thanks Florian

That makes sense.

Considering complexity of WebServices architecture, REST provides simplicity.

-Nikesh
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: CMIS interfaces: why more than one?
 
Similar Threads
Do we use interfaces just for multiple inheritence?
IBM CMIS
Extending interface
CMIS support in popular document repositories
A CMIS question...