Jump to: navigation, search

Difference between revisions of "CDO"

 
(2 intermediate revisions by the same user not shown)
Line 49: Line 49:
 
[[#Network_Protocol_Features|Network Protocol]]<br>
 
[[#Network_Protocol_Features|Network Protocol]]<br>
 
[[#Server_Side_Features|Server Side]]<br>
 
[[#Server_Side_Features|Server Side]]<br>
[[#DB_Store_Features|DB Store]]<br>
+
[[CDO/DB Store|DB Store]]<br>
 
[[CDO/MongoDB Store|MongoDB Store]]<br>
 
[[CDO/MongoDB Store|MongoDB Store]]<br>
 
[[CDO/Hibernate Store|Hibernate Store]]: [[CDO/Hibernate_Store/Quick_Start|Quick Start]], [[CDO/Hibernate_Store/Tutorial|Tutorial]]<br>
 
[[CDO/Hibernate Store|Hibernate Store]]: [[CDO/Hibernate_Store/Quick_Start|Quick Start]], [[CDO/Hibernate_Store/Tutorial|Tutorial]]<br>
Line 132: Line 132:
 
*Support for OSGi environments (usually headless)  
 
*Support for OSGi environments (usually headless)  
 
*Support for standalone applications (non-OSGi)
 
*Support for standalone applications (non-OSGi)
 
<br>
 
 
== DB Store Features  ==
 
 
*Supports all optional features of the [[#CDO_Server|CDO Server]]
 
*Pluggable SQL dialect adapters
 
*Includes support for [[Derby]], [[H2]], [[HSQLDB]], [[MySQL]] and [[Oracle]] (TBD)
 
*Pluggable mapping strategies
 
*Includes horizontal mapping strategy (one table per concrete class)
 
*Includes vertical mapping strategy (TBD, one table per class in hierarchy)
 
*Supports different mapping modes for collections
 
*Various mapping options by using [[EAnnotation]]
 
  
 
<br> <br>  
 
<br> <br>  

Latest revision as of 00:21, 18 November 2012


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 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
Dealing with Git

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