blob: 72a3d1a4028dc92fb4594eedebbc0aecc5b27d1e (
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
70
71
72
73
74
75
76
77
78
79
80
|
/*
* Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Eclipse Public License v1.0
* which accompanies this distribution, and is available at
* http://www.eclipse.org/legal/epl-v10.html
*
* Contributors:
* Eike Stepper - initial API and implementation
*/
package org.eclipse.emf.cdo.doc.programmers.client;
import org.eclipse.emf.ecore.EObject;
/**
* Understanding the Architecture of a Client Application
* <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 {@link EObject EObjects}. 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: {@img application-architecture.png}
*
* @author Eike Stepper
*/
public class Architecture
{
/**
* OSGi
* <p>
* The <i>Open Services Gateway Initiative</i> (OSGi)...
*/
public class OSGi
{
}
/**
* EMF
*/
public class EMF
{
}
/**
* CDO Client
*/
public class Client
{
}
/**
* Net4j Core
*/
public class Net4j
{
}
/**
* Models
*/
public class Models
{
}
/**
* Protocol
*/
public class Protocol
{
}
/**
* Transport
*/
public class Transport
{
}
}
|
