Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "CDO/Preparing EMF Models"

< CDO
(Use the CDO Model Importer)
(7 intermediate revisions by 2 users not shown)
Line 88: Line 88:
  
 
[[Image:Model1Project.png]]
 
[[Image:Model1Project.png]]
<br>
 
  
 +
<br>
 
==Use the CDO Model Importer==
 
==Use the CDO Model Importer==
  
The easiest way to create a CDO enabled GenModel is to use the CDO Migrator utility that is shipped with the CDO SDK. It includes a special Ecore Model Importer that adjusts all the GenModel properties needed to generated CDO native models. Right-click the Ecore model file and select the ''EMF Model'' New Wizard:
+
The easiest way to create a CDO enabled GenModel is to use the CDO Migrator utility that is shipped with the CDO SDK. It includes a special Ecore Model Importer that adjusts all the GenModel properties needed to generated CDO native models. Right-click the Ecore model file and select ''New'' and ''Other...'' and choose the ''EMF Generator Model'' New Wizard:
 +
 
 +
[[Image:Migrator0.png]]
  
  
Line 120: Line 122:
  
 
[[Image:Migrator5.png]]
 
[[Image:Migrator5.png]]
 +
 +
 +
Proceed with [[#Generate The Model|Generate The Model]]
 +
 
<br>
 
<br>
  
==Use the CDO Migrator==
+
==Use the CDO Model Migrator==
  
 
If you don't want to use the [[#Use the CDO Model Importer|CDO Model Importer]] to automatically let a proper GenModel be created for you it is still rather easy to migrate an existing GenModel with the CDO Migrator:
 
If you don't want to use the [[#Use the CDO Model Importer|CDO Model Importer]] to automatically let a proper GenModel be created for you it is still rather easy to migrate an existing GenModel with the CDO Migrator:
Line 134: Line 140:
  
 
[[Image:Migrator7.png]]
 
[[Image:Migrator7.png]]
<br>
 
  
 +
 +
Proceed with [[#Generate The Model|Generate The Model]]
 +
 +
<br>
 
==Migrate your GenModel Manually==
 
==Migrate your GenModel Manually==
  
Line 215: Line 224:
 
</genmodel:GenModel>
 
</genmodel:GenModel>
 
</pre>
 
</pre>
<br>
 
 
===Create the Marker File===
 
 
At runtime the CDO client needs to determine whether a given EPackage (your model) has been generated for CDO or not. Create a file <code>META-INF/CDO.MF</code> with arbitrary or no content to signal that all models in your bundle are CDO native models.
 
 
'''Important:''' Formerly you had to declaratively specify this information by contributing to the <tt>org.eclipse.emf.cdo.persistent_package</tt> extension point. This method is now deprecated! Only the existence of the <code>META-INF/CDO.MF</code> file is checked at runtime!
 
 
<br>
 
<br>
  
Line 236: Line 238:
  
 
[[Image:GeneratorResults.png]]
 
[[Image:GeneratorResults.png]]
 +
 +
 +
'''Important note:''' If you want to modify the behaviour of generated getters and setters (or have already done so in existing models) you might want to try ''dynamic feature delegation'' (introduced in EMF 2.5). With this pattern, the reflective methods like eGet still call your generated method like getX() and then that calls the dymamic reflective method like eDynamicGet.  It effectively produces the same behavior as "Refective" delegating but does so by delegating through your generated accessors allowing you to specialize those as you could when you used "None"...
  
 
<br>
 
<br>
 
----
 
----
 
Wikis: [[CDO]] | [[Net4j]] | [[EMF]] | [[Eclipse]]
 
Wikis: [[CDO]] | [[Net4j]] | [[EMF]] | [[Eclipse]]

Revision as of 01:57, 29 June 2011


Create an Ecore Model

There's really not much to say about this step. The .ecore file for CDO models is the same as for pure EMF models. Use the Empty EMF Project New Wizard to create an initial project for your model:


EmptyEMFProject.png


Create an ordinary Ecore model file in the models folder. The model1 example model in the usual Ecore model editor looks like follows:


Model1Ecore.png


You can download this Ecore model from here. Its XML form is:

<?xml version="1.0" encoding="UTF-8"?>
<ecore:EPackage xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" name="model1"
    nsURI="http://www.eclipse.org/emf/CDO/tests/model1/1.0.0" nsPrefix="model1">
  <eClassifiers xsi:type="ecore:EClass" name="Address">
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="name" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EString"/>
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="street" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EString"/>
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="city" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EString"/>
  </eClassifiers>
  <eClassifiers xsi:type="ecore:EClass" name="Company" eSuperTypes="#//Address">
    <eStructuralFeatures xsi:type="ecore:EReference" name="categories" upperBound="-1"
        eType="#//Category" containment="true"/>
    <eStructuralFeatures xsi:type="ecore:EReference" name="suppliers" upperBound="-1"
        eType="#//Supplier" containment="true"/>
    <eStructuralFeatures xsi:type="ecore:EReference" name="customers" upperBound="-1"
        eType="#//Customer" containment="true"/>
    <eStructuralFeatures xsi:type="ecore:EReference" name="purchaseOrders" upperBound="-1"
        eType="#//PurchaseOrder" containment="true"/>
    <eStructuralFeatures xsi:type="ecore:EReference" name="salesOrders" upperBound="-1"
        eType="#//SalesOrder" containment="true"/>
  </eClassifiers>
  <eClassifiers xsi:type="ecore:EClass" name="Supplier" eSuperTypes="#//Address">
    <eStructuralFeatures xsi:type="ecore:EReference" name="purchaseOrders" upperBound="-1"
        eType="#//PurchaseOrder" eOpposite="#//PurchaseOrder/supplier"/>
  </eClassifiers>
  <eClassifiers xsi:type="ecore:EClass" name="Customer" eSuperTypes="#//Address">
    <eStructuralFeatures xsi:type="ecore:EReference" name="salesOrders" unique="false"
        upperBound="-1" eType="#//SalesOrder" eOpposite="#//SalesOrder/customer"/>
  </eClassifiers>
  <eClassifiers xsi:type="ecore:EClass" name="Order">
    <eStructuralFeatures xsi:type="ecore:EReference" name="orderDetails" upperBound="-1"
        eType="#//OrderDetail" containment="true" eOpposite="#//OrderDetail/order"/>
  </eClassifiers>
  <eClassifiers xsi:type="ecore:EClass" name="OrderDetail">
    <eStructuralFeatures xsi:type="ecore:EReference" name="order" lowerBound="1" eType="#//Order"
        eOpposite="#//Order/orderDetails"/>
    <eStructuralFeatures xsi:type="ecore:EReference" name="product" eType="#//Product"
        eOpposite="#//Product/orderDetails"/>
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="price" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EFloat"/>
  </eClassifiers>
  <eClassifiers xsi:type="ecore:EClass" name="PurchaseOrder" eSuperTypes="#//Order">
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="date" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDate"/>
    <eStructuralFeatures xsi:type="ecore:EReference" name="supplier" lowerBound="1"
        eType="#//Supplier" eOpposite="#//Supplier/purchaseOrders"/>
  </eClassifiers>
  <eClassifiers xsi:type="ecore:EClass" name="SalesOrder" eSuperTypes="#//Order">
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="id" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EInt"/>
    <eStructuralFeatures xsi:type="ecore:EReference" name="customer" lowerBound="1"
        eType="#//Customer" eOpposite="#//Customer/salesOrders"/>
  </eClassifiers>
  <eClassifiers xsi:type="ecore:EClass" name="Category">
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="name" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EString"/>
    <eStructuralFeatures xsi:type="ecore:EReference" name="categories" upperBound="-1"
        eType="#//Category" containment="true"/>
    <eStructuralFeatures xsi:type="ecore:EReference" name="products" upperBound="-1"
        eType="#//Product" containment="true"/>
  </eClassifiers>
  <eClassifiers xsi:type="ecore:EClass" name="Product">
    <eStructuralFeatures xsi:type="ecore:EAttribute" name="name" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EString"/>
    <eStructuralFeatures xsi:type="ecore:EReference" name="orderDetails" upperBound="-1"
        eType="#//OrderDetail" eOpposite="#//OrderDetail/product"/>
  </eClassifiers>
</ecore:EPackage>

The model project should look similar to this, now:


Model1Project.png


Use the CDO Model Importer

The easiest way to create a CDO enabled GenModel is to use the CDO Migrator utility that is shipped with the CDO SDK. It includes a special Ecore Model Importer that adjusts all the GenModel properties needed to generated CDO native models. Right-click the Ecore model file and select New and Other... and choose the EMF Generator Model New Wizard:

Migrator0.png


Migrator1.png


On the next page, the Select a Model Importer page, select the Ecore model (CDO native) importer:


Migrator2.png


On the next page, the Ecore Import page, click the Load button:


Migrator3.png


On the next page, the Package Selection page, adjust the settings depending on your model and its referenced models:


Migrator4.png


After clicking the Finish button your model project should look similar to this (please note that the CDO marker file META-INF/CDO.MF has also been created by the importer):


Migrator5.png


Proceed with Generate The Model


Use the CDO Model Migrator

If you don't want to use the CDO Model Importer to automatically let a proper GenModel be created for you it is still rather easy to migrate an existing GenModel with the CDO Migrator:


Migrator6.png


In case the generator model was successfully migrated to CDO the following dialog box will appear:


Migrator7.png


Proceed with Generate The Model


Migrate your GenModel Manually

If you don't want to use the CDO Model Importer to automatically let a proper GenModel be created for you it is still rather easy to migrate an existing GenModel by hand.

Modify an Existing GenModel

The EMF generator model for your Ecore model is much like a usual GenModel except for the following four differences:

  • The Feature Delegation property must be set to Reflective
  • The Model Plug-in Variables property should be set to CDO=org.eclipse.emf.cdo
  • The Root Extends Class property must be set to org.eclipse.emf.internal.cdo.CDOObjectImpl
  • The Root Extends Interface property can be set to org.eclipse.emf.cdo.CDOObject


GenModel.png


Note that you do not need to generate an editor if you want to use your model with the CDO User Interface. A dedicated model editor is only needed if you plan to use your model with normal XML based files as well. Even in this scenario it could be simpler to use the EMF Reflective Model Editor though.

You can download this generator model from here. Its XML form is:

<?xml version="1.0" encoding="UTF-8"?>
<genmodel:GenModel xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore"
    xmlns:genmodel="http://www.eclipse.org/emf/2002/GenModel" modelDirectory="/org.eclipse.emf.cdo.tests.model1/src"
    modelPluginID="org.eclipse.emf.cdo.tests.model1" modelName="Model1" rootExtendsInterface="org.eclipse.emf.cdo.CDOObject"
    rootExtendsClass="org.eclipse.emf.internal.cdo.CDOObjectImpl" reflectiveDelegation="true"
    testsDirectory="" importerID="org.eclipse.emf.importer.ecore" featureDelegation="Reflective"
    complianceLevel="5.0">
  <foreignModel>model1.ecore</foreignModel>
  <modelPluginVariables>CDO=org.eclipse.emf.cdo</modelPluginVariables>
  <genPackages prefix="Model1" basePackage="org.eclipse.emf.cdo.tests" disposableProviderFactory="true"
      ecorePackage="model1.ecore#/">
    <genClasses ecoreClass="model1.ecore#//Address">
      <genFeatures createChild="false" ecoreFeature="ecore:EAttribute model1.ecore#//Address/name"/>
      <genFeatures createChild="false" ecoreFeature="ecore:EAttribute model1.ecore#//Address/street"/>
      <genFeatures createChild="false" ecoreFeature="ecore:EAttribute model1.ecore#//Address/city"/>
    </genClasses>
    <genClasses ecoreClass="model1.ecore#//Company">
      <genFeatures property="None" children="true" createChild="true" ecoreFeature="ecore:EReference model1.ecore#//Company/categories"/>
      <genFeatures property="None" children="true" createChild="true" ecoreFeature="ecore:EReference model1.ecore#//Company/suppliers"/>
      <genFeatures property="None" children="true" createChild="true" ecoreFeature="ecore:EReference model1.ecore#//Company/customers"/>
      <genFeatures property="None" children="true" createChild="true" ecoreFeature="ecore:EReference model1.ecore#//Company/purchaseOrders"/>
      <genFeatures property="None" children="true" createChild="true" ecoreFeature="ecore:EReference model1.ecore#//Company/salesOrders"/>
    </genClasses>
    <genClasses ecoreClass="model1.ecore#//Supplier">
      <genFeatures notify="false" createChild="false" propertySortChoices="true" ecoreFeature="ecore:EReference model1.ecore#//Supplier/purchaseOrders"/>
    </genClasses>
    <genClasses ecoreClass="model1.ecore#//Customer">
      <genFeatures notify="false" createChild="false" propertySortChoices="true" ecoreFeature="ecore:EReference model1.ecore#//Customer/salesOrders"/>
    </genClasses>
    <genClasses ecoreClass="model1.ecore#//Order">
      <genFeatures property="None" children="true" createChild="true" ecoreFeature="ecore:EReference model1.ecore#//Order/orderDetails"/>
    </genClasses>
    <genClasses ecoreClass="model1.ecore#//OrderDetail">
      <genFeatures property="None" notify="false" createChild="false" ecoreFeature="ecore:EReference model1.ecore#//OrderDetail/order"/>
      <genFeatures notify="false" createChild="false" propertySortChoices="true" ecoreFeature="ecore:EReference model1.ecore#//OrderDetail/product"/>
      <genFeatures createChild="false" ecoreFeature="ecore:EAttribute model1.ecore#//OrderDetail/price"/>
    </genClasses>
    <genClasses ecoreClass="model1.ecore#//PurchaseOrder">
      <genFeatures createChild="false" ecoreFeature="ecore:EAttribute model1.ecore#//PurchaseOrder/date"/>
      <genFeatures notify="false" createChild="false" propertySortChoices="true" ecoreFeature="ecore:EReference model1.ecore#//PurchaseOrder/supplier"/>
    </genClasses>
    <genClasses ecoreClass="model1.ecore#//SalesOrder">
      <genFeatures createChild="false" ecoreFeature="ecore:EAttribute model1.ecore#//SalesOrder/id"/>
      <genFeatures notify="false" createChild="false" propertySortChoices="true" ecoreFeature="ecore:EReference model1.ecore#//SalesOrder/customer"/>
    </genClasses>
    <genClasses ecoreClass="model1.ecore#//Category">
      <genFeatures createChild="false" ecoreFeature="ecore:EAttribute model1.ecore#//Category/name"/>
      <genFeatures property="None" children="true" createChild="true" ecoreFeature="ecore:EReference model1.ecore#//Category/categories"/>
      <genFeatures property="None" children="true" createChild="true" ecoreFeature="ecore:EReference model1.ecore#//Category/products"/>
    </genClasses>
    <genClasses ecoreClass="model1.ecore#//Product">
      <genFeatures createChild="false" ecoreFeature="ecore:EAttribute model1.ecore#//Product/name"/>
      <genFeatures notify="false" createChild="false" propertySortChoices="true" ecoreFeature="ecore:EReference model1.ecore#//Product/orderDetails"/>
    </genClasses>
  </genPackages>
</genmodel:GenModel>


Generate The Model

Generate the Java code for your model like you are used to do it:


GenerateTheModel.png


The result of the generation can look similar to this (some artifacts are hidden to declutter the Package Explorer):


GeneratorResults.png


Important note: If you want to modify the behaviour of generated getters and setters (or have already done so in existing models) you might want to try dynamic feature delegation (introduced in EMF 2.5). With this pattern, the reflective methods like eGet still call your generated method like getX() and then that calls the dymamic reflective method like eDynamicGet. It effectively produces the same behavior as "Refective" delegating but does so by delegating through your generated accessors allowing you to specialize those as you could when you used "None"...



Wikis: CDO | Net4j | EMF | Eclipse

Copyright © Eclipse Foundation, Inc. All Rights Reserved.