Chapter 1. Introducing CMIS
Figure 1.1. Before SQL standardization, developers wrote applications against specific databases.
Figure 1.2. CMIS standardizes the way applications work with rich content repositories in much the same way SQL did for relational databases.
Figure 1.3. Most companies store content in multiple ECM repositories. Content-centric applications either have to use multiple disparate APIs, or take advantage of CMIS’s ability to use each repository in a standard way.
Figure 1.4. Your local CMIS development setup includes two components: the CMIS Workbench and the OpenCMIS InMemory Repository. This is all you’ll need for the examples in part 1 of this book.
Figure 1.5. Apache Chemistry OpenCMIS InMemory Repository welcome page
Figure 1.6. An empty CMIS Workbench login dialog box
Figure 1.7. To connect to the repository, you must select a binding and specify the service URL.
Figure 1.8. Root folder of the OpenCMIS InMemory Repository
Figure 1.9. Groovy console after running code to retrieve the CMIS server name
Chapter 2. Exploring the CMIS domain model
Figure 2.1. CMIS high-level object types (all of which we’ll discuss in this chapter)
Figure 2.2. The CMIS service is an interface to all of the CMIS repositories and the objects that they contain.
Figure 2.3. Three bindings expose the same functionality for clients with different needs.
Figure 2.4. The repository is where all of the objects are stored.
Figure 2.5. Repository Info button in the Workbench