Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEike Stepper2011-09-20 10:07:17 +0000
committerEike Stepper2011-09-20 10:07:17 +0000
commit8e0ca0ae40864f12c855aa100711d46f7ad9c176 (patch)
tree255f93cc293359bdf4aeb93888e824fb530fa38d
parent0c89905307ebf59a7bf3597d07e809e43187644f (diff)
downloadcdo-8e0ca0ae40864f12c855aa100711d46f7ad9c176.tar.gz
cdo-8e0ca0ae40864f12c855aa100711d46f7ad9c176.tar.xz
cdo-8e0ca0ae40864f12c855aa100711d46f7ad9c176.zip
overview
-rw-r--r--plugins/org.eclipse.emf.cdo.doc/html/Overview.html57
-rw-r--r--plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Overview.java103
2 files changed, 156 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&nbsp;&nbsp;Functionality</h2>
@@ -123,10 +123,59 @@ function windowTitle()
<p>
<img src="application-architecture.png"/>.
+<h4><a name="OSGi"/>2.1.1&nbsp;&nbsp;OSGi</h4>
+
+
+<h4><a name="EMF"/>2.1.2&nbsp;&nbsp;EMF</h4>
+
+
+<h4><a name="CDOClient"/>2.1.3&nbsp;&nbsp;CDO Client</h4>
+
+
+<h4><a name="Net4j"/>2.1.4&nbsp;&nbsp;Net4j Core</h4>
+
+
+<h4><a name="Models"/>2.1.5&nbsp;&nbsp;Models</h4>
+
+
+<h4><a name="Protocol"/>2.1.6&nbsp;&nbsp;Protocol</h4>
+
+
+<h4><a name="Transport"/>2.1.7&nbsp;&nbsp;Transport</h4>
+
+
<h3><a name="Repository"/>2.2&nbsp;&nbsp;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&nbsp;&nbsp;OSGi</h4>
+
+
+<h4><a name="CDOServerCore"/>2.2.2&nbsp;&nbsp;CDO Server Core</h4>
+
+
+<h4><a name="CDOStore"/>2.2.3&nbsp;&nbsp;CDO Store</h4>
+
+
+<h4><a name="OCL"/>2.2.4&nbsp;&nbsp;OCL</h4>
+
+
+<h4><a name="Net4j"/>2.2.5&nbsp;&nbsp;Net4j</h4>
+
+
+<h4><a name="Protocol"/>2.2.6&nbsp;&nbsp;Protocol</h4>
+
+
+<h4><a name="Transport"/>2.2.7&nbsp;&nbsp;Transport</h4>
+
+
<HR>
<i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i>
</BODY>
diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Overview.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Overview.java
index ccc24cc286..b43790501e 100644
--- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Overview.java
+++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Overview.java
@@ -131,15 +131,118 @@ public class Overview
*/
public class Application
{
+ /**
+ * OSGi
+ */
+ public class OSGi
+ {
+ }
+
+ /**
+ * EMF
+ */
+ public class EMF
+ {
+ }
+
+ /**
+ * CDO Client
+ */
+ public class CDOClient
+ {
+ }
+
+ /**
+ * Net4j Core
+ */
+ public class Net4j
+ {
+ }
+
+ /**
+ * Models
+ */
+ public class Models
+ {
+ }
+
+ /**
+ * Protocol
+ */
+ public class Protocol
+ {
+ }
+
+ /**
+ * Transport
+ */
+ public class Transport
+ {
+ }
}
/**
* Repository Architecture
* <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
+ * {@link CDOStore}.
+ * <p>
+ * The following diagram illustrates the major building blocks of a CDO repository:
+ * <p>
* <img src="repository-architecture.png"/>.
*/
public class Repository
{
+ /**
+ * OSGi
+ */
+ public class OSGi
+ {
+ }
+
+ /**
+ * CDO Server Core
+ */
+ public class CDOServerCore
+ {
+ }
+
+ /**
+ * CDO Store
+ */
+ public class CDOStore
+ {
+ }
+
+ /**
+ * OCL
+ */
+ public class OCL
+ {
+ }
+
+ /**
+ * Net4j
+ */
+ public class Net4j
+ {
+ }
+
+ /**
+ * Protocol
+ */
+ public class Protocol
+ {
+ }
+
+ /**
+ * Transport
+ */
+ public class Transport
+ {
+ }
}
}
}

Back to the top