Skip to main content
Jump to: navigation, search

Difference between revisions of "CDO"

(Project Resources)
 
(138 intermediate revisions by 11 users not shown)
Line 1: Line 1:
==Introduction==
+
__NOTOC__<br>
  
CDO is a 3-tiers solution for ''distributed shared models'' and a complete ''model repository''. With CDO you can easily enhance your existing EMF models in such a way that they can be stored and subsequently maintained in a central model repository. While object relational mapping against a JDBC data source on the server side is the shipped default CDO provides for ''pluggable storage adapters'' that allow you to develop and use different mappers (like Hibernate- or OODB-based). On the client side CDO provides a default integration with EMF, the Eclipse Modeling Framework, although other model integrations on top of the ''CDO protocol'' are imaginable as well.
+
{| border="0"
 +
|-
 +
| valign="top" | [[Image:CDOOverview.png]]
 +
| &nbsp;<br>
 +
| &nbsp;<br>
 +
| &nbsp;<br>
 +
| width="500" valign="top" |
 +
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, queries, temporality, branching, merging, offline and fail-over modes, ...
  
[[Image:CDOOverview.png]]
+
The storage back-end is pluggable and migrations between direct JDBC, Hibernate, Objectivity/DB, MongoDB or DB4O are seamless for CDO applications.
  
 +
You may also want to visit our '''[http://www.eclipse.org/cdo homepage]'''.
  
==Features==
+
|}
  
===Model Integration===
+
<br>
* EMF integration on model level (as opposed to the edit level)
+
* Support for generated models (just switch two .genmodel properties)
+
* Support for dynamic models (just load .ecore file and commit to repository)
+
* Support for legacy models (for compiled models without access to .genmodel)
+
* Support for the Ecore meta meta model and descendants
+
  
===CDO User Interface===
+
{| cellspacing="10" border="0"
* Eclipse view for working with CDO sessions, transactions, views and resources
+
|-
* Package Manager dialog per session
+
| valign="top" | '''Documentation'''<br>
* Eclipse editor for working with resources and objects
+
[[CDO Explorer]]<br>
 +
'''[http://wiki.eclipse.org/images/0/07/CDO-Poster.pdf CDO Poster]'''<br>
 +
[[CDO/Client|Client Architecture]]<br>
 +
[[CDO/Server Configuration Reference|Server Configuration]]<br>
 +
[http://www.eclipse.org/cdo CDO Presentations]<br>
 +
[http://live.eclipse.org/node/884 Webinar 2010/04]<br>
  
===CDO Client===
+
| valign="top" | '''Tutorials'''<br>
* Multiple sessions to multiple repositories on multiple servers
+
[[CDO/Preparing EMF Models|Preparing EMF Models for CDO]]<br>
* Multiple transactions per session
+
[[CDO/Using the User Interface|Using the CDO User Interface]]<br>
* Multiple read-only views per session
+
[[CDO/Tweaking Performance|Tweaking CDO Performance]]<br>
* Multiple audit views per session (an audit is a view that shows a consistent, historical version of a repository)
+
'''[[CDO/User Contributed Documentation | User Contributed Documentation]]'''<br>
* Multiple resources per view (a view is always associated with its own EMF ResourceSet)
+
* Inter-resource proxy resolution
+
* Multiple root objects per resource
+
* Object state shared among all views of a session
+
* Object graph internally unconnected (unused parts of the graph can easily be reclaimed by the garbage collector)
+
* Only new and modified objects committed in a transaction
+
* Transactions can span multiple resources
+
* Demand loading of objects (resources are populated as they are navigated)
+
* Partial loading of collections (chunk size can be configured per session)
+
* Adaptable pre-fetching of objects (different intelligent usage analyzers are available)
+
* Asynchronous object invalidation (optional)
+
* Clean API to work with sessions, views, transactions and objects
+
* CDOResources are EObjects as well
+
* Objects carry meta information like id, state, version and life span
+
* Support for OSGi environments (headless, Eclipse RCP, ...)
+
* Support for standalone applications (non-OSGi)
+
  
===CDO Protocol===
+
| valign="top" | '''Resources'''<br>
* [[Net4j]] based binary application protocol
+
'''[[FAQ for CDO and Net4j|FAQ]]'''<br>
* Pluggable transport layer (shipped with NIO socket transport and JVM embedded transport)
+
[http://www.eclipse.org/cdo/downloads/ Downloads and Updates]<br>
* Pluggable fail over support
+
[[CDO Source Installation|Source Installation]]<br>
* Pluggable authentication (shipped with challenge/response negotiation)
+
[[CDO Development Guidelines|Development Guidelines]]<br>
* Multiple acceptors per server
+
[[CDO/Release Engineering|Release Engineering]]<br>
  
===CDO Server===
+
| valign="top" | '''Features'''<br>
* Pluggable storage adapters
+
[[#Model_Integration_Features|Model Integration]]<br>
* Multiple repositories per server
+
[[#User_Interface_Features|User Interface]]<br>
* Multiple models (packages) per repository
+
[[#Client_Side_Features|Client Side]]<br>
* Multiple resources (instance documents) per repository
+
[[#Network_Protocol_Features|Network Protocol]]<br>
* Expressive XML configuration file
+
[[#Server_Side_Features|Server Side]]<br>
* Configurable storage adapter per repository (see below)
+
[[CDO/DB Store|DB Store]]<br>
* Configurable caching per repository
+
[[CDO/MongoDB Store|MongoDB Store]]<br>
* Clean API to work with repositories, sessions, views, transactions and revisions
+
[[CDO/Hibernate Store|Hibernate Store]]: [[CDO/Hibernate_Store/Quick_Start|Quick Start]], [[CDO/Hibernate_Store/Tutorial|Tutorial]]<br>
* Support for OSGi environments (usually headless)
+
[[CDO/Objectivity Store|Objectivity Store]]<br>
* Support for standalone applications (non-OSGi)
+
[[/New And Noteworthy for CDO 2.0/]]<br>
 +
[http://www.eclipse.org/cdo/documentation/relnotes_30/relnotes-3.0.html New And Noteworthy for CDO 3.0]<br>
 +
'''[https://bugs.eclipse.org/bugs/buglist.cgi?keywords=noteworthy;keywords_type=allwords;bug_severity=enhancement;resolution=FIXED;classification=Modeling;query_format=advanced;version=4.0;component=cdo.core;component=cdo.dawn;component=cdo.db;component=cdo.docs;component=cdo.hibernate;component=cdo.net4j;component=cdo.net4j.db;component=cdo.net4j.ui;component=cdo.objy;component=cdo.releng;component=cdo.ui;product=EMF New And Noteworthy for CDO 4.0]'''<br>
  
===DB Storage Adapter===
+
|}
* Pluggable SQL dialect adapters
+
* Pluggable mapping strategies
+
* Supports horizontal mapping strategy (one table per concrete class)
+
* Supports vertical mapping strategy (TBD, one table per class in hierarchy)
+
* Supports different mapping modes for collections
+
  
 +
<br>
  
==Project Resources==
+
== Model Integration Features  ==
  
* [http://www.eclipse.org/modeling/emft/downloads/index.php?project=cdo&showAll=0&showMax=5 CDO Downloads] and [http://www.eclipse.org/modeling/emft/news/relnotes.php?project=cdo&version=HEAD Release notes]
+
*EMF integration at model level (as opposed to the edit level)
* [http://www.eclipse.org/modeling/emft/updates/ EMFT Update Manager]
+
*Supported model types:
* [http://www.ohloh.net/projects/8908?p=CDO CDO at Ohloh]
+
**Generated models (just switch two .genmodel properties)
* [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.emf/org.eclipse.emf.cdo/?root=Modeling_Project CVS Web Viewer]
+
**Dynamic models (just load .ecore file and commit to repository)  
* [[Media:CDOAndNet4jProjectSet.psf|Eclipse Team Project Set File (PSF) to checkout Net4j and CDO from CVS]]
+
**[[/Legacy Mode/|Legacy models]] (for compiled models without access to .genmodel)
* [http://download.eclipse.org/modeling/emft/cdo/javadoc/0.8.0/ JavaDoc for CDO 0.8.0]
+
**Ecore meta meta model and descendants
* [http://bugs.eclipse.org/bugs/buglist.cgi?product=EMFT&component=CDO&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_status,bugs.target_milestone,bugs.bug_id&query_format=advanced Open Bugs List] or [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EMFT Submit a Bug]
+
* [http://www.eclipse.org/modeling/emft/newsgroup-mailing-list.php Newsgroups & Mailing Lists]
+
  
==Further Reading==
+
<br>
* [[CDO Architecture]]
+
 
* [[CDO Weaver]]
+
== User Interface Features  ==
* [[CDO User Interface]]
+
 
* [[CDO Client]]
+
*Eclipse view for working with CDO sessions, transactions, views and resources
* [[CDO Protocol]]
+
*Package Manager dialog per session
* [[CDO Server]]
+
*Eclipse editor for working with resources and objects
* [[CDO Storage Framework]]
+
*[http://wiki.eclipse.org/CDO/Explorer_%28work_in_progress%29 CDO Explorer]
* [[Net4j]]
+
 
 +
<br>
 +
 
 +
== Client Side Features  ==
 +
 
 +
*Multiple sessions to multiple repositories on multiple servers
 +
*Multiple transactions per session
 +
*Multiple read-only views per session
 +
*Multiple audit views per session (an audit is a view that shows a consistent, historical version of a repository)
 +
*Multiple resources per view (a view is always associated with its own EMF ResourceSet)
 +
*Inter-resource proxy resolution
 +
*Multiple root objects per resource
 +
*Object state shared among all views of a session
 +
*Object graph internally unconnected (unused parts of the graph can easily be reclaimed by the garbage collector)
 +
*Only new and modified objects committed in a transaction
 +
*Transactions can span multiple resources
 +
*Demand loading of objects (resources are populated as they are navigated)
 +
*Partial loading of collections (chunk size can be configured per session)
 +
*Adaptable pre-fetching of objects (different intelligent usage analyzers are available)
 +
*Asynchronous object invalidation (optional)
 +
*Clean API to work with sessions, views, transactions and objects
 +
*CDOResources are [[EObject]]s as well
 +
*Objects carry meta information like id, state, version and life span
 +
*Support for [[OSGi]] environments (headless, Eclipse [[RCP]], ...)
 +
*Support for standalone applications (non-OSGi)
 +
 
 +
<br>
 +
 
 +
== Network Protocol Features  ==
 +
 
 +
*[[Net4j]] based binary application protocol
 +
*Pluggable transport layer (shipped with NIO socket transport, polling HTTP and JVM embedded transport)
 +
*Pluggable fail over support
 +
*Pluggable authentication (shipped with challenge/response negotiation)
 +
*Multiple acceptors per server
 +
 
 +
<br>
 +
 
 +
== Server Side Features  ==
 +
 
 +
*Pluggable storage adapters
 +
**See [[CDO/DB Store|DB Store Features]]
 +
**See [[CDO/Hibernate_Store|Hibernate Store Features]]  
 +
**See [http://download.eclipse.org/modeling/emf/cdo/drops/R20140610-0212/help/org.eclipse.emf.cdo.doc/html/reference/StoreFeatures.html Store Feature Matrix]
 +
**Objectivity support coming soon
 +
**Native memory storage adapter
 +
*Multiple repositories per server
 +
*Multiple models (packages) per repository
 +
*Multiple resources (instance documents) per repository
 +
*Expressive XML configuration file
 +
*Configurable storage adapter per repository (see below)
 +
*Configurable caching per repository
 +
*Clean API to work with repositories, sessions, views, transactions and revisions
 +
*Support for OSGi environments (usually headless)
 +
*Support for standalone applications (non-OSGi)
 +
 
 +
<br> <br>
  
 
----
 
----
Wikis: [[Net4j]] | [[EMF]] | [[Eclipse]]
+
 
 +
Wikis: [[Net4j]] | [[EMF]] | [[Eclipse]]
 +
 
 +
[[Category:Modeling]] [[Category:EMF]] [[Category:CDO]] [[Category:Net4j]]

Latest revision as of 12:05, 1 November 2016


CDOOverview.png  
 
 

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, 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.

You may also want to visit our homepage.


Documentation

CDO Explorer
CDO Poster
Client Architecture
Server Configuration
CDO Presentations
Webinar 2010/04

Tutorials

Preparing EMF Models for CDO
Using the CDO User Interface
Tweaking CDO Performance
User Contributed Documentation

Resources

FAQ
Downloads and Updates
Source Installation
Development Guidelines
Release Engineering

Features

Model Integration
User Interface
Client Side
Network Protocol
Server Side
DB Store
MongoDB Store
Hibernate Store: Quick Start, Tutorial
Objectivity Store
New And Noteworthy for CDO 2.0
New And Noteworthy for CDO 3.0
New And Noteworthy for CDO 4.0


Model Integration Features

  • EMF integration at model level (as opposed to the edit level)
  • Supported model types:
    • Generated models (just switch two .genmodel properties)
    • Dynamic models (just load .ecore file and commit to repository)
    • Legacy models (for compiled models without access to .genmodel)
    • Ecore meta meta model and descendants


User Interface Features

  • Eclipse view for working with CDO sessions, transactions, views and resources
  • Package Manager dialog per session
  • Eclipse editor for working with resources and objects
  • CDO Explorer


Client Side Features

  • Multiple sessions to multiple repositories on multiple servers
  • Multiple transactions per session
  • Multiple read-only views per session
  • Multiple audit views per session (an audit is a view that shows a consistent, historical version of a repository)
  • Multiple resources per view (a view is always associated with its own EMF ResourceSet)
  • Inter-resource proxy resolution
  • Multiple root objects per resource
  • Object state shared among all views of a session
  • Object graph internally unconnected (unused parts of the graph can easily be reclaimed by the garbage collector)
  • Only new and modified objects committed in a transaction
  • Transactions can span multiple resources
  • Demand loading of objects (resources are populated as they are navigated)
  • Partial loading of collections (chunk size can be configured per session)
  • Adaptable pre-fetching of objects (different intelligent usage analyzers are available)
  • Asynchronous object invalidation (optional)
  • Clean API to work with sessions, views, transactions and objects
  • CDOResources are EObjects as well
  • Objects carry meta information like id, state, version and life span
  • Support for OSGi environments (headless, Eclipse RCP, ...)
  • Support for standalone applications (non-OSGi)


Network Protocol Features

  • Net4j based binary application protocol
  • Pluggable transport layer (shipped with NIO socket transport, polling HTTP and JVM embedded transport)
  • Pluggable fail over support
  • Pluggable authentication (shipped with challenge/response negotiation)
  • Multiple acceptors per server


Server Side Features

  • Pluggable storage adapters
  • Multiple repositories per server
  • Multiple models (packages) per repository
  • Multiple resources (instance documents) per repository
  • Expressive XML configuration file
  • Configurable storage adapter per repository (see below)
  • Configurable caching per repository
  • Clean API to work with repositories, sessions, views, transactions and revisions
  • Support for OSGi environments (usually headless)
  • Support for standalone applications (non-OSGi)




Wikis: Net4j | EMF | Eclipse

Back to the top