Skip to main content
Jump to: navigation, search


Revision as of 04:13, 21 October 2007 by (Talk | contribs) (Views)



CDOObjects represent the object instances of the models that your application deals with. Internally each such object is managed by a singleton CDOStateMachine. The state machine accurately transits objects and trees of objects through the states TRANSIENT, NEW, CLEAN, DIRTY, PROXY and CONFLICT. When a CDOObject is in one of the persistent states NEW, CLEAN or DIRTY the state machine associates a CDORevision that carries the current values of the modeled structural features. All revisions created or used in a CDOSession are shared by the CDORevisionMnager of that session. CDOObjects are only known to the CDO client. Only revisions are subject to (network) transfers between client and server.




A CDOObject is basically an EObject with a handful of additional read-only features as the following java code shows:

public interface CDOObject extends EObject
  public CDOClass    cdoClass();
  public CDOID       cdoID();
  public CDOState    cdoState();
  public CDOView     cdoView();
  public CDOResource cdoResource();
  public CDORevision cdoRevision();

The method names differ from the regular Java getter notation to make it less likely that name collisions with your model name space occur. To understand the details about the return types you should browse the JavaDoc.


While a user application always deals with EObjects the internal CDOStateMachine interacts with InternalCDOObjects. Depending on how the EObjects relate to the InternalCDOObjects there are a handful of different categories of CDOObjects, that is, implementations of InternalCDOObject. The following type hierarchy shows an example with the shipped test model installed:


The main categories are:

  • Native objects extend CDOObjectImpl and fall into three sub categories:
    • Generated native objects directly extend CDOObjectImpl and result from slightly modified GenModels
    • Dynamic native objects are of class DynamicCDOObjectImpl and result from dynamic models added to a session's package registry
    • Resources are of class CDOResourceImpl (which also implements CDOObject and thus EObject!)
  • Legacy objects extend EObjectImpl and fall into two sub categories to interface the CDOStateMachine:
    • Unwoven legacy objects interface the state machine via an EMF adapter of class CDOAdapterImpl
    • Woven legacy objects interface the state machine via an AspectJ inter type declaration of class CDOCallbackImpl
  • Meta objects are the EModelElements contained in a session's package registry. Although their state is immutable they interface the state machine via CDOMetaImpl instances so that they can be referenced from ordinary objects.

From a CDO perspective native objects are the most efficient and full featured ones. They are the only category that combine the user application contract and the CDO state machine contract in a single object instance. Whenever possible you should generate your models to produce subclasses of CDOObjectImpl! The following table compares some important characteristics of the different object categories:

Model Type Native Legacy Meta
Dynamic Generated Unwoven Woven
Ecore Unaffected N/A
Genmodel N/A Slightly modified Unaffected
Instance Interface CDOObject EObject EModelObject
State Machine Interface CDOAdapter CDOCallback CDOMeta
Location of
Internal Values
class DynamicCDOObject Java Byte Code
store CDOObject N/A
view CDOAdapter CDOCallback CDOMeta
id CDOSession
state N/A
Location of
Model Values
per CDOState
NEW CDORevision EObject
CLEAN EModelObject

Client Infra Structure

CDOObjects do not just appear out of the dark. To create, load or access them you need, as usual in EMF, an instance of a Resource, here a CDOResource. The following diagram illustrates the CDO client infra structure concepts and their relation to CDOObjects:



A CDOSession is your connection to a single repository on a CDO server. Before you can do anything with CDO you need to open a session.


There are two ways to obtain a session:

  • If you already have an instance of a Net4j IConnector, which represents the physical connection to the server, at hand you can use the CDOUtil class:
IConnector connector = ...;
CDOSession session = CDOUtil.openSession(connector, "repo1");
  • You can also use a Net4j IManagedContainer, for example an extension point based IPluginContainer. The advantage of this approach is that you can leave all the wiring and configuration of the various components to the container which uses factories and element processors that you can contribute centrally via extension points:
CDOSession session = CDOSessionFactory.get(IPluginContainer.INSTANCE, "tcp://");


A CDOView is a partial, yet consistent view onto a model repository. It represents the parts of the overall object graph currently viewed by the client.


Views, in contrast to sessions, are considered light weight entities in CDO, such that you can open and close them as often as you want. There are (nearly) no server side resources associated with a client side view. A CDOView can be seen of as the mediator between an EMF ResourceSet and the loaded objects' state which is managed by the CDORevisionManager of the CDOSession.

public interface CDOView extends INotifier
  public static final long UNSPECIFIED_DATE = CDORevision.UNSPECIFIED_DATE;
  public static final int NO_PRELOAD = 1;

  public enum Type { TRANSACTION, READONLY, AUDIT }

  public int getViewID();
  public Type getViewType();
  public CDOSession getSession();
  public ResourceSet getResourceSet();
  public boolean isDirty();
  public void close();

  public boolean isEnableInvalidationNotifications();
  public void setEnableInvalidationNotifications(boolean on);

  public int getLoadRevisionCollectionChunkSize();
  public void setLoadRevisionCollectionChunkSize(int loadRevisionCollectionChunkSize);

  public CDOResource getResource(String path);
  public CDOObject getObject(CDOID id);
  public CDORevision getRevision(CDOID id);
  public boolean isObjectRegistered(CDOID id);


Instances of CDOTransaction are the only views that permit read-write access to the contained resources and objects. All changes are recorded by a transaction until the application decides to either commit or roll back the transaction.

CDOSession session = ...;
CDOTransaction transaction = session.openTransaction();
CDOResource resource = transaction.createResource("/path/to/resource");

You can also use a CDOTransaction with an existing EMF ResourceSet:

ResourceSet resourceSet = editingDomain.getResourceSet();
CDOTransaction transaction = session.openTransaction(resourceSet);

Read-Only Views

Instances of CDOView are floating views that permit read-only access to the contained resources and objects. They always show the latest changes of the repository but inhibit changes themselves.

CDOSession session = ...;
CDOView view = session.openView();
CDOResource resource = view.getResource("/path/to/resource");

You can also use a CDOView with an existing EMF ResourceSet:

ResourceSet resourceSet = editingDomain.getResourceSet();
CDOView view = session.openView(resourceSet);

Audit Views

Instances of CDOAudit are views that allow the application to view historical state of the repository. They always show a consistent object graph at a particular point in time back in the past. To keep these object graphs consistent audit views only permit read-only access to the contained resources and objects.

CDOSession session = ...;
CDOView audit = session.openAudit(new Date("2007-10-02 10:33").getTime());
CDOResource resource = audit.getResource("/path/to/resource");

You can also use a CDOAudit with an existing EMF ResourceSet:

ResourceSet resourceSet = editingDomain.getResourceSet();
CDOView audit = session.openAudit(resourceSet, timeStamp);



Wikis: CDO | Net4j | EMF | Eclipse

Back to the top