diff options
Diffstat (limited to 'plugins/org.eclipse.emf.cdo.doc/html/Overview.html')
| -rw-r--r-- | plugins/org.eclipse.emf.cdo.doc/html/Overview.html | 57 |
1 files changed, 53 insertions, 4 deletions
diff --git a/plugins/org.eclipse.emf.cdo.doc/html/Overview.html b/plugins/org.eclipse.emf.cdo.doc/html/Overview.html index fd60c9bfe1..20b603b81d 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/Overview.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/Overview.html @@ -23,10 +23,10 @@ function windowTitle() <BODY BGCOLOR="white" onload="windowTitle();"> <h1><a name="Overview.html"/>Overview</h1> <p> - CDO is a pure Java <i>model repository</i> for your EMF models and meta models (refer to <a href="Overview.html#Application" title="Chapter in CDO Model Repository Documentation">application architecture</a> for details). CDO can also serve as a <i>persistence and distribution framework</i> for - your EMF based application systems. For the sake of this overview a model can be regarded as a graph of application - or business objects and a meta model as a set of classifiers that describe the structure of and the possible - relations between these objects. + CDO is a pure Java <i>model repository</i> for your EMF models and meta models. CDO can also serve as a + <i>persistence and distribution framework</i> for your EMF based application systems. For the sake of this overview a + model can be regarded as a graph of application or business objects and a meta model as a set of classifiers that + describe the structure of and the possible relations between these objects. <p> <h2><a name="Functionality"/>1 Functionality</h2> @@ -123,10 +123,59 @@ function windowTitle() <p> <img src="application-architecture.png"/>. +<h4><a name="OSGi"/>2.1.1 OSGi</h4> + + +<h4><a name="EMF"/>2.1.2 EMF</h4> + + +<h4><a name="CDOClient"/>2.1.3 CDO Client</h4> + + +<h4><a name="Net4j"/>2.1.4 Net4j Core</h4> + + +<h4><a name="Models"/>2.1.5 Models</h4> + + +<h4><a name="Protocol"/>2.1.6 Protocol</h4> + + +<h4><a name="Transport"/>2.1.7 Transport</h4> + + <h3><a name="Repository"/>2.2 Repository Architecture</h3> <p> + The main building block of a CDO repository is split into two layers, the generic repository layer that client + applications interact with and the database integration layer that providers can hook into to integrate their + data storage solutions with CDO. A number of such integrations already ship with CDO, as outlined in + <a href="Overview.html#CDOStore" title="Chapter in CDO Model Repository Documentation">CDO Store</a>. + <p> + The following diagram illustrates the major building blocks of a CDO repository: + <p> <img src="repository-architecture.png"/>. +<h4><a name="OSGi"/>2.2.1 OSGi</h4> + + +<h4><a name="CDOServerCore"/>2.2.2 CDO Server Core</h4> + + +<h4><a name="CDOStore"/>2.2.3 CDO Store</h4> + + +<h4><a name="OCL"/>2.2.4 OCL</h4> + + +<h4><a name="Net4j"/>2.2.5 Net4j</h4> + + +<h4><a name="Protocol"/>2.2.6 Protocol</h4> + + +<h4><a name="Transport"/>2.2.7 Transport</h4> + + <HR> <i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i> </BODY> |