blob: e39630ef1feb1167aab1d406ce5b1c06eecba73b (
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
|
<!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 Client Application (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 Client Application (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">Developing Client Applications</a></div> -->
<table border="0">
<tr>
<td width="100%"><h1>Understanding the Architecture of a Client Application</h1></td>
<td align="right" valign="middle" nowrap><a href="index.html" title="Backward to Developing Client Applications"><img src="../../../images/backward.png" border="0"></a> <a href="../server/index.html" title="Forward to Dealing with Servers"><img src="../../../images/forward.png" border="0"></a></td>
</tr>
</table>
<p class="author">Author: Eike Stepper</p>
<p>
The architecture of a CDO application is characterized by its mandatory dependency on EMF, the Eclipse Modeling
Framework. Most of the time an application interacts with the object graph of the model through standard EMF APIs
because CDO model graph objects are <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>. While CDO's basic functionality integrates nicely and
transparently with EMF's extension mechansims some of the more advanced functions may require to add direct
dependendcies on CDO to your application code.
<p>
The following diagram illustrates the major building blocks of a CDO application: <p align="center"><img src="application-architecture.png"></p>
<h2><a name="OSGi"></a>1 OSGi</h2>
<h2><a name="EMF"></a>2 EMF</h2>
<h2><a name="Client"></a>3 CDO Client</h2>
<h2><a name="Net4j"></a>4 Net4j Core</h2>
<h2><a name="Models"></a>5 Models</h2>
<h2><a name="Protocol"></a>6 Protocol</h2>
<h2><a name="Transport"></a>7 Transport</h2>
<p align="right">
<a href="index.html" title="Backward to Developing Client Applications"><img src="../../../images/backward.png" border="0"></a> <a href="../server/index.html" title="Forward to Dealing with Servers"><img src="../../../images/forward.png" border="0"></a></p>
<HR>
<i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i>
</BODY>
</HTML>
|
