diff options
Diffstat (limited to 'plugins/org.eclipse.emf.cdo.doc/html')
12 files changed, 660 insertions, 660 deletions
diff --git a/plugins/org.eclipse.emf.cdo.doc/html/Overview.html b/plugins/org.eclipse.emf.cdo.doc/html/Overview.html index 7b3efa9f6d..d53df26fbf 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/Overview.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/Overview.html @@ -1,174 +1,174 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> -<HTML> - -<HEAD> -<TITLE>Overview (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="Overview (CDO Model Repository Documentation)"; - } -} -</SCRIPT> -<NOSCRIPT></NOSCRIPT> -</HEAD> - -<BODY BGCOLOR="white" onload="windowTitle();"> -<!-- <div class="help_breadcrumbs"><a href="" title="CDO Model Repository Documentation">CDO Model Repository Documentation</a></div> --> - -<table border="0"> - <tr> - <td width="100%"><h1>Overview</h1></td> - <td align="right" valign="middle" nowrap> <a href="programmers/index.html" title="Forward to Programmer's Guide"><img src="../images/forward.png" border="0"></a></td> - </tr> -</table> -<p class="author">Author: Eike Stepper</p> -<p> - 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> - CDO supports plentyfold deployments such as embedded repositories, offline clones or replicated clusters. The - following diagram illustrates the most common scenario: <p align="center"><img src="cdo-overview.png"></p> - - -<h2><a name="Functionality"></a>1 Functionality</h2> -<p> - The main functionality of CDO can be summarized as follows: - <dl> - <dt><b>Persistence</b> - <dd>Persistence of your models in all kinds of database backends like major relational databases or NoSQL - databases. CDO keeps your application code free of vendor specific data access code and eases transitions between - the supported backend types. - <p> - <dt><b>Multi User Access</b> - <dd>Multi user access to your models is supported through the notion of repository sessions. The physical transport - of sessions is pluggable and repositories can be configured to require secure authentication of users. Various - authorization policies can be established programmatically. - <p> - <dt><b>Transactional Access</b> - <dd>Transactional access to your models with ACID properties is provided by optimistic and/or pessimistic locking - on a per object granule. Transactions support multiple savepoints that changes can be rolled back to. Pessimistic - locks can be acquired separately for read access, write access and the option to reserve write access in the - future. All kinds of locks can optionally be turned into long lasting locks that survive repository restarts. - Transactional modification of models in multiple repositories is provided through the notion of XA transactions - with a two phase commit protocol. - <p> - <dt><b>Transparent Temporality</b> - <dd>Transparent temporality is available through audit views, a special kind of read only transactions that provide - you with a consistent model object graph exactly in the state it has been at a point in the past. Depending on the - chosen backend type the storage of the audit data can lead to considerable increase of database sizes in time. - Therefore it can be configured per repository. - <p> - <dt><b>Parallel Evolution</b> - <dd>Parallel evolution of the object graph stored in a repository through the concept of branches similar to source - code management systems like Subversion or Git. Comparisons or merges between any two branch points are supported - through sophisticated APIs, as well as the reconstruction of committed change sets or old states of single objects. - <p> - <dt><b>Scalability</b> - <dd>Scalability, the ability to store and access models of arbitrary size, is transparently achieved by loading - single objects on demand and caching them <i>softly</i> in your application. That implies that objects that are no - longer referenced by the application are automatically garbage collected when memory runs low. Lazy loading is - accompanied by various prefetching strategies, including the monitoring of the object graph's <i>usage</i> and the - calculation of fetch rules that are optimal for the current usage patterns. The scalability of EMF applications can - be further increased by leveraging CDO constructs such as remote cross referencing or optimized content adapters. - <p> - <dt><b>Thread Safety</b> - <dd>Thread safety ensures that multiple threads of your application can access and modify the object graph without - worrying about the synchronization details. This is possible and cheap because multiple transactions can be opened - from within a single session and they all share the same object data until one of them modifies the graph. Possible - commit conflicts can be handled in the same way as if they were conflicts between different sessions. - <p> - <dt><b>Collaboration</b> - <dd>Collaboration on models with CDO is a snap because an application can opt in to be notified about remote - changes to the object graph. By default your local object graph transparently changes when it has changed remotely. - With configurable change subscription policies you can fine tune the characteristics of your <i>distributed shared - model</i> so that all users enjoy the impression to collaborate on a single instance of an object graph. The level - of collaboration can be further increased by plugging custom collaboration handlers into the asynchronous CDO - protocol. - <p> - <dt><b>Data Integrity</b> - <dd>Data integrity can be ensured by enabling optional commit checks in the repository server such as referential - integrity checks and containment cycle checks, as well as custom checks implemented by write access handlers. - <p> - <dt><b>Fault Tolerance</b> - <dd>Fault tolerance on multiple levels, namely the setup of fail-over clusters of replicating repositories under - the control of a fail-over monitor, as well as the usage of a number of special session types such as fail-over or - reconnecting sessions that allow applications to hold on their copy of the object graph even though the physical - repository connection has broken down or changed to a different fail-over participant. - <p> - <dt><b>Offline Work</b> - <dd>Offline work with your models is supported by two different mechanisms: - <ul> - <li>One way is to create a <b>clone</b> of a complete remote repository, including all history of all branches. - Such a clone is continuously synchronized with its remote master and can either act as an embedded repository to - make a single application tolerant against network outage or it can be set up to serve multiple clients, e.g., to - compensate low latency master connections and speed up read access to the object graph. - <p> - <li>An entirely different and somewhat lighter approach to offline work is to check out a single version of the - object graph from a particular branch point of the repository into a local CDO <b>workspace</b>. Such a workspace - behaves similar to a local repository without branching or history capture, in particular it supports multiple - concurrent transactions on the local checkout. In addition it supports most remote functionality that is known from - source code management systems such as update, merge, compare, revert and check in. - </ul> - </dl> - -<h2><a name="Architecture"></a>2 Architecture</h2> -<p> - The architecture of CDO comprises applications and repositories. Despite a number of embedding options applications - are usually deployed to client nodes and repositories to server nodes. They communicate through an application - level CDO protocol which can be driven through various kinds of physical transports, including fast intra JVM - connections. - <p> - CDO has been designed to take full advantage of the OSGi platform, if available at runtime, but can perfectly be - operated in standalone deployments or in various kinds of containers such as JEE web or application servers. - <p> - The following chapters give an overview about the architecures of applications and repositories, respectively. - -<h3><a name="Client"></a>2.1 Client Architecture</h3> -<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="programmers/client/application-architecture.png"></p> -<p><b>See Also:</b></p> -<ul> - <li><a href="programmers/client/Architecture.html" title="Article in CDO Model Repository Documentation">Understanding the Architecture of a Client Application</a></li> -</ul> - - -<h3><a name="Repository"></a>2.2 Repository Architecture</h3> -<p> - <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="programmers/server/repository-architecture.png"></p> -<p><b>See Also:</b></p> -<ul> - <li><a href="programmers/server/Architecture.html" title="Article in CDO Model Repository Documentation">Understanding the Architecture of a Repository</a></li> -</ul> - - -<p align="right"> - <a href="programmers/index.html" title="Forward to Programmer's Guide"><img src="../images/forward.png" border="0"></a></p> -<HR> -<i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i> -</BODY> -</HTML> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+
+<HEAD>
+<TITLE>Overview (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="Overview (CDO Model Repository Documentation)";
+ }
+}
+</SCRIPT>
+<NOSCRIPT></NOSCRIPT>
+</HEAD>
+
+<BODY BGCOLOR="white" onload="windowTitle();">
+<!-- <div class="help_breadcrumbs"><a href="" title="CDO Model Repository Documentation">CDO Model Repository Documentation</a></div> -->
+
+<table border="0">
+ <tr>
+ <td width="100%"><h1>Overview</h1></td>
+ <td align="right" valign="middle" nowrap> <a href="programmers/index.html" title="Forward to Programmer's Guide"><img src="../images/forward.png" border="0"></a></td>
+ </tr>
+</table>
+<p class="author">Author: Eike Stepper</p>
+<p>
+ 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>
+ CDO supports plentyfold deployments such as embedded repositories, offline clones or replicated clusters. The
+ following diagram illustrates the most common scenario: <p align="center"><img src="cdo-overview.png"></p>
+
+
+<h2><a name="Functionality"></a>1 Functionality</h2>
+<p>
+ The main functionality of CDO can be summarized as follows:
+ <dl>
+ <dt><b>Persistence</b>
+ <dd>Persistence of your models in all kinds of database backends like major relational databases or NoSQL
+ databases. CDO keeps your application code free of vendor specific data access code and eases transitions between
+ the supported backend types.
+ <p>
+ <dt><b>Multi User Access</b>
+ <dd>Multi user access to your models is supported through the notion of repository sessions. The physical transport
+ of sessions is pluggable and repositories can be configured to require secure authentication of users. Various
+ authorization policies can be established programmatically.
+ <p>
+ <dt><b>Transactional Access</b>
+ <dd>Transactional access to your models with ACID properties is provided by optimistic and/or pessimistic locking
+ on a per object granule. Transactions support multiple savepoints that changes can be rolled back to. Pessimistic
+ locks can be acquired separately for read access, write access and the option to reserve write access in the
+ future. All kinds of locks can optionally be turned into long lasting locks that survive repository restarts.
+ Transactional modification of models in multiple repositories is provided through the notion of XA transactions
+ with a two phase commit protocol.
+ <p>
+ <dt><b>Transparent Temporality</b>
+ <dd>Transparent temporality is available through audit views, a special kind of read only transactions that provide
+ you with a consistent model object graph exactly in the state it has been at a point in the past. Depending on the
+ chosen backend type the storage of the audit data can lead to considerable increase of database sizes in time.
+ Therefore it can be configured per repository.
+ <p>
+ <dt><b>Parallel Evolution</b>
+ <dd>Parallel evolution of the object graph stored in a repository through the concept of branches similar to source
+ code management systems like Subversion or Git. Comparisons or merges between any two branch points are supported
+ through sophisticated APIs, as well as the reconstruction of committed change sets or old states of single objects.
+ <p>
+ <dt><b>Scalability</b>
+ <dd>Scalability, the ability to store and access models of arbitrary size, is transparently achieved by loading
+ single objects on demand and caching them <i>softly</i> in your application. That implies that objects that are no
+ longer referenced by the application are automatically garbage collected when memory runs low. Lazy loading is
+ accompanied by various prefetching strategies, including the monitoring of the object graph's <i>usage</i> and the
+ calculation of fetch rules that are optimal for the current usage patterns. The scalability of EMF applications can
+ be further increased by leveraging CDO constructs such as remote cross referencing or optimized content adapters.
+ <p>
+ <dt><b>Thread Safety</b>
+ <dd>Thread safety ensures that multiple threads of your application can access and modify the object graph without
+ worrying about the synchronization details. This is possible and cheap because multiple transactions can be opened
+ from within a single session and they all share the same object data until one of them modifies the graph. Possible
+ commit conflicts can be handled in the same way as if they were conflicts between different sessions.
+ <p>
+ <dt><b>Collaboration</b>
+ <dd>Collaboration on models with CDO is a snap because an application can opt in to be notified about remote
+ changes to the object graph. By default your local object graph transparently changes when it has changed remotely.
+ With configurable change subscription policies you can fine tune the characteristics of your <i>distributed shared
+ model</i> so that all users enjoy the impression to collaborate on a single instance of an object graph. The level
+ of collaboration can be further increased by plugging custom collaboration handlers into the asynchronous CDO
+ protocol.
+ <p>
+ <dt><b>Data Integrity</b>
+ <dd>Data integrity can be ensured by enabling optional commit checks in the repository server such as referential
+ integrity checks and containment cycle checks, as well as custom checks implemented by write access handlers.
+ <p>
+ <dt><b>Fault Tolerance</b>
+ <dd>Fault tolerance on multiple levels, namely the setup of fail-over clusters of replicating repositories under
+ the control of a fail-over monitor, as well as the usage of a number of special session types such as fail-over or
+ reconnecting sessions that allow applications to hold on their copy of the object graph even though the physical
+ repository connection has broken down or changed to a different fail-over participant.
+ <p>
+ <dt><b>Offline Work</b>
+ <dd>Offline work with your models is supported by two different mechanisms:
+ <ul>
+ <li>One way is to create a <b>clone</b> of a complete remote repository, including all history of all branches.
+ Such a clone is continuously synchronized with its remote master and can either act as an embedded repository to
+ make a single application tolerant against network outage or it can be set up to serve multiple clients, e.g., to
+ compensate low latency master connections and speed up read access to the object graph.
+ <p>
+ <li>An entirely different and somewhat lighter approach to offline work is to check out a single version of the
+ object graph from a particular branch point of the repository into a local CDO <b>workspace</b>. Such a workspace
+ behaves similar to a local repository without branching or history capture, in particular it supports multiple
+ concurrent transactions on the local checkout. In addition it supports most remote functionality that is known from
+ source code management systems such as update, merge, compare, revert and check in.
+ </ul>
+ </dl>
+
+<h2><a name="Architecture"></a>2 Architecture</h2>
+<p>
+ The architecture of CDO comprises applications and repositories. Despite a number of embedding options applications
+ are usually deployed to client nodes and repositories to server nodes. They communicate through an application
+ level CDO protocol which can be driven through various kinds of physical transports, including fast intra JVM
+ connections.
+ <p>
+ CDO has been designed to take full advantage of the OSGi platform, if available at runtime, but can perfectly be
+ operated in standalone deployments or in various kinds of containers such as JEE web or application servers.
+ <p>
+ The following chapters give an overview about the architecures of applications and repositories, respectively.
+
+<h3><a name="Client"></a>2.1 Client Architecture</h3>
+<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="programmers/client/application-architecture.png"></p>
+<p><b>See Also:</b></p>
+<ul>
+ <li><a href="programmers/client/Architecture.html" title="Article in CDO Model Repository Documentation">Understanding the Architecture of a Client Application</a></li>
+</ul>
+
+
+<h3><a name="Repository"></a>2.2 Repository Architecture</h3>
+<p>
+ <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="programmers/server/repository-architecture.png"></p>
+<p><b>See Also:</b></p>
+<ul>
+ <li><a href="programmers/server/Architecture.html" title="Article in CDO Model Repository Documentation">Understanding the Architecture of a Repository</a></li>
+</ul>
+
+
+<p align="right">
+ <a href="programmers/index.html" title="Forward to Programmer's Guide"><img src="../images/forward.png" border="0"></a></p>
+<HR>
+<i>Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.</i>
+</BODY>
+</HTML>
diff --git a/plugins/org.eclipse.emf.cdo.doc/html/online/index.html b/plugins/org.eclipse.emf.cdo.doc/html/online/index.html index f6132e1594..40a1e1c031 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/online/index.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/online/index.html @@ -1,42 +1,42 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> -<HTML> - -<HEAD> -<TITLE>Online Docs (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="Online Docs (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></div> --> - -<table border="0"> - <tr> - <td width="100%"><h1>Online Docs</h1></td> - <td align="right" valign="middle" nowrap><a href="../reference/MappingStrategies.html" title="Backward to DBStore Mapping Strategies"><img src="../../images/backward.png" border="0"></a> <a href="http://www.eclipse.org/cdo" title="Forward to Homepage"><img src="../../images/forward.png" border="0"></a></td> - </tr> -</table> -<p> -<table border="0"> -<tr><td><img src="../../images/article.gif"> </td><td colspan="3"><a href="http://www.eclipse.org/cdo" title="Article in CDO Model Repository Documentation">Homepage</a></td></tr> -<tr><td><img src="../../images/article.gif"> </td><td colspan="3"><a href="http://wiki.eclipse.org/CDO" title="Article in CDO Model Repository Documentation">Wiki</a></td></tr> -</table> -</p> - - -<p align="right"> -<a href="../reference/MappingStrategies.html" title="Backward to DBStore Mapping Strategies"><img src="../../images/backward.png" border="0"></a> <a href="http://www.eclipse.org/cdo" title="Forward to Homepage"><img src="../../images/forward.png" border="0"></a></p> -<HR> -<i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i> -</BODY> -</HTML> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+
+<HEAD>
+<TITLE>Online Docs (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="Online Docs (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></div> -->
+
+<table border="0">
+ <tr>
+ <td width="100%"><h1>Online Docs</h1></td>
+ <td align="right" valign="middle" nowrap><a href="../reference/MappingStrategies.html" title="Backward to DBStore Mapping Strategies"><img src="../../images/backward.png" border="0"></a> <a href="http://www.eclipse.org/cdo" title="Forward to Homepage"><img src="../../images/forward.png" border="0"></a></td>
+ </tr>
+</table>
+<p>
+<table border="0">
+<tr><td><img src="../../images/article.gif"> </td><td colspan="3"><a href="http://www.eclipse.org/cdo" title="Article in CDO Model Repository Documentation">Homepage</a></td></tr>
+<tr><td><img src="../../images/article.gif"> </td><td colspan="3"><a href="http://wiki.eclipse.org/CDO" title="Article in CDO Model Repository Documentation">Wiki</a></td></tr>
+</table>
+</p>
+
+
+<p align="right">
+<a href="../reference/MappingStrategies.html" title="Backward to DBStore Mapping Strategies"><img src="../../images/backward.png" border="0"></a> <a href="http://www.eclipse.org/cdo" title="Forward to Homepage"><img src="../../images/forward.png" border="0"></a></p>
+<HR>
+<i>Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.</i>
+</BODY>
+</HTML>
diff --git a/plugins/org.eclipse.emf.cdo.doc/html/programmers/client/Architecture.html b/plugins/org.eclipse.emf.cdo.doc/html/programmers/client/Architecture.html index fe3b567dcb..bb2b7422b4 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/programmers/client/Architecture.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/programmers/client/Architecture.html @@ -1,67 +1,67 @@ -<!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="ViewProviders.html" title="Forward to View Providers"><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> -<p> - The <i>Open Services Gateway Initiative</i> (OSGi)... - -<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="ViewProviders.html" title="Forward to View Providers"><img src="../../../images/forward.png" border="0"></a></p> -<HR> -<i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i> -</BODY> -</HTML> +<!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="ViewProviders.html" title="Forward to View Providers"><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>
+<p>
+ The <i>Open Services Gateway Initiative</i> (OSGi)...
+
+<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="ViewProviders.html" title="Forward to View Providers"><img src="../../../images/forward.png" border="0"></a></p>
+<HR>
+<i>Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.</i>
+</BODY>
+</HTML>
diff --git a/plugins/org.eclipse.emf.cdo.doc/html/programmers/client/ViewProviders.html b/plugins/org.eclipse.emf.cdo.doc/html/programmers/client/ViewProviders.html index d1d2cf3a59..c9d4220c96 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/programmers/client/ViewProviders.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/programmers/client/ViewProviders.html @@ -185,6 +185,6 @@ function windowTitle() <p align="right"> <a href="Architecture.html" title="Backward to Understanding the Architecture of a Client Application"><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> +<i>Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.</i> </BODY> </HTML> diff --git a/plugins/org.eclipse.emf.cdo.doc/html/programmers/client/index.html b/plugins/org.eclipse.emf.cdo.doc/html/programmers/client/index.html index d58f54b6d6..f50483c0a1 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/programmers/client/index.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/programmers/client/index.html @@ -1,52 +1,52 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> -<HTML> - -<HEAD> -<TITLE>Developing Client Applications (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="Developing Client Applications (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></div> --> - -<table border="0"> - <tr> - <td width="100%"><h1>Developing Client Applications</h1></td> - <td align="right" valign="middle" nowrap><a href="../index.html" title="Backward to Programmer's Guide"><img src="../../../images/backward.png" border="0"></a> <a href="Architecture.html" title="Forward to Understanding the Architecture of a Client Application"><img src="../../../images/forward.png" border="0"></a></td> - </tr> -</table> -<p> -<table border="0"> -<tr><td><img src="../../../images/article.gif"> </td><td colspan="4"><a href="Architecture.html" title="Article in CDO Model Repository Documentation">Understanding the Architecture of a Client Application</a></td></tr> -<tr><td></td><td>1 </td><td colspan="3"><a href="Architecture.html#OSGi" title="Chapter in CDO Model Repository Documentation">OSGi</a></td></tr> -<tr><td></td><td>2 </td><td colspan="3"><a href="Architecture.html#EMF" title="Chapter in CDO Model Repository Documentation">EMF</a></td></tr> -<tr><td></td><td>3 </td><td colspan="3"><a href="Architecture.html#Client" title="Chapter in CDO Model Repository Documentation">CDO Client</a></td></tr> -<tr><td></td><td>4 </td><td colspan="3"><a href="Architecture.html#Net4j" title="Chapter in CDO Model Repository Documentation">Net4j Core</a></td></tr> -<tr><td></td><td>5 </td><td colspan="3"><a href="Architecture.html#Models" title="Chapter in CDO Model Repository Documentation">Models</a></td></tr> -<tr><td></td><td>6 </td><td colspan="3"><a href="Architecture.html#Protocol" title="Chapter in CDO Model Repository Documentation">Protocol</a></td></tr> -<tr><td></td><td>7 </td><td colspan="3"><a href="Architecture.html#Transport" title="Chapter in CDO Model Repository Documentation">Transport</a></td></tr> -<tr><td><img src="../../../images/article.gif"> </td><td colspan="4"><a href="ViewProviders.html" title="Article in CDO Model Repository Documentation">View Providers</a></td></tr> -<tr><td></td><td>1 </td><td colspan="3"><a href="ViewProviders.html#ProviderImplementation" title="Chapter in CDO Model Repository Documentation">Implementing a View Provider</a></td></tr> -<tr><td></td><td>2 </td><td colspan="3"><a href="ViewProviders.html#ContributeProviderProgrammatically" title="Chapter in CDO Model Repository Documentation">Contributing View Providers Programmatically</a></td></tr> -<tr><td></td><td>3 </td><td colspan="3"><a href="ViewProviders.html#ContributeProviderUsingExtensionPoint" title="Chapter in CDO Model Repository Documentation">Contributing View Providers Using Extension Points</a></td></tr> -</table> -</p> - - -<p align="right"> -<a href="../index.html" title="Backward to Programmer's Guide"><img src="../../../images/backward.png" border="0"></a> <a href="Architecture.html" title="Forward to Understanding the Architecture of a Client Application"><img src="../../../images/forward.png" border="0"></a></p> -<HR> -<i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i> -</BODY> -</HTML> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+
+<HEAD>
+<TITLE>Developing Client Applications (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="Developing Client Applications (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></div> -->
+
+<table border="0">
+ <tr>
+ <td width="100%"><h1>Developing Client Applications</h1></td>
+ <td align="right" valign="middle" nowrap><a href="../index.html" title="Backward to Programmer's Guide"><img src="../../../images/backward.png" border="0"></a> <a href="Architecture.html" title="Forward to Understanding the Architecture of a Client Application"><img src="../../../images/forward.png" border="0"></a></td>
+ </tr>
+</table>
+<p>
+<table border="0">
+<tr><td><img src="../../../images/article.gif"> </td><td colspan="4"><a href="Architecture.html" title="Article in CDO Model Repository Documentation">Understanding the Architecture of a Client Application</a></td></tr>
+<tr><td></td><td>1 </td><td colspan="3"><a href="Architecture.html#OSGi" title="Chapter in CDO Model Repository Documentation">OSGi</a></td></tr>
+<tr><td></td><td>2 </td><td colspan="3"><a href="Architecture.html#EMF" title="Chapter in CDO Model Repository Documentation">EMF</a></td></tr>
+<tr><td></td><td>3 </td><td colspan="3"><a href="Architecture.html#Client" title="Chapter in CDO Model Repository Documentation">CDO Client</a></td></tr>
+<tr><td></td><td>4 </td><td colspan="3"><a href="Architecture.html#Net4j" title="Chapter in CDO Model Repository Documentation">Net4j Core</a></td></tr>
+<tr><td></td><td>5 </td><td colspan="3"><a href="Architecture.html#Models" title="Chapter in CDO Model Repository Documentation">Models</a></td></tr>
+<tr><td></td><td>6 </td><td colspan="3"><a href="Architecture.html#Protocol" title="Chapter in CDO Model Repository Documentation">Protocol</a></td></tr>
+<tr><td></td><td>7 </td><td colspan="3"><a href="Architecture.html#Transport" title="Chapter in CDO Model Repository Documentation">Transport</a></td></tr>
+<tr><td><img src="../../../images/article.gif"> </td><td colspan="4"><a href="ViewProviders.html" title="Article in CDO Model Repository Documentation">View Providers</a></td></tr>
+<tr><td></td><td>1 </td><td colspan="3"><a href="ViewProviders.html#ProviderImplementation" title="Chapter in CDO Model Repository Documentation">Implementing a View Provider</a></td></tr>
+<tr><td></td><td>2 </td><td colspan="3"><a href="ViewProviders.html#ContributeProviderProgrammatically" title="Chapter in CDO Model Repository Documentation">Contributing View Providers Programmatically</a></td></tr>
+<tr><td></td><td>3 </td><td colspan="3"><a href="ViewProviders.html#ContributeProviderUsingExtensionPoint" title="Chapter in CDO Model Repository Documentation">Contributing View Providers Using Extension Points</a></td></tr>
+</table>
+</p>
+
+
+<p align="right">
+<a href="../index.html" title="Backward to Programmer's Guide"><img src="../../../images/backward.png" border="0"></a> <a href="Architecture.html" title="Forward to Understanding the Architecture of a Client Application"><img src="../../../images/forward.png" border="0"></a></p>
+<HR>
+<i>Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.</i>
+</BODY>
+</HTML>
diff --git a/plugins/org.eclipse.emf.cdo.doc/html/programmers/index.html b/plugins/org.eclipse.emf.cdo.doc/html/programmers/index.html index 8e7885d9e6..4a81655774 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/programmers/index.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/programmers/index.html @@ -1,62 +1,62 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> -<HTML> - -<HEAD> -<TITLE>Programmer's Guide (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="Programmer's Guide (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></div> --> - -<table border="0"> - <tr> - <td width="100%"><h1>Programmer's Guide</h1></td> - <td align="right" valign="middle" nowrap><a href="../Overview.html" title="Backward to Overview"><img src="../../images/backward.png" border="0"></a> <a href="client/index.html" title="Forward to Developing Client Applications"><img src="../../images/forward.png" border="0"></a></td> - </tr> -</table> -<p> -<table border="0"> -<tr><td><img src="../../images/category.gif"> </td><td colspan="5"><a href="client/index.html" title="Category in CDO Model Repository Documentation">Developing Client Applications</a></td></tr> -<tr><td></td><td><img src="../../images/article.gif"> </td><td colspan="4"><a href="client/Architecture.html" title="Article in CDO Model Repository Documentation">Understanding the Architecture of a Client Application</a></td></tr> -<tr><td></td><td></td><td>1 </td><td colspan="3"><a href="client/Architecture.html#OSGi" title="Chapter in CDO Model Repository Documentation">OSGi</a></td></tr> -<tr><td></td><td></td><td>2 </td><td colspan="3"><a href="client/Architecture.html#EMF" title="Chapter in CDO Model Repository Documentation">EMF</a></td></tr> -<tr><td></td><td></td><td>3 </td><td colspan="3"><a href="client/Architecture.html#Client" title="Chapter in CDO Model Repository Documentation">CDO Client</a></td></tr> -<tr><td></td><td></td><td>4 </td><td colspan="3"><a href="client/Architecture.html#Net4j" title="Chapter in CDO Model Repository Documentation">Net4j Core</a></td></tr> -<tr><td></td><td></td><td>5 </td><td colspan="3"><a href="client/Architecture.html#Models" title="Chapter in CDO Model Repository Documentation">Models</a></td></tr> -<tr><td></td><td></td><td>6 </td><td colspan="3"><a href="client/Architecture.html#Protocol" title="Chapter in CDO Model Repository Documentation">Protocol</a></td></tr> -<tr><td></td><td></td><td>7 </td><td colspan="3"><a href="client/Architecture.html#Transport" title="Chapter in CDO Model Repository Documentation">Transport</a></td></tr> -<tr><td></td><td><img src="../../images/article.gif"> </td><td colspan="4"><a href="client/ViewProviders.html" title="Article in CDO Model Repository Documentation">View Providers</a></td></tr> -<tr><td></td><td></td><td>1 </td><td colspan="3"><a href="client/ViewProviders.html#ProviderImplementation" title="Chapter in CDO Model Repository Documentation">Implementing a View Provider</a></td></tr> -<tr><td></td><td></td><td>2 </td><td colspan="3"><a href="client/ViewProviders.html#ContributeProviderProgrammatically" title="Chapter in CDO Model Repository Documentation">Contributing View Providers Programmatically</a></td></tr> -<tr><td></td><td></td><td>3 </td><td colspan="3"><a href="client/ViewProviders.html#ContributeProviderUsingExtensionPoint" title="Chapter in CDO Model Repository Documentation">Contributing View Providers Using Extension Points</a></td></tr> -<tr><td><img src="../../images/category.gif"> </td><td colspan="5"><a href="server/index.html" title="Category in CDO Model Repository Documentation">Dealing with Servers</a></td></tr> -<tr><td></td><td><img src="../../images/article.gif"> </td><td colspan="4"><a href="server/Architecture.html" title="Article in CDO Model Repository Documentation">Understanding the Architecture of a Repository</a></td></tr> -<tr><td></td><td></td><td>1 </td><td colspan="3"><a href="server/Architecture.html#OSGi" title="Chapter in CDO Model Repository Documentation">OSGi</a></td></tr> -<tr><td></td><td></td><td>2 </td><td colspan="3"><a href="server/Architecture.html#Core" title="Chapter in CDO Model Repository Documentation">CDO Server Core</a></td></tr> -<tr><td></td><td></td><td>3 </td><td colspan="3"><a href="server/Architecture.html#Store" title="Chapter in CDO Model Repository Documentation">CDO Store</a></td></tr> -<tr><td></td><td></td><td>4 </td><td colspan="3"><a href="server/Architecture.html#Protocol" title="Chapter in CDO Model Repository Documentation">Protocol</a></td></tr> -<tr><td></td><td></td><td>5 </td><td colspan="3"><a href="server/Architecture.html#OCL" title="Chapter in CDO Model Repository Documentation">OCL</a></td></tr> -<tr><td></td><td></td><td>6 </td><td colspan="3"><a href="server/Architecture.html#Net4j" title="Chapter in CDO Model Repository Documentation">Net4j Core</a></td></tr> -<tr><td></td><td></td><td>7 </td><td colspan="3"><a href="server/Architecture.html#Transport" title="Chapter in CDO Model Repository Documentation">Transport</a></td></tr> -</table> -</p> - - -<p align="right"> -<a href="../Overview.html" title="Backward to Overview"><img src="../../images/backward.png" border="0"></a> <a href="client/index.html" title="Forward to Developing Client Applications"><img src="../../images/forward.png" border="0"></a></p> -<HR> -<i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i> -</BODY> -</HTML> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+
+<HEAD>
+<TITLE>Programmer's Guide (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="Programmer's Guide (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></div> -->
+
+<table border="0">
+ <tr>
+ <td width="100%"><h1>Programmer's Guide</h1></td>
+ <td align="right" valign="middle" nowrap><a href="../Overview.html" title="Backward to Overview"><img src="../../images/backward.png" border="0"></a> <a href="client/index.html" title="Forward to Developing Client Applications"><img src="../../images/forward.png" border="0"></a></td>
+ </tr>
+</table>
+<p>
+<table border="0">
+<tr><td><img src="../../images/category.gif"> </td><td colspan="5"><a href="client/index.html" title="Category in CDO Model Repository Documentation">Developing Client Applications</a></td></tr>
+<tr><td></td><td><img src="../../images/article.gif"> </td><td colspan="4"><a href="client/Architecture.html" title="Article in CDO Model Repository Documentation">Understanding the Architecture of a Client Application</a></td></tr>
+<tr><td></td><td></td><td>1 </td><td colspan="3"><a href="client/Architecture.html#OSGi" title="Chapter in CDO Model Repository Documentation">OSGi</a></td></tr>
+<tr><td></td><td></td><td>2 </td><td colspan="3"><a href="client/Architecture.html#EMF" title="Chapter in CDO Model Repository Documentation">EMF</a></td></tr>
+<tr><td></td><td></td><td>3 </td><td colspan="3"><a href="client/Architecture.html#Client" title="Chapter in CDO Model Repository Documentation">CDO Client</a></td></tr>
+<tr><td></td><td></td><td>4 </td><td colspan="3"><a href="client/Architecture.html#Net4j" title="Chapter in CDO Model Repository Documentation">Net4j Core</a></td></tr>
+<tr><td></td><td></td><td>5 </td><td colspan="3"><a href="client/Architecture.html#Models" title="Chapter in CDO Model Repository Documentation">Models</a></td></tr>
+<tr><td></td><td></td><td>6 </td><td colspan="3"><a href="client/Architecture.html#Protocol" title="Chapter in CDO Model Repository Documentation">Protocol</a></td></tr>
+<tr><td></td><td></td><td>7 </td><td colspan="3"><a href="client/Architecture.html#Transport" title="Chapter in CDO Model Repository Documentation">Transport</a></td></tr>
+<tr><td></td><td><img src="../../images/article.gif"> </td><td colspan="4"><a href="client/ViewProviders.html" title="Article in CDO Model Repository Documentation">View Providers</a></td></tr>
+<tr><td></td><td></td><td>1 </td><td colspan="3"><a href="client/ViewProviders.html#ProviderImplementation" title="Chapter in CDO Model Repository Documentation">Implementing a View Provider</a></td></tr>
+<tr><td></td><td></td><td>2 </td><td colspan="3"><a href="client/ViewProviders.html#ContributeProviderProgrammatically" title="Chapter in CDO Model Repository Documentation">Contributing View Providers Programmatically</a></td></tr>
+<tr><td></td><td></td><td>3 </td><td colspan="3"><a href="client/ViewProviders.html#ContributeProviderUsingExtensionPoint" title="Chapter in CDO Model Repository Documentation">Contributing View Providers Using Extension Points</a></td></tr>
+<tr><td><img src="../../images/category.gif"> </td><td colspan="5"><a href="server/index.html" title="Category in CDO Model Repository Documentation">Dealing with Servers</a></td></tr>
+<tr><td></td><td><img src="../../images/article.gif"> </td><td colspan="4"><a href="server/Architecture.html" title="Article in CDO Model Repository Documentation">Understanding the Architecture of a Repository</a></td></tr>
+<tr><td></td><td></td><td>1 </td><td colspan="3"><a href="server/Architecture.html#OSGi" title="Chapter in CDO Model Repository Documentation">OSGi</a></td></tr>
+<tr><td></td><td></td><td>2 </td><td colspan="3"><a href="server/Architecture.html#Core" title="Chapter in CDO Model Repository Documentation">CDO Server Core</a></td></tr>
+<tr><td></td><td></td><td>3 </td><td colspan="3"><a href="server/Architecture.html#Store" title="Chapter in CDO Model Repository Documentation">CDO Store</a></td></tr>
+<tr><td></td><td></td><td>4 </td><td colspan="3"><a href="server/Architecture.html#Protocol" title="Chapter in CDO Model Repository Documentation">Protocol</a></td></tr>
+<tr><td></td><td></td><td>5 </td><td colspan="3"><a href="server/Architecture.html#OCL" title="Chapter in CDO Model Repository Documentation">OCL</a></td></tr>
+<tr><td></td><td></td><td>6 </td><td colspan="3"><a href="server/Architecture.html#Net4j" title="Chapter in CDO Model Repository Documentation">Net4j Core</a></td></tr>
+<tr><td></td><td></td><td>7 </td><td colspan="3"><a href="server/Architecture.html#Transport" title="Chapter in CDO Model Repository Documentation">Transport</a></td></tr>
+</table>
+</p>
+
+
+<p align="right">
+<a href="../Overview.html" title="Backward to Overview"><img src="../../images/backward.png" border="0"></a> <a href="client/index.html" title="Forward to Developing Client Applications"><img src="../../images/forward.png" border="0"></a></p>
+<HR>
+<i>Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.</i>
+</BODY>
+</HTML>
diff --git a/plugins/org.eclipse.emf.cdo.doc/html/programmers/server/Architecture.html b/plugins/org.eclipse.emf.cdo.doc/html/programmers/server/Architecture.html index f894a170ad..6f9e6c90ac 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/programmers/server/Architecture.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/programmers/server/Architecture.html @@ -1,128 +1,128 @@ -<!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> <a href="../../reference/index.html" title="Forward to Reference"><img src="../../../images/forward.png" border="0"></a></td> - </tr> -</table> -<p class="author">Author: Eike Stepper</p> -<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 OSGi</h2> -<p> - All components of CDO are implemented as <a href="http://www.osgi.org">OSGi</a> bundles. The core components of - both clients and servers do not require OSGi to actually run to be functional, they can perfectly be operated - stand-alone. If OSGi is running the setup and configuration of some CDO facilities is a little simpler than in - stand-alone mode because the needed <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/factory/IFactory.html" title="Interface in org.eclipse.net4j.util.factory"><code>factories</code></a> get automatically registered with the central - <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/container/IPluginContainer.html" title="Interface in org.eclipse.net4j.util.container"><code>wiring container</code></a>. - <p> - CDO utilizes an <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/om/OMPlatform.html" title="Interface in org.eclipse.net4j.util.om"><code>operations and maintenance</code></a> framework to abstract common platform services such - as <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/om/log/OMLogger.html" title="Interface in org.eclipse.net4j.util.om.log"><code>logging</code></a>, <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/om/trace/OMTracer.html" title="Interface in org.eclipse.net4j.util.om.trace"><code>tracing</code></a>, <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/om/monitor/OMMonitor.html" title="Interface in org.eclipse.net4j.util.om.monitor"><code>monitoring</code></a> and <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/om/pref/OMPreference.html" title="Interface in org.eclipse.net4j.util.om.pref"><code>configuration</code></a>. Without the need to depend on additional external libraries these services integrate seamlessly - with OSGi, if available at runtime, or emulate similar functionality if running stand-alone. - -<h2><a name="Core"></a>2 CDO Server Core</h2> -<p> - The core of a CDO server consists of one or more <a href="../../../javadoc/org/eclipse/emf/cdo/server/IRepository.html" title="Interface in org.eclipse.emf.cdo.server"><code>repositories</code></a> each of which, in turn, consists - of several generic (network and storage independent) <b>components</b>, such as: - <p> - <ul> - <li>a <a href="../../../javadoc/org/eclipse/emf/cdo/common/revision/CDORevision.html" title="Interface in org.eclipse.emf.cdo.common.revision"><code>revision</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/common/revision/CDORevisionManager.html" title="Interface in org.eclipse.emf.cdo.common.revision"><code>manager</code></a> and <a href="../../../javadoc/org/eclipse/emf/cdo/common/revision/CDORevisionCache.html" title="Interface in org.eclipse.emf.cdo.common.revision"><code>cache</code></a>, - <li>a <a href="../../../javadoc/org/eclipse/emf/cdo/common/branch/CDOBranch.html" title="Interface in org.eclipse.emf.cdo.common.branch"><code>branch</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/common/branch/CDOBranchManager.html" title="Interface in org.eclipse.emf.cdo.common.branch"><code>manager</code></a>, - <li>a <a href="http://download.eclipse.org/modeling/emf/emf/javadoc/2.7.0/org/eclipse/emf/ecore/EPackage.html" title="Interface in org.eclipse.emf.ecore"><code>package</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/common/model/CDOPackageRegistry.html" title="Interface in org.eclipse.emf.cdo.common.model"><code>registry</code></a>, - <li>a <a href="../../../javadoc/org/eclipse/emf/cdo/CDOLock.html" title="Interface in org.eclipse.emf.cdo"><code>lock</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/server/ILockingManager.html" title="Interface in org.eclipse.emf.cdo.server"><code>manager</code></a>, - <li>a <a href="../../../javadoc/org/eclipse/emf/cdo/session/CDOSession.html" title="Interface in org.eclipse.emf.cdo.session"><code>session</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/server/ISessionManager.html" title="Interface in org.eclipse.emf.cdo.server"><code>manager</code></a>, - <li>a <a href="../../../javadoc/org/eclipse/emf/cdo/common/commit/CDOCommitInfo.html" title="Interface in org.eclipse.emf.cdo.common.commit"><code>commit info</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/common/commit/CDOCommitInfoManager.html" title="Interface in org.eclipse.emf.cdo.common.commit"><code>manager</code></a>, - <li>a <a href="../../../javadoc/org/eclipse/emf/cdo/server/IQueryHandler.html" title="Interface in org.eclipse.emf.cdo.server"><code>query handler</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/server/IQueryHandlerProvider.html" title="Interface in org.eclipse.emf.cdo.server"><code>provider</code></a>. - </ul> - <p> - In addition the following types of <b>handlers</b> can be hooked up with a repository: - <p> - <ul> - <li><a href="../../../javadoc/org/eclipse/emf/cdo/server/IRepository.ReadAccessHandler.html" title="Interface in org.eclipse.emf.cdo.server.IRepository"><code>Read access</code></a> handlers, - <li><a href="../../../javadoc/org/eclipse/emf/cdo/server/IRepository.WriteAccessHandler.html" title="Interface in org.eclipse.emf.cdo.server.IRepository"><code>Write access</code></a> handlers, - <li><a href="../../../javadoc/org/eclipse/emf/cdo/common/commit/CDOCommitInfoHandler.html" title="Interface in org.eclipse.emf.cdo.common.commit"><code>Commit info</code></a> handlers. - </ul> - <p> - All <b>persistent aspects</b> (the storage/retrieval of data in/from a database system) are fully abstracted - through the service provider interfaces (SPI) <a href="../../../javadoc/org/eclipse/emf/cdo/server/IStore.html" title="Interface in org.eclipse.emf.cdo.server"><code>IStore</code></a>, <a href="../../../javadoc/org/eclipse/emf/cdo/server/IStoreAccessor.html" title="Interface in org.eclipse.emf.cdo.server"><code>IStoreAccessor</code></a> and <a href="../../../javadoc/org/eclipse/emf/cdo/server/IStoreChunkReader.html" title="Interface in org.eclipse.emf.cdo.server"><code>IStoreChunkReader</code></a>. - Concrete implementations are fully separated and can be plugged into the core as described in <a href="Architecture.html#Store" title="Chapter in CDO Model Repository Documentation">CDO Store</a>. - <p> - All <b>communication aspects</b> (the sending/receiving of signals to/from a network system) are fully abstracted - through the service provider interface (SPI) ISessionProtocol. Concrete implementations are fully separated - and can be plugged into the core as described in <a href="Architecture.html#Protocol" title="Chapter in CDO Model Repository Documentation">Protocol</a>. - -<h2><a name="Store"></a>3 CDO Store</h2> -<p> - A concrete storage adapter, an <a href="../../../javadoc/org/eclipse/emf/cdo/server/IStore.html" title="Interface in org.eclipse.emf.cdo.server"><code>IStore</code></a> implementation, operates on top of the generic <a href="Architecture.html#Core" title="Chapter in CDO Model Repository Documentation">server - core</a>. A number of such stores already ship with CDO, making it possible to connect a repository to all sorts of - JDBC databases, Hibernate, Objectivity/DB, MongoDB or DB4O.<p><b>See Also:</b></p> -<ul> - <li><a href="../../reference/StoreFeatures.html" title="Article in CDO Model Repository Documentation">Store Feature Matrix</a></li> -</ul> - - -<h2><a name="Protocol"></a>4 Protocol</h2> -<p> - A concrete communications adapter, an ISessionProtocol implementation, operates on top of the generic - <a href="Architecture.html#Core" title="Chapter in CDO Model Repository Documentation">server core</a>. The only session protocol implementation that currently ships with CDO is based on - <a href="Architecture.html#Net4j" title="Chapter in CDO Model Repository Documentation">Net4j Core</a>. - -<h2><a name="OCL"></a>5 OCL</h2> - - -<h2><a name="Net4j"></a>6 Net4j Core</h2> -<p> - The <i>Net4j Signalling Platform</i> is an extensible client/server communications framework. Net4j eases the - development of fast and maintainable application <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/signal/ISignalProtocol.html" title="Interface in org.eclipse.net4j.signal"><code>protocols</code></a> that are independent of the - physical <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/connector/IConnector.html" title="Interface in org.eclipse.net4j.connector"><code>transport</code></a> medium. Transport protocols are pluggable and Net4j ships with support for - <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/tcp/ITCPConnector.html" title="Interface in org.eclipse.net4j.tcp"><code>TCP</code></a>, <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/tcp/ssl/SSLUtil.html" title="Class in org.eclipse.net4j.tcp.ssl"><code>SSL</code></a>, <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/http/common/IHTTPConnector.html" title="Interface in org.eclipse.net4j.http.common"><code>HTTP</code></a> and <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/jvm/IJVMConnector.html" title="Interface in org.eclipse.net4j.jvm"><code>JVM</code></a> - (in-process) transport. The core of Net4j is a fast, asynchronous and non-blocking <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/buffer/IBuffer.html" title="Interface in org.eclipse.net4j.buffer"><code>buffer</code></a> - multiplexing kernel, based on <a href="Architecture.html#OSGi" title="Chapter in CDO Model Repository Documentation">OSGi</a> but also executable stand-alone.<p><b>See Also:</b></p> -<ul> - <li><a href="Architecture.html#Transport" title="Chapter in CDO Model Repository Documentation">Transport</a></li> - <li><a href="Architecture.html#Protocol" title="Chapter in CDO Model Repository Documentation">Protocol</a></li> -</ul> - - -<h2><a name="Transport"></a>7 Transport</h2> - - -<p align="right"> -<a href="index.html" title="Backward to Dealing with Servers"><img src="../../../images/backward.png" border="0"></a> <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> +<!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> <a href="../../reference/index.html" title="Forward to Reference"><img src="../../../images/forward.png" border="0"></a></td>
+ </tr>
+</table>
+<p class="author">Author: Eike Stepper</p>
+<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 OSGi</h2>
+<p>
+ All components of CDO are implemented as <a href="http://www.osgi.org">OSGi</a> bundles. The core components of
+ both clients and servers do not require OSGi to actually run to be functional, they can perfectly be operated
+ stand-alone. If OSGi is running the setup and configuration of some CDO facilities is a little simpler than in
+ stand-alone mode because the needed <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/factory/IFactory.html" title="Interface in org.eclipse.net4j.util.factory"><code>factories</code></a> get automatically registered with the central
+ <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/container/IPluginContainer.html" title="Interface in org.eclipse.net4j.util.container"><code>wiring container</code></a>.
+ <p>
+ CDO utilizes an <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/om/OMPlatform.html" title="Interface in org.eclipse.net4j.util.om"><code>operations and maintenance</code></a> framework to abstract common platform services such
+ as <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/om/log/OMLogger.html" title="Interface in org.eclipse.net4j.util.om.log"><code>logging</code></a>, <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/om/trace/OMTracer.html" title="Interface in org.eclipse.net4j.util.om.trace"><code>tracing</code></a>, <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/om/monitor/OMMonitor.html" title="Interface in org.eclipse.net4j.util.om.monitor"><code>monitoring</code></a> and <a href="../../../../org.eclipse.net4j.util.doc/javadoc/org/eclipse/net4j/util/om/pref/OMPreference.html" title="Interface in org.eclipse.net4j.util.om.pref"><code>configuration</code></a>. Without the need to depend on additional external libraries these services integrate seamlessly
+ with OSGi, if available at runtime, or emulate similar functionality if running stand-alone.
+
+<h2><a name="Core"></a>2 CDO Server Core</h2>
+<p>
+ The core of a CDO server consists of one or more <a href="../../../javadoc/org/eclipse/emf/cdo/server/IRepository.html" title="Interface in org.eclipse.emf.cdo.server"><code>repositories</code></a> each of which, in turn, consists
+ of several generic (network and storage independent) <b>components</b>, such as:
+ <p>
+ <ul>
+ <li>a <a href="../../../javadoc/org/eclipse/emf/cdo/common/revision/CDORevision.html" title="Interface in org.eclipse.emf.cdo.common.revision"><code>revision</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/common/revision/CDORevisionManager.html" title="Interface in org.eclipse.emf.cdo.common.revision"><code>manager</code></a> and <a href="../../../javadoc/org/eclipse/emf/cdo/common/revision/CDORevisionCache.html" title="Interface in org.eclipse.emf.cdo.common.revision"><code>cache</code></a>,
+ <li>a <a href="../../../javadoc/org/eclipse/emf/cdo/common/branch/CDOBranch.html" title="Interface in org.eclipse.emf.cdo.common.branch"><code>branch</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/common/branch/CDOBranchManager.html" title="Interface in org.eclipse.emf.cdo.common.branch"><code>manager</code></a>,
+ <li>a <a href="http://download.eclipse.org/modeling/emf/emf/javadoc/2.7.0/org/eclipse/emf/ecore/EPackage.html" title="Interface in org.eclipse.emf.ecore"><code>package</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/common/model/CDOPackageRegistry.html" title="Interface in org.eclipse.emf.cdo.common.model"><code>registry</code></a>,
+ <li>a <a href="../../../javadoc/org/eclipse/emf/cdo/CDOLock.html" title="Interface in org.eclipse.emf.cdo"><code>lock</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/server/ILockingManager.html" title="Interface in org.eclipse.emf.cdo.server"><code>manager</code></a>,
+ <li>a <a href="../../../javadoc/org/eclipse/emf/cdo/session/CDOSession.html" title="Interface in org.eclipse.emf.cdo.session"><code>session</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/server/ISessionManager.html" title="Interface in org.eclipse.emf.cdo.server"><code>manager</code></a>,
+ <li>a <a href="../../../javadoc/org/eclipse/emf/cdo/common/commit/CDOCommitInfo.html" title="Interface in org.eclipse.emf.cdo.common.commit"><code>commit info</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/common/commit/CDOCommitInfoManager.html" title="Interface in org.eclipse.emf.cdo.common.commit"><code>manager</code></a>,
+ <li>a <a href="../../../javadoc/org/eclipse/emf/cdo/server/IQueryHandler.html" title="Interface in org.eclipse.emf.cdo.server"><code>query handler</code></a> <a href="../../../javadoc/org/eclipse/emf/cdo/server/IQueryHandlerProvider.html" title="Interface in org.eclipse.emf.cdo.server"><code>provider</code></a>.
+ </ul>
+ <p>
+ In addition the following types of <b>handlers</b> can be hooked up with a repository:
+ <p>
+ <ul>
+ <li><a href="../../../javadoc/org/eclipse/emf/cdo/server/IRepository.ReadAccessHandler.html" title="Interface in org.eclipse.emf.cdo.server.IRepository"><code>Read access</code></a> handlers,
+ <li><a href="../../../javadoc/org/eclipse/emf/cdo/server/IRepository.WriteAccessHandler.html" title="Interface in org.eclipse.emf.cdo.server.IRepository"><code>Write access</code></a> handlers,
+ <li><a href="../../../javadoc/org/eclipse/emf/cdo/common/commit/CDOCommitInfoHandler.html" title="Interface in org.eclipse.emf.cdo.common.commit"><code>Commit info</code></a> handlers.
+ </ul>
+ <p>
+ All <b>persistent aspects</b> (the storage/retrieval of data in/from a database system) are fully abstracted
+ through the service provider interfaces (SPI) <a href="../../../javadoc/org/eclipse/emf/cdo/server/IStore.html" title="Interface in org.eclipse.emf.cdo.server"><code>IStore</code></a>, <a href="../../../javadoc/org/eclipse/emf/cdo/server/IStoreAccessor.html" title="Interface in org.eclipse.emf.cdo.server"><code>IStoreAccessor</code></a> and <a href="../../../javadoc/org/eclipse/emf/cdo/server/IStoreChunkReader.html" title="Interface in org.eclipse.emf.cdo.server"><code>IStoreChunkReader</code></a>.
+ Concrete implementations are fully separated and can be plugged into the core as described in <a href="Architecture.html#Store" title="Chapter in CDO Model Repository Documentation">CDO Store</a>.
+ <p>
+ All <b>communication aspects</b> (the sending/receiving of signals to/from a network system) are fully abstracted
+ through the service provider interface (SPI) ISessionProtocol. Concrete implementations are fully separated
+ and can be plugged into the core as described in <a href="Architecture.html#Protocol" title="Chapter in CDO Model Repository Documentation">Protocol</a>.
+
+<h2><a name="Store"></a>3 CDO Store</h2>
+<p>
+ A concrete storage adapter, an <a href="../../../javadoc/org/eclipse/emf/cdo/server/IStore.html" title="Interface in org.eclipse.emf.cdo.server"><code>IStore</code></a> implementation, operates on top of the generic <a href="Architecture.html#Core" title="Chapter in CDO Model Repository Documentation">server
+ core</a>. A number of such stores already ship with CDO, making it possible to connect a repository to all sorts of
+ JDBC databases, Hibernate, Objectivity/DB, MongoDB or DB4O.<p><b>See Also:</b></p>
+<ul>
+ <li><a href="../../reference/StoreFeatures.html" title="Article in CDO Model Repository Documentation">Store Feature Matrix</a></li>
+</ul>
+
+
+<h2><a name="Protocol"></a>4 Protocol</h2>
+<p>
+ A concrete communications adapter, an ISessionProtocol implementation, operates on top of the generic
+ <a href="Architecture.html#Core" title="Chapter in CDO Model Repository Documentation">server core</a>. The only session protocol implementation that currently ships with CDO is based on
+ <a href="Architecture.html#Net4j" title="Chapter in CDO Model Repository Documentation">Net4j Core</a>.
+
+<h2><a name="OCL"></a>5 OCL</h2>
+
+
+<h2><a name="Net4j"></a>6 Net4j Core</h2>
+<p>
+ The <i>Net4j Signalling Platform</i> is an extensible client/server communications framework. Net4j eases the
+ development of fast and maintainable application <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/signal/ISignalProtocol.html" title="Interface in org.eclipse.net4j.signal"><code>protocols</code></a> that are independent of the
+ physical <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/connector/IConnector.html" title="Interface in org.eclipse.net4j.connector"><code>transport</code></a> medium. Transport protocols are pluggable and Net4j ships with support for
+ <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/tcp/ITCPConnector.html" title="Interface in org.eclipse.net4j.tcp"><code>TCP</code></a>, <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/tcp/ssl/SSLUtil.html" title="Class in org.eclipse.net4j.tcp.ssl"><code>SSL</code></a>, <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/http/common/IHTTPConnector.html" title="Interface in org.eclipse.net4j.http.common"><code>HTTP</code></a> and <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/jvm/IJVMConnector.html" title="Interface in org.eclipse.net4j.jvm"><code>JVM</code></a>
+ (in-process) transport. The core of Net4j is a fast, asynchronous and non-blocking <a href="../../../../org.eclipse.net4j.doc/javadoc/org/eclipse/net4j/buffer/IBuffer.html" title="Interface in org.eclipse.net4j.buffer"><code>buffer</code></a>
+ multiplexing kernel, based on <a href="Architecture.html#OSGi" title="Chapter in CDO Model Repository Documentation">OSGi</a> but also executable stand-alone.<p><b>See Also:</b></p>
+<ul>
+ <li><a href="Architecture.html#Transport" title="Chapter in CDO Model Repository Documentation">Transport</a></li>
+ <li><a href="Architecture.html#Protocol" title="Chapter in CDO Model Repository Documentation">Protocol</a></li>
+</ul>
+
+
+<h2><a name="Transport"></a>7 Transport</h2>
+
+
+<p align="right">
+<a href="index.html" title="Backward to Dealing with Servers"><img src="../../../images/backward.png" border="0"></a> <a href="../../reference/index.html" title="Forward to Reference"><img src="../../../images/forward.png" border="0"></a></p>
+<HR>
+<i>Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.</i>
+</BODY>
+</HTML>
diff --git a/plugins/org.eclipse.emf.cdo.doc/html/programmers/server/index.html b/plugins/org.eclipse.emf.cdo.doc/html/programmers/server/index.html index a0ceed2b34..f12e177e59 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/programmers/server/index.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/programmers/server/index.html @@ -1,48 +1,48 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> -<HTML> - -<HEAD> -<TITLE>Dealing with Servers (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="Dealing with Servers (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></div> --> - -<table border="0"> - <tr> - <td width="100%"><h1>Dealing with Servers</h1></td> - <td align="right" valign="middle" nowrap><a href="../client/ViewProviders.html" title="Backward to View Providers"><img src="../../../images/backward.png" border="0"></a> <a href="Architecture.html" title="Forward to Understanding the Architecture of a Repository"><img src="../../../images/forward.png" border="0"></a></td> - </tr> -</table> -<p> -<table border="0"> -<tr><td><img src="../../../images/article.gif"> </td><td colspan="4"><a href="Architecture.html" title="Article in CDO Model Repository Documentation">Understanding the Architecture of a Repository</a></td></tr> -<tr><td></td><td>1 </td><td colspan="3"><a href="Architecture.html#OSGi" title="Chapter in CDO Model Repository Documentation">OSGi</a></td></tr> -<tr><td></td><td>2 </td><td colspan="3"><a href="Architecture.html#Core" title="Chapter in CDO Model Repository Documentation">CDO Server Core</a></td></tr> -<tr><td></td><td>3 </td><td colspan="3"><a href="Architecture.html#Store" title="Chapter in CDO Model Repository Documentation">CDO Store</a></td></tr> -<tr><td></td><td>4 </td><td colspan="3"><a href="Architecture.html#Protocol" title="Chapter in CDO Model Repository Documentation">Protocol</a></td></tr> -<tr><td></td><td>5 </td><td colspan="3"><a href="Architecture.html#OCL" title="Chapter in CDO Model Repository Documentation">OCL</a></td></tr> -<tr><td></td><td>6 </td><td colspan="3"><a href="Architecture.html#Net4j" title="Chapter in CDO Model Repository Documentation">Net4j Core</a></td></tr> -<tr><td></td><td>7 </td><td colspan="3"><a href="Architecture.html#Transport" title="Chapter in CDO Model Repository Documentation">Transport</a></td></tr> -</table> -</p> - - -<p align="right"> -<a href="../client/ViewProviders.html" title="Backward to View Providers"><img src="../../../images/backward.png" border="0"></a> <a href="Architecture.html" title="Forward to Understanding the Architecture of a Repository"><img src="../../../images/forward.png" border="0"></a></p> -<HR> -<i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i> -</BODY> -</HTML> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+
+<HEAD>
+<TITLE>Dealing with Servers (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="Dealing with Servers (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></div> -->
+
+<table border="0">
+ <tr>
+ <td width="100%"><h1>Dealing with Servers</h1></td>
+ <td align="right" valign="middle" nowrap><a href="../client/ViewProviders.html" title="Backward to View Providers"><img src="../../../images/backward.png" border="0"></a> <a href="Architecture.html" title="Forward to Understanding the Architecture of a Repository"><img src="../../../images/forward.png" border="0"></a></td>
+ </tr>
+</table>
+<p>
+<table border="0">
+<tr><td><img src="../../../images/article.gif"> </td><td colspan="4"><a href="Architecture.html" title="Article in CDO Model Repository Documentation">Understanding the Architecture of a Repository</a></td></tr>
+<tr><td></td><td>1 </td><td colspan="3"><a href="Architecture.html#OSGi" title="Chapter in CDO Model Repository Documentation">OSGi</a></td></tr>
+<tr><td></td><td>2 </td><td colspan="3"><a href="Architecture.html#Core" title="Chapter in CDO Model Repository Documentation">CDO Server Core</a></td></tr>
+<tr><td></td><td>3 </td><td colspan="3"><a href="Architecture.html#Store" title="Chapter in CDO Model Repository Documentation">CDO Store</a></td></tr>
+<tr><td></td><td>4 </td><td colspan="3"><a href="Architecture.html#Protocol" title="Chapter in CDO Model Repository Documentation">Protocol</a></td></tr>
+<tr><td></td><td>5 </td><td colspan="3"><a href="Architecture.html#OCL" title="Chapter in CDO Model Repository Documentation">OCL</a></td></tr>
+<tr><td></td><td>6 </td><td colspan="3"><a href="Architecture.html#Net4j" title="Chapter in CDO Model Repository Documentation">Net4j Core</a></td></tr>
+<tr><td></td><td>7 </td><td colspan="3"><a href="Architecture.html#Transport" title="Chapter in CDO Model Repository Documentation">Transport</a></td></tr>
+</table>
+</p>
+
+
+<p align="right">
+<a href="../client/ViewProviders.html" title="Backward to View Providers"><img src="../../../images/backward.png" border="0"></a> <a href="Architecture.html" title="Forward to Understanding the Architecture of a Repository"><img src="../../../images/forward.png" border="0"></a></p>
+<HR>
+<i>Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.</i>
+</BODY>
+</HTML>
diff --git a/plugins/org.eclipse.emf.cdo.doc/html/reference/MappingStrategies.html b/plugins/org.eclipse.emf.cdo.doc/html/reference/MappingStrategies.html index 8e75894867..86dae1461d 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/reference/MappingStrategies.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/reference/MappingStrategies.html @@ -179,6 +179,6 @@ function windowTitle() <p align="right"> <a href="StoreFeatures.html" title="Backward to Store Feature Matrix"><img src="../../images/backward.png" border="0"></a> <a href="../online/index.html" title="Forward to Online Docs"><img src="../../images/forward.png" border="0"></a></p> <HR> -<i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i> +<i>Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.</i> </BODY> </HTML> diff --git a/plugins/org.eclipse.emf.cdo.doc/html/reference/StoreFeatures.html b/plugins/org.eclipse.emf.cdo.doc/html/reference/StoreFeatures.html index b6a74a5ae2..8a4519ee2f 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/reference/StoreFeatures.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/reference/StoreFeatures.html @@ -169,6 +169,6 @@ function windowTitle() <p align="right"> <a href="schema/index.html" title="Backward to Extension Point Reference"><img src="../../images/backward.png" border="0"></a> <a href="MappingStrategies.html" title="Forward to DBStore Mapping Strategies"><img src="../../images/forward.png" border="0"></a></p> <HR> -<i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i> +<i>Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.</i> </BODY> </HTML> diff --git a/plugins/org.eclipse.emf.cdo.doc/html/reference/index.html b/plugins/org.eclipse.emf.cdo.doc/html/reference/index.html index 0ea157b9d5..818fe99fc5 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/reference/index.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/reference/index.html @@ -1,44 +1,44 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> -<HTML> - -<HEAD> -<TITLE>Reference (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="Reference (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></div> --> - -<table border="0"> - <tr> - <td width="100%"><h1>Reference</h1></td> - <td align="right" valign="middle" nowrap><a href="../programmers/server/Architecture.html" title="Backward to Understanding the Architecture of a Repository"><img src="../../images/backward.png" border="0"></a> <a href="../../javadoc/overview-summary.html" title="Forward to API Reference"><img src="../../images/forward.png" border="0"></a></td> - </tr> -</table> -<p> -<table border="0"> -<tr><td><img src="../../images/category.gif"> </td><td colspan="3"><a href="../../javadoc/overview-summary.html" title="Category in CDO Model Repository Documentation">API Reference</a></td></tr> -<tr><td><img src="../../images/category.gif"> </td><td colspan="3"><a href="schema/index.html" title="Category in CDO Model Repository Documentation">Extension Point Reference</a></td></tr> -<tr><td><img src="../../images/article.gif"> </td><td colspan="3"><a href="StoreFeatures.html" title="Article in CDO Model Repository Documentation">Store Feature Matrix</a></td></tr> -<tr><td><img src="../../images/article.gif"> </td><td colspan="3"><a href="MappingStrategies.html" title="Article in CDO Model Repository Documentation">DBStore Mapping Strategies</a></td></tr> -</table> -</p> - - -<p align="right"> -<a href="../programmers/server/Architecture.html" title="Backward to Understanding the Architecture of a Repository"><img src="../../images/backward.png" border="0"></a> <a href="../../javadoc/overview-summary.html" title="Forward to API 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> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+
+<HEAD>
+<TITLE>Reference (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="Reference (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></div> -->
+
+<table border="0">
+ <tr>
+ <td width="100%"><h1>Reference</h1></td>
+ <td align="right" valign="middle" nowrap><a href="../programmers/server/Architecture.html" title="Backward to Understanding the Architecture of a Repository"><img src="../../images/backward.png" border="0"></a> <a href="../../javadoc/overview-summary.html" title="Forward to API Reference"><img src="../../images/forward.png" border="0"></a></td>
+ </tr>
+</table>
+<p>
+<table border="0">
+<tr><td><img src="../../images/category.gif"> </td><td colspan="3"><a href="../../javadoc/overview-summary.html" title="Category in CDO Model Repository Documentation">API Reference</a></td></tr>
+<tr><td><img src="../../images/category.gif"> </td><td colspan="3"><a href="schema/index.html" title="Category in CDO Model Repository Documentation">Extension Point Reference</a></td></tr>
+<tr><td><img src="../../images/article.gif"> </td><td colspan="3"><a href="StoreFeatures.html" title="Article in CDO Model Repository Documentation">Store Feature Matrix</a></td></tr>
+<tr><td><img src="../../images/article.gif"> </td><td colspan="3"><a href="MappingStrategies.html" title="Article in CDO Model Repository Documentation">DBStore Mapping Strategies</a></td></tr>
+</table>
+</p>
+
+
+<p align="right">
+<a href="../programmers/server/Architecture.html" title="Backward to Understanding the Architecture of a Repository"><img src="../../images/backward.png" border="0"></a> <a href="../../javadoc/overview-summary.html" title="Forward to API Reference"><img src="../../images/forward.png" border="0"></a></p>
+<HR>
+<i>Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.</i>
+</BODY>
+</HTML>
diff --git a/plugins/org.eclipse.emf.cdo.doc/html/reference/schema/index.html b/plugins/org.eclipse.emf.cdo.doc/html/reference/schema/index.html index 48fd55591d..5f2d8f75f5 100644 --- a/plugins/org.eclipse.emf.cdo.doc/html/reference/schema/index.html +++ b/plugins/org.eclipse.emf.cdo.doc/html/reference/schema/index.html @@ -1,40 +1,40 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> -<HTML> - -<HEAD> -<TITLE>Extension Point Reference (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="Extension Point Reference (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">Reference</a></div> --> - -<table border="0"> - <tr> - <td width="100%"><h1>Extension Point Reference</h1></td> - <td align="right" valign="middle" nowrap><a href="../../../javadoc/overview-summary.html" title="Backward to API Reference"><img src="../../../images/backward.png" border="0"></a> <a href="../StoreFeatures.html" title="Forward to Store Feature Matrix"><img src="../../../images/forward.png" border="0"></a></td> - </tr> -</table> -<p> -<table border="0"> -</table> -</p> - - -<p align="right"> -<a href="../../../javadoc/overview-summary.html" title="Backward to API Reference"><img src="../../../images/backward.png" border="0"></a> <a href="../StoreFeatures.html" title="Forward to Store Feature Matrix"><img src="../../../images/forward.png" border="0"></a></p> -<HR> -<i>Copyright (c) 2004 - 2011 Eike Stepper (Berlin, Germany) and others.</i> -</BODY> -</HTML> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+
+<HEAD>
+<TITLE>Extension Point Reference (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="Extension Point Reference (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">Reference</a></div> -->
+
+<table border="0">
+ <tr>
+ <td width="100%"><h1>Extension Point Reference</h1></td>
+ <td align="right" valign="middle" nowrap><a href="../../../javadoc/overview-summary.html" title="Backward to API Reference"><img src="../../../images/backward.png" border="0"></a> <a href="../StoreFeatures.html" title="Forward to Store Feature Matrix"><img src="../../../images/forward.png" border="0"></a></td>
+ </tr>
+</table>
+<p>
+<table border="0">
+</table>
+</p>
+
+
+<p align="right">
+<a href="../../../javadoc/overview-summary.html" title="Backward to API Reference"><img src="../../../images/backward.png" border="0"></a> <a href="../StoreFeatures.html" title="Forward to Store Feature Matrix"><img src="../../../images/forward.png" border="0"></a></p>
+<HR>
+<i>Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.</i>
+</BODY>
+</HTML>
|