diff options
Diffstat (limited to 'plugins/org.eclipse.emf.cdo.doc/src/org/eclipse')
15 files changed, 617 insertions, 617 deletions
diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Legal.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Legal.java index f71b343836..d363a62a95 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Legal.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Legal.java @@ -1,21 +1,21 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-package org.eclipse.emf.cdo.doc;
-
-/**
- * Legal
- *
- * @external about.html
- * @number 666
- */
-public class Legal
-{
-}
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ +package org.eclipse.emf.cdo.doc; + +/** + * Legal + * + * @external about.html + * @number 666 + */ +public class Legal +{ +} diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Overview.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Overview.java index 26c91aeeeb..2c2b1c6f16 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Overview.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/Overview.java @@ -1,152 +1,152 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-package org.eclipse.emf.cdo.doc;
-
-/**
- * Overview
- * <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: {@img cdo-overview.png}
- *
- * @default
- * @author Eike Stepper
- */
-public class Overview
-{
- /**
- * Functionality
- * <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>
- */
- public class Functionality
- {
- }
-
- /**
- * Architecture
- * <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.
- */
- public class Architecture
- {
- /**
- * Client Architecture
- * <p>
- * {@link org.eclipse.emf.cdo.doc.programmers.client.Architecture !!inline!!}
- *
- * @see org.eclipse.emf.cdo.doc.programmers.client.Architecture
- */
- public class Client
- {
- }
-
- /**
- * Repository Architecture
- * <p>
- * {@link org.eclipse.emf.cdo.doc.programmers.server.Architecture !!inline!!}
- *
- * @see org.eclipse.emf.cdo.doc.programmers.server.Architecture
- */
- public class Repository
- {
- }
- }
-}
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ +package org.eclipse.emf.cdo.doc; + +/** + * Overview + * <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: {@img cdo-overview.png} + * + * @default + * @author Eike Stepper + */ +public class Overview +{ + /** + * Functionality + * <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> + */ + public class Functionality + { + } + + /** + * Architecture + * <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. + */ + public class Architecture + { + /** + * Client Architecture + * <p> + * {@link org.eclipse.emf.cdo.doc.programmers.client.Architecture !!inline!!} + * + * @see org.eclipse.emf.cdo.doc.programmers.client.Architecture + */ + public class Client + { + } + + /** + * Repository Architecture + * <p> + * {@link org.eclipse.emf.cdo.doc.programmers.server.Architecture !!inline!!} + * + * @see org.eclipse.emf.cdo.doc.programmers.server.Architecture + */ + public class Repository + { + } + } +} diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/online/Homepage.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/online/Homepage.java index a7944cd3dd..d848f78ad7 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/online/Homepage.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/online/Homepage.java @@ -1,21 +1,21 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-package org.eclipse.emf.cdo.doc.online;
-
-/**
- * Homepage
- *
- * @external http://www.eclipse.org/cdo
- * @number 1
- */
-public class Homepage
-{
-}
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ +package org.eclipse.emf.cdo.doc.online; + +/** + * Homepage + * + * @external http://www.eclipse.org/cdo + * @number 1 + */ +public class Homepage +{ +} diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/online/Wiki.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/online/Wiki.java index 90ba763ec3..bdeb871de6 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/online/Wiki.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/online/Wiki.java @@ -1,21 +1,21 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-package org.eclipse.emf.cdo.doc.online;
-
-/**
- * Wiki
- *
- * @external http://wiki.eclipse.org/CDO
- * @number 2
- */
-public class Wiki
-{
-}
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ +package org.eclipse.emf.cdo.doc.online; + +/** + * Wiki + * + * @external http://wiki.eclipse.org/CDO + * @number 2 + */ +public class Wiki +{ +} diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/online/package-info.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/online/package-info.java index f3114c270f..07f0fd9ce4 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/online/package-info.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/online/package-info.java @@ -1,18 +1,18 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-
-/**
- * Online Docs
- *
- * @number 555
- */
-package org.eclipse.emf.cdo.doc.online;
-
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ + +/** + * Online Docs + * + * @number 555 + */ +package org.eclipse.emf.cdo.doc.online; + diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/client/Architecture.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/client/Architecture.java index 872ccd147d..9d3f4b9f6f 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/client/Architecture.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/client/Architecture.java @@ -1,80 +1,80 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-package org.eclipse.emf.cdo.doc.programmers.client;
-
-import org.eclipse.emf.ecore.EObject;
-
-/**
- * Understanding the Architecture of a Client Application
- * <p>
- * The architecture of a CDO application is characterized by its mandatory dependency on EMF, the Eclipse Modeling
- * Framework. Most of the time an application interacts with the object graph of the model through standard EMF APIs
- * because CDO model graph objects are {@link EObject EObjects}. While CDO's basic functionality integrates nicely and
- * transparently with EMF's extension mechansims some of the more advanced functions may require to add direct
- * dependendcies on CDO to your application code.
- * <p>
- * The following diagram illustrates the major building blocks of a CDO application: {@img application-architecture.png}
- *
- * @author Eike Stepper
- */
-public class Architecture
-{
- /**
- * OSGi
- * <p>
- * The <i>Open Services Gateway Initiative</i> (OSGi)...
- */
- public class OSGi
- {
- }
-
- /**
- * EMF
- */
- public class EMF
- {
- }
-
- /**
- * CDO Client
- */
- public class Client
- {
- }
-
- /**
- * Net4j Core
- */
- public class Net4j
- {
- }
-
- /**
- * Models
- */
- public class Models
- {
- }
-
- /**
- * Protocol
- */
- public class Protocol
- {
- }
-
- /**
- * Transport
- */
- public class Transport
- {
- }
-}
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ +package org.eclipse.emf.cdo.doc.programmers.client; + +import org.eclipse.emf.ecore.EObject; + +/** + * Understanding the Architecture of a Client Application + * <p> + * The architecture of a CDO application is characterized by its mandatory dependency on EMF, the Eclipse Modeling + * Framework. Most of the time an application interacts with the object graph of the model through standard EMF APIs + * because CDO model graph objects are {@link EObject EObjects}. While CDO's basic functionality integrates nicely and + * transparently with EMF's extension mechansims some of the more advanced functions may require to add direct + * dependendcies on CDO to your application code. + * <p> + * The following diagram illustrates the major building blocks of a CDO application: {@img application-architecture.png} + * + * @author Eike Stepper + */ +public class Architecture +{ + /** + * OSGi + * <p> + * The <i>Open Services Gateway Initiative</i> (OSGi)... + */ + public class OSGi + { + } + + /** + * EMF + */ + public class EMF + { + } + + /** + * CDO Client + */ + public class Client + { + } + + /** + * Net4j Core + */ + public class Net4j + { + } + + /** + * Models + */ + public class Models + { + } + + /** + * Protocol + */ + public class Protocol + { + } + + /** + * Transport + */ + public class Transport + { + } +} diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/client/ViewProviders.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/client/ViewProviders.java index 745235b4af..68d73b7346 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/client/ViewProviders.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/client/ViewProviders.java @@ -1,146 +1,146 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Victor Roldan Betancort - initial API and implementation
- */
-package org.eclipse.emf.cdo.doc.programmers.client;
-
-import org.eclipse.emf.cdo.eresource.CDOResourceFactory;
-import org.eclipse.emf.cdo.net4j.CDONet4jSessionConfiguration;
-import org.eclipse.emf.cdo.net4j.CDONet4jUtil;
-import org.eclipse.emf.cdo.session.CDOSession;
-import org.eclipse.emf.cdo.transaction.CDOTransaction;
-import org.eclipse.emf.cdo.view.AbstractCDOViewProvider;
-import org.eclipse.emf.cdo.view.CDOView;
-import org.eclipse.emf.cdo.view.CDOViewProvider;
-import org.eclipse.emf.cdo.view.CDOViewProviderRegistry;
-
-import org.eclipse.net4j.Net4jUtil;
-import org.eclipse.net4j.connector.IConnector;
-import org.eclipse.net4j.tcp.TCPUtil;
-import org.eclipse.net4j.util.container.IManagedContainer;
-import org.eclipse.net4j.util.container.ManagedContainer;
-
-import org.eclipse.emf.common.util.URI;
-import org.eclipse.emf.ecore.resource.Resource;
-import org.eclipse.emf.ecore.resource.ResourceSet;
-
-/**
- * View Providers
- * <p>
- * A {@link CDOViewProvider view provider} allows clients to inject custom logic into the {@link CDOResourceFactory
- * resource factory} mechansim, capable of handling the whole {@link CDOSession session} and {@link CDOView view}
- * instantiation process. This permits to obtain {@link Resource resources} through the {@link ResourceSet resource set}
- * API transparently, without any prior CDO client API code. The view provider automatically kicks in the middle of the
- * {@link ResourceSet#getResource(org.eclipse.emf.common.util.URI, boolean) ResourceSet.getResource()} call, forgetting
- * about the whole openning session / openning transaction process, which happens behind the scenes.
- * <p>
- * This is quite useful when integrating CDO with EMF-based frameworks and tools that are not prepared for a CDO
- * scenario themselves.
- * <p>
- * <b>Table of Contents</b> {@toc}
- *
- * @author Victor Roldan Betancort
- */
-public class ViewProviders
-{
- /**
- * Implementing a View Provider
- * <p>
- * Clients should implement the {@link CDOViewProvider} interface, or sub class the {@link AbstractCDOViewProvider}
- * class, which provides common functionality.
- * <p>
- * The example below shows a simple implementation that opens a <b>new</b> {@link CDOSession session} to a local
- * server and a <b>new</b> {@link CDOTransaction transaction} on that session.
- * <p>
- * {@link #example() ExampleViewProvider.java}
- */
- public class ProviderImplementation
- {
- /**
- * @snippet
- * @callout The example provider catches all URIs with shape "cdo.local:<repoName>".
- * @callout Register the provider with {@link CDOViewProviderRegistry}.
- */
- public void example()
- {
- /* callout */new AbstractCDOViewProvider("cdo\\.local:.*", 100)
- {
- private IManagedContainer container;
-
- /* callout */public CDOView getView(URI uri, ResourceSet resourceSet)
- {
- if (container == null)
- {
- container = new ManagedContainer();
- Net4jUtil.prepareContainer(container);
- TCPUtil.prepareContainer(container);
- container.activate();
- }
-
- int startIndex = uri.toString().indexOf(':');
- String repoName = uri.toString().substring(startIndex);
-
- IConnector connector = (IConnector)container.getElement("org.eclipse.net4j.connectors", "tcp", "localhost");
-
- CDONet4jSessionConfiguration config = CDONet4jUtil.createNet4jSessionConfiguration();
- config.setConnector(connector);
- config.setRepositoryName(repoName);
-
- CDOSession session = config.openNet4jSession();
- return session.openTransaction();
- }
- };
- }
- }
-
- /**
- * Contributing View Providers Programmatically
- * <p>
- * A client's view provider implementation can be contributed programmatically to the {@link CDOViewProviderRegistry},
- * as the following example suggests:
- * <p>
- * {@link #snippet2() ProviderContribution.java}
- */
- public class ContributeProviderProgrammatically
- {
- /**
- * @snippet
- * @callout Get the target {@link CDOViewProvider} implementation.
- * @callout Add the provider instance to {@link CDOViewProviderRegistry}.
- */
- @SuppressWarnings("restriction")
- public void snippet2()
- {
- // Instantiate your view provider
- CDOViewProvider viewProvider = /* callout */org.eclipse.emf.internal.cdo.view.PluginContainerViewProvider.INSTANCE;
-
- // Add the instance to the registry
- /* callout */CDOViewProviderRegistry.INSTANCE.addViewProvider(viewProvider);
- }
- }
-
- /**
- * Contributing View Providers Using Extension Points
- * <p>
- * A specific {@link CDOViewProvider} implementation can also be contributed using the
- * <code>org.eclipse.emf.cdo.viewProviders</code> extension point. Clients specify:
- * <p>
- * <ul>
- * <li>A mandatory <b><code>class</code></b> implementing the {@link CDOViewProvider} interface.
- * <li>A mandatory <b>regular expression</b> string indicating the shape of {@link org.eclipse.emf.common.util.URI
- * URIs} that should match with the contributed provider.
- * <li>An optional <b><code>priority</code></b> integer value, to indicate preference over other implementations
- * matching the same regular expression. A higher value indicates a higher priority, {@link Integer#MAX_VALUE} being
- * the maximum priority value and {@link Integer#MIN_VALUE} the minimum.
- * </ul>
- */
- public class ContributeProviderUsingExtensionPoint
- {
- }
-}
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Victor Roldan Betancort - initial API and implementation + */ +package org.eclipse.emf.cdo.doc.programmers.client; + +import org.eclipse.emf.cdo.eresource.CDOResourceFactory; +import org.eclipse.emf.cdo.net4j.CDONet4jSessionConfiguration; +import org.eclipse.emf.cdo.net4j.CDONet4jUtil; +import org.eclipse.emf.cdo.session.CDOSession; +import org.eclipse.emf.cdo.transaction.CDOTransaction; +import org.eclipse.emf.cdo.view.AbstractCDOViewProvider; +import org.eclipse.emf.cdo.view.CDOView; +import org.eclipse.emf.cdo.view.CDOViewProvider; +import org.eclipse.emf.cdo.view.CDOViewProviderRegistry; + +import org.eclipse.net4j.Net4jUtil; +import org.eclipse.net4j.connector.IConnector; +import org.eclipse.net4j.tcp.TCPUtil; +import org.eclipse.net4j.util.container.IManagedContainer; +import org.eclipse.net4j.util.container.ManagedContainer; + +import org.eclipse.emf.common.util.URI; +import org.eclipse.emf.ecore.resource.Resource; +import org.eclipse.emf.ecore.resource.ResourceSet; + +/** + * View Providers + * <p> + * A {@link CDOViewProvider view provider} allows clients to inject custom logic into the {@link CDOResourceFactory + * resource factory} mechansim, capable of handling the whole {@link CDOSession session} and {@link CDOView view} + * instantiation process. This permits to obtain {@link Resource resources} through the {@link ResourceSet resource set} + * API transparently, without any prior CDO client API code. The view provider automatically kicks in the middle of the + * {@link ResourceSet#getResource(org.eclipse.emf.common.util.URI, boolean) ResourceSet.getResource()} call, forgetting + * about the whole openning session / openning transaction process, which happens behind the scenes. + * <p> + * This is quite useful when integrating CDO with EMF-based frameworks and tools that are not prepared for a CDO + * scenario themselves. + * <p> + * <b>Table of Contents</b> {@toc} + * + * @author Victor Roldan Betancort + */ +public class ViewProviders +{ + /** + * Implementing a View Provider + * <p> + * Clients should implement the {@link CDOViewProvider} interface, or sub class the {@link AbstractCDOViewProvider} + * class, which provides common functionality. + * <p> + * The example below shows a simple implementation that opens a <b>new</b> {@link CDOSession session} to a local + * server and a <b>new</b> {@link CDOTransaction transaction} on that session. + * <p> + * {@link #example() ExampleViewProvider.java} + */ + public class ProviderImplementation + { + /** + * @snippet + * @callout The example provider catches all URIs with shape "cdo.local:<repoName>". + * @callout Register the provider with {@link CDOViewProviderRegistry}. + */ + public void example() + { + /* callout */new AbstractCDOViewProvider("cdo\\.local:.*", 100) + { + private IManagedContainer container; + + /* callout */public CDOView getView(URI uri, ResourceSet resourceSet) + { + if (container == null) + { + container = new ManagedContainer(); + Net4jUtil.prepareContainer(container); + TCPUtil.prepareContainer(container); + container.activate(); + } + + int startIndex = uri.toString().indexOf(':'); + String repoName = uri.toString().substring(startIndex); + + IConnector connector = (IConnector)container.getElement("org.eclipse.net4j.connectors", "tcp", "localhost"); + + CDONet4jSessionConfiguration config = CDONet4jUtil.createNet4jSessionConfiguration(); + config.setConnector(connector); + config.setRepositoryName(repoName); + + CDOSession session = config.openNet4jSession(); + return session.openTransaction(); + } + }; + } + } + + /** + * Contributing View Providers Programmatically + * <p> + * A client's view provider implementation can be contributed programmatically to the {@link CDOViewProviderRegistry}, + * as the following example suggests: + * <p> + * {@link #snippet2() ProviderContribution.java} + */ + public class ContributeProviderProgrammatically + { + /** + * @snippet + * @callout Get the target {@link CDOViewProvider} implementation. + * @callout Add the provider instance to {@link CDOViewProviderRegistry}. + */ + @SuppressWarnings("restriction") + public void snippet2() + { + // Instantiate your view provider + CDOViewProvider viewProvider = /* callout */org.eclipse.emf.internal.cdo.view.PluginContainerViewProvider.INSTANCE; + + // Add the instance to the registry + /* callout */CDOViewProviderRegistry.INSTANCE.addViewProvider(viewProvider); + } + } + + /** + * Contributing View Providers Using Extension Points + * <p> + * A specific {@link CDOViewProvider} implementation can also be contributed using the + * <code>org.eclipse.emf.cdo.viewProviders</code> extension point. Clients specify: + * <p> + * <ul> + * <li>A mandatory <b><code>class</code></b> implementing the {@link CDOViewProvider} interface. + * <li>A mandatory <b>regular expression</b> string indicating the shape of {@link org.eclipse.emf.common.util.URI + * URIs} that should match with the contributed provider. + * <li>An optional <b><code>priority</code></b> integer value, to indicate preference over other implementations + * matching the same regular expression. A higher value indicates a higher priority, {@link Integer#MAX_VALUE} being + * the maximum priority value and {@link Integer#MIN_VALUE} the minimum. + * </ul> + */ + public class ContributeProviderUsingExtensionPoint + { + } +} diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/client/package-info.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/client/package-info.java index 4fd2ce5d3c..e2f26fe04a 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/client/package-info.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/client/package-info.java @@ -1,18 +1,18 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-
-/**
- * Developing Client Applications
- *
- * @number 1
- */
-package org.eclipse.emf.cdo.doc.programmers.client;
-
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ + +/** + * Developing Client Applications + * + * @number 1 + */ +package org.eclipse.emf.cdo.doc.programmers.client; + diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/package-info.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/package-info.java index 9a4822903c..11b1bff39a 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/package-info.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/package-info.java @@ -1,18 +1,18 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-
-/**
- * Programmer's Guide
- *
- * @number 1
- */
-package org.eclipse.emf.cdo.doc.programmers;
-
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ + +/** + * Programmer's Guide + * + * @number 1 + */ +package org.eclipse.emf.cdo.doc.programmers; + diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/server/package-info.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/server/package-info.java index bc4b886e3c..451784b12a 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/server/package-info.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/programmers/server/package-info.java @@ -1,18 +1,18 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-
-/**
- * Dealing with Servers
- *
- * @number 1
- */
-package org.eclipse.emf.cdo.doc.programmers.server;
-
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ + +/** + * Dealing with Servers + * + * @number 1 + */ +package org.eclipse.emf.cdo.doc.programmers.server; + diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/MappingStrategies.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/MappingStrategies.java index 9c52739361..6cd565babf 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/MappingStrategies.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/MappingStrategies.java @@ -1,22 +1,22 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-package org.eclipse.emf.cdo.doc.reference;
-
-/**
- * DBStore Mapping Strategies
- * <p>
- * {@excel ../../../../../../../Tables.xlsx#MappingStrategies}
- *
- * @number 201
- */
-public class MappingStrategies
-{
-}
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ +package org.eclipse.emf.cdo.doc.reference; + +/** + * DBStore Mapping Strategies + * <p> + * {@excel ../../../../../../../Tables.xlsx#MappingStrategies} + * + * @number 201 + */ +public class MappingStrategies +{ +} diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/StoreFeatures.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/StoreFeatures.java index 12907b2bb9..bac80509c3 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/StoreFeatures.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/StoreFeatures.java @@ -1,22 +1,22 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-package org.eclipse.emf.cdo.doc.reference;
-
-/**
- * Store Feature Matrix
- * <p>
- * {@excel ../../../../../../../Tables.xlsx}
- *
- * @number 200
- */
-public class StoreFeatures
-{
-}
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ +package org.eclipse.emf.cdo.doc.reference; + +/** + * Store Feature Matrix + * <p> + * {@excel ../../../../../../../Tables.xlsx} + * + * @number 200 + */ +public class StoreFeatures +{ +} diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/api/package-info.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/api/package-info.java index 9f625fa3fb..dfcf722d19 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/api/package-info.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/api/package-info.java @@ -1,21 +1,21 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-
-/**
- * API Reference
- *
- * @number 1
- */
-package org.eclipse.emf.cdo.doc.reference.api;
-
-class Javadoc
-{
-}
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ + +/** + * API Reference + * + * @number 1 + */ +package org.eclipse.emf.cdo.doc.reference.api; + +class Javadoc +{ +} diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/package-info.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/package-info.java index 07fc482dbd..7d2a130776 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/package-info.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/package-info.java @@ -1,18 +1,18 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-
-/**
- * Reference
- *
- * @number 444
- */
-package org.eclipse.emf.cdo.doc.reference;
-
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ + +/** + * Reference + * + * @number 444 + */ +package org.eclipse.emf.cdo.doc.reference; + diff --git a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/schema/package-info.java b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/schema/package-info.java index f90b2c8724..d325a87897 100644 --- a/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/schema/package-info.java +++ b/plugins/org.eclipse.emf.cdo.doc/src/org/eclipse/emf/cdo/doc/reference/schema/package-info.java @@ -1,21 +1,21 @@ -/*
- * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * Eike Stepper - initial API and implementation
- */
-
-/**
- * Extension Point Reference
- *
- * @number 2
- */
-package org.eclipse.emf.cdo.doc.reference.schema;
-
-class Schemadoc
-{
-}
+/* + * Copyright (c) 2004 - 2012 Eike Stepper (Berlin, Germany) and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Eike Stepper - initial API and implementation + */ + +/** + * Extension Point Reference + * + * @number 2 + */ +package org.eclipse.emf.cdo.doc.reference.schema; + +class Schemadoc +{ +} |