CDO Model Repository Documentation

CDO is both a development-time model repository and a run-time persistence framework; being highly optimized it supports object graphs of arbitrary size.

CDO offers transactions with save points, explicit locking, change notification, remote queries, temporality, branching, merging, offline and fail-over modes. The storage back-end is pluggable and migrations between direct JDBC, Hibernate, Objectivity/DB, MongoDB or DB4O are seamless for CDO applications.

Package
Description
Client concepts like CDOObject and CDOState.
Client side of the protocol to administer CDO repositories remotely.
Common concepts that are differently extended in clients and servers.
Common concepts for the protocol to administer CDO repositories remotely.
Common concepts for dealing with branches.
Common concepts for dealing with commits and change sets.
Some useful commit info handler implementations.
Common concepts for dealing with object and revision IDs.
Common concepts for dealing with large binary objects and large character objects.
Common concepts for dealing with durable locks and views.
Common concepts for dealing with models and types.
Common concepts for dealing with protocols and CDO-specific I/O.
Common concepts for dealing with revisions and revision lists.
Common concepts for dealing with revision deltas and feature deltas.
Common concepts for dealing with permissions and protectable entities.
Common utility classes, some common interfaces and exceptions.
Client concepts for integrating EMF Compare with CDO.
Useful base classes that can be referenced from custom EMF generator models.
The generated EMF API of the CDO repository file system.
The generated EMF implementation of the CDO repository file system.
The generated EMF edit support of the CDO repository file system.
The generated EMF utilities of the CDO repository file system.
The generated EMF API of the CDO system data types and native annotations.
The generated EMF implementation of the CDO system data types and native annotations.
The generated EMF edit support of the CDO system data types and native annotations.
Provides a base class for supporting the specialization of AnnotationItemProvider and StringToStringMapEntryItemProvider.
The generated EMF utilities of the CDO system data types and native annotations.
Base interfaces and a utility class for repositories and checkouts.
Interfaces for working with checkouts.
Interfaces for working with repositories.
The generated EMF API of the CDO expressions model.
The generated EMF implementation of the CDO expressions model.
The generated EMF edit support of the CDO expressions model.
The generated EMF utilities of the CDO expressions model.
The generated EMF API of the CDO Lifecycle Management model.
The generated EMF API of the CDO Lifecycle Management Assembly model.
The generated EMF implementation of the CDO Lifecycle Management Assembly model.
The generated EMF edit support of the CDO Lifecycle Management Assembly model.
The generated EMF utilities of the CDO Lifecycle Management Assembly model.
Client concepts for dealing with CDO Lifecycle Management systems and assemblies.
The generated EMF implementation of the CDO Lifecycle Management model.
The generated EMF API of the CDO Lifecycle Management Modules model.
The generated EMF implementation of the CDO Lifecycle Management Modules model.
The generated EMF edit support of the CDO Lifecycle Management Modules model.
The generated EMF utilities of the CDO Lifecycle Management Modules model.
The generated EMF edit support of the CDO Lifecycle Management model.
 
The generated EMF API of the CDO Lifecycle Management Security model.
The generated EMF implementation of the CDO Lifecycle Management Security model.
The generated EMF edit support of the CDO Lifecycle Management Security model.
The generated EMF utilities of the CDO Lifecycle Management Security model.
Server integration of the CDO Lifecycle Management.
The generated EMF utilities of the CDO Lifecycle Management model.
Client concepts for dealing with Net4j-based sessions to remote repositories.
The generated EMF API of the CDO security model.
The generated EMF implementation of the CDO security model.
The generated EMF edit support of the CDO security model.
Concepts and default implementations for the CDO security user interface.
The generated EMF utilities of the CDO security model.
Server concepts for dealing with repositories and stores.
Server side of the protocol to administer CDO repositories remotely.
Server concepts for dealing with DB stores and accessors.
Server concepts for dealing with mapping strategies and mappings for classes, lists and types.
Server concepts for dealing with Net4j-based repositories and fail-over infrastructure.
Server concepts for dealing with DB stores and accessors.
Server concepts for dealing with in-memory stores.
Server concepts for dealing with MongoDB stores and accessors.
Server concepts for dealing with Net4j-based repositories and fail-over infrastructure.
Server implementation of a generic OCL query handler.
Server integration of the Security model.
Server provider interfaces (SPI) for the protocol to administer CDO repositories remotely.
Server provider interfaces (SPI) for the server integration of the Security model.
Client concepts for dealing with sessions to CDO repositories.
Client concepts for the communication and collaboration with other sessions.
Common service provider interfaces and useful base implementations.
Common concepts for dealing with protocols and CDO administration-specific I/O.
Common service provider interfaces and useful base implementations for dealing with branches.
Common service provider interfaces and useful base implementations for dealing with commits and change sets.
Common service provider interfaces and useful base implementations for dealing with object and revision IDs.
Common service provider interfaces and useful base implementations for dealing with object locks.
Common service provider interfaces and useful base implementations for dealing with models and types
Common base implementations for dealing with I/O of CDO data structures.
Common service provider interfaces and useful base implementations for dealing with revisions and deltas.
Common utility classes.
Server service provider interfaces and useful base implementations.
Service provider concepts for dealing with transfers of resources between systems.
Server provider interfaces (SPI) for CDO workspaces.
Client concepts for dealing with transactions, distributed transactions and their save points.
Client concepts for dealing with transfers of resources between systems.
Client concepts for dealing with transfers of resources between systems.
Service provider concepts for dealing with transfers of resources between systems.
Client concepts for dealing with transfers of resources between systems.
Reusable implementatins of common JFace concepts for dealing with transfers of resources between systems.
Reusable controls for dealing with transfers of resources between systems.
Reusable UI components specific to the CDO Model Repository.
Classes that help to open EMF Compare user interfaces on CDO models.
A library with reusable widgets.
Client utility classes, some common interfaces and exceptions.
Client concepts for dealing with views, view sets, queries, CDO objects and EMF resource sets.
Concepts to checkout, open and further operate CDO workspaces.
Exposes CDOObjectImpl for extension in generated EMF models.
Client service provider interfaces and useful base implementations.