Skip to main content
aboutsummaryrefslogtreecommitdiffstats
blob: 1fad1077902726e6639c5e4f9093790541011233 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>

<HEAD>
<TITLE>Understanding the Architecture of a Repository (CDO Model Repository Documentation)</TITLE>

<LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">

<SCRIPT type="text/javascript">
function windowTitle()
{
    if (location.href.indexOf('is-external=true') == -1) {
        parent.document.title="Understanding the Architecture of a Repository (CDO Model Repository Documentation)";
    }
}
</SCRIPT>
<NOSCRIPT></NOSCRIPT>
</HEAD>

<BODY BGCOLOR="white" onload="windowTitle();">
<!-- <div class="help_breadcrumbs"><a href="../../Overview.html" title="CDO Model Repository Documentation">CDO Model Repository Documentation</a> > <a href="../index.html" title="Category in CDO Model Repository Documentation">Programmer's Guide</a> > <a href="index.html" title="Category in CDO Model Repository Documentation">Dealing with Servers</a></div> -->

<table border="0">
	<tr>
		<td width="100%"><h1>Understanding the Architecture of a Repository</h1></td>
		<td align="right" valign="middle" nowrap><a href="index.html" title="Backward to Dealing with Servers"><img src="../../../images/backward.png" border="0"></a>&nbsp;<a href="../../reference/index.html" title="Forward to Reference"><img src="../../../images/forward.png" border="0"></a></td>
	</tr>
</table>
<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, making it possible to connect a
 repository to all sorts of JDBC databases, Hibernate, Objectivity/DB, MongoDB or DB4O.
 <p>
 While technically a CDO repository depends on EMF this dependency is not of equal importance as it is in a CDO
 application. In particular the generated application models are not required to be deployed to the server because a
 CDO repository accesses models reflectively and the model objects are not implemented as <a href="http://download.eclipse.org/modeling/emf/emf/javadoc/2.7.0/org/eclipse/emf/ecore/EObject.html" title="Interface in org.eclipse.emf.ecore"><code>EObjects</code></a> on
 the server.
 <p>
 The following diagram illustrates the major building blocks of a CDO repository: <p align="center"><img src="repository-architecture.png"></p>


<h2><a name="OSGi"></a>1&nbsp;&nbsp;OSGi</h2>


<h2><a name="Core"></a>2&nbsp;&nbsp;CDO Server Core</h2>


<h2><a name="Store"></a>3&nbsp;&nbsp;CDO Store</h2>


<h2><a name="OCL"></a>4&nbsp;&nbsp;OCL</h2>


<h2><a name="Net4j"></a>5&nbsp;&nbsp;Net4j</h2>


<h2><a name="Protocol"></a>6&nbsp;&nbsp;Protocol</h2>


<h2><a name="Transport"></a>7&nbsp;&nbsp;Transport</h2>


<p align="right">
<a href="index.html" title="Backward to Dealing with Servers"><img src="../../../images/backward.png" border="0"></a>&nbsp;<a href="../../reference/index.html" title="Forward to Reference"><img src="../../../images/forward.png" border="0"></a></p>
<HR>
<i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i>
</BODY>
</HTML>

Back to the top