EclipseModelingFramework(EMF)DeveloperGuide资源-CSDN文库

5星 · 超过95%的资源需积分: 9 155 浏览量 2008-06-24 15:59:48 上传评论 1 收藏 1.59MB PDF 举报

资源详情

资源评论

Eclipse Modeling Framework (EMF) Developer Guide http://127.0.0.1:50338/help/advanced/print.jsp?topic=/../nav/14_7_2

第1页共215页 2008-4-11 13:38

Eclipse Modeling Framework (EMF) Developer Guide

Contents

1. Programmer's Guides

1.1. EMF Framework Programmer's Guide

1.2. EMF.Edit Framework Programmer's Guide

1.3.

EMF Validation Framework Programmer's Guide

2. Tutorials

2.1. Generating an EMF Model

2.2.

Generating an Extended EMF Model

2.3. Generating an EMF Model using XML Schema

2.4. JET Tutorial Part 1 (Introduction to JET)

2.5.

JET Tutorial Part 2 (Write Code that Writes Code)

2.6. Specifying Package Information in Rose

3. Online Docs

3.1.

Release Notes

3.1.1. What's New in v2.3

3.1.2. What's New in v2.2

3.1.3.

What's New in v2.1

3.1.4. What's New in v2.0

3.1.5. What's New in v1.x

3.2.

EMF FAQ

4. Reference

4.1.

API Reference

4.1.1. org.eclipse.emf.ant

4.1.2. org.eclipse.emf.ant.taskdefs.codegen.ecore

4.1.3.

org.eclipse.emf.ant.taskdefs.codegen

4.1.4. org.eclipse.emf.ant.taskdefs

4.1.5. org.eclipse.emf.ant.util

4.1.6.

org.eclipse.emf.codegen.action

4.1.7. org.eclipse.emf.codegen.ecore.generator

4.1.8. org.eclipse.emf.codegen.ecore.genmodel.action

4.1.9.

org.eclipse.emf.codegen.ecore.genmodel.generator

4.1.10. org.eclipse.emf.codegen.ecore.genmodel.impl

4.1.11. org.eclipse.emf.codegen.ecore.genmodel

4.1.12.

org.eclipse.emf.codegen.ecore.genmodel.presentation

4.1.13. org.eclipse.emf.codegen.ecore.genmodel.provider

4.1.14. org.eclipse.emf.codegen.ecore.genmodel.util

4.1.15.

org.eclipse.emf.codegen.ecore

4.1.16.

org.eclipse.emf.codegen.ecore.templates.edit

4.1.17.

org.eclipse.emf.codegen.ecore.templates.editor

4.1.18.

org.eclipse.emf.codegen.ecore.templates.model

4.1.19. org.eclipse.emf.codegen.ecore.templates.model.tests

4.1.20. org.eclipse.emf.codegen.ecore.ui

4.1.21.

org.eclipse.emf.codegen.jet

4.1.22. org.eclipse.emf.codegen.jmerge

4.1.23. org.eclipse.emf.codegen.merge.java.facade.ast

4.1.24.

org.eclipse.emf.codegen.merge.java.facade.jdom

4.1.25. org.eclipse.emf.codegen.merge.java.facade

4.1.26. org.eclipse.emf.codegen.merge.java

4.1.27.

org.eclipse.emf.codegen.merge.properties

4.1.28. org.eclipse.emf.codegen

4.1.29. org.eclipse.emf.codegen.presentation

4.1.30.

org.eclipse.emf.codegen.util

4.1.31. org.eclipse.emf.common.archive

4.1.32. org.eclipse.emf.common.command

4.1.33.

org.eclipse.emf.common.notify.impl

4.1.34. org.eclipse.emf.common.notify

4.1.35. org.eclipse.emf.common

4.1.36.

org.eclipse.emf.common.ui.action

4.1.37. org.eclipse.emf.common.ui.celleditor

4.1.38. org.eclipse.emf.common.ui.dialogs

4.1.39.

org.eclipse.emf.common.ui.editor

4.1.40. org.eclipse.emf.common.ui

Eclipse Modeling Framework (EMF) Developer Guide http://127.0.0.1:50338/help/advanced/print.jsp?topic=/../nav/14_7_2

第2页共215页 2008-4-11 13:38

4.1.41.

org.eclipse.emf.common.ui.viewer

4.1.42.

org.eclipse.emf.common.ui.wizard

4.1.43.

org.eclipse.emf.common.util

4.1.44. org.eclipse.emf.converter

4.1.45.

org.eclipse.emf.converter.ui.contribution.base

4.1.46.

org.eclipse.emf.converter.ui.contribution

4.1.47. org.eclipse.emf.converter.ui

4.1.48.

org.eclipse.emf.converter.util

4.1.49. org.eclipse.emf.ecore.action

4.1.50. org.eclipse.emf.ecore.change.impl

4.1.51.

org.eclipse.emf.ecore.change

4.1.52. org.eclipse.emf.ecore.change.provider

4.1.53. org.eclipse.emf.ecore.change.util

4.1.54.

org.eclipse.emf.ecore.impl

4.1.55.

org.eclipse.emf.ecore

4.1.56. org.eclipse.emf.ecore.plugin

4.1.57.

org.eclipse.emf.ecore.presentation

4.1.58.

org.eclipse.emf.ecore.provider

4.1.59. org.eclipse.emf.ecore.resource.impl

4.1.60.

org.eclipse.emf.ecore.resource

4.1.61.

org.eclipse.emf.ecore.util

4.1.62. org.eclipse.emf.ecore.xmi.impl

4.1.63.

org.eclipse.emf.ecore.xmi

4.1.64.

org.eclipse.emf.ecore.xmi.util

4.1.65. org.eclipse.emf.ecore.xml.namespace.impl

4.1.66.

org.eclipse.emf.ecore.xml.namespace

4.1.67. org.eclipse.emf.ecore.xml.namespace.util

4.1.68. org.eclipse.emf.ecore.xml.type.impl

4.1.69.

org.eclipse.emf.ecore.xml.type.internal

4.1.70. org.eclipse.emf.ecore.xml.type

4.1.71. org.eclipse.emf.ecore.xml.type.util

4.1.72.

org.eclipse.emf.edit.command

4.1.73. org.eclipse.emf.edit.domain

4.1.74. org.eclipse.emf.edit

4.1.75.

org.eclipse.emf.edit.provider

4.1.76. org.eclipse.emf.edit.provider.resource

4.1.77. org.eclipse.emf.edit.tree.impl

4.1.78.

org.eclipse.emf.edit.tree

4.1.79. org.eclipse.emf.edit.tree.provider

4.1.80. org.eclipse.emf.edit.tree.util

4.1.81.

org.eclipse.emf.edit.ui.action

4.1.82.

org.eclipse.emf.edit.ui.celleditor

4.1.83. org.eclipse.emf.edit.ui.dnd

4.1.84.

org.eclipse.emf.edit.ui

4.1.85.

org.eclipse.emf.edit.ui.provider

4.1.86. org.eclipse.emf.edit.ui.util

4.1.87.

org.eclipse.emf.edit.ui.view

4.1.88.

org.eclipse.emf.exporter

4.1.89. org.eclipse.emf.exporter.ui.contribution.base

4.1.90.

org.eclipse.emf.exporter.ui.contribution

4.1.91.

org.eclipse.emf.exporter.ui

4.1.92. org.eclipse.emf.exporter.util

4.1.93.

org.eclipse.emf.importer.ecore

4.1.94. org.eclipse.emf.importer.ecore.taskdefs

4.1.95. org.eclipse.emf.importer.ecore.ui

4.1.96.

org.eclipse.emf.importer.java.builder

4.1.97.

org.eclipse.emf.importer.java

4.1.98. org.eclipse.emf.importer.java.taskdefs

4.1.99.

org.eclipse.emf.importer.java.ui

4.1.100.

org.eclipse.emf.importer

4.1.101. org.eclipse.emf.importer.rose.builder

4.1.102.

org.eclipse.emf.importer.rose

4.1.103.

org.eclipse.emf.importer.rose.parser

4.1.104. org.eclipse.emf.importer.rose.taskdefs

4.1.105.

org.eclipse.emf.importer.rose.ui

4.1.106.

org.eclipse.emf.importer.ui.contribution.base

Eclipse Modeling Framework (EMF) Developer Guide http://127.0.0.1:50338/help/advanced/print.jsp?topic=/../nav/14_7_2

第3页共215页 2008-4-11 13:38

4.1.107.

org.eclipse.emf.importer.ui.contribution

4.1.108.

org.eclipse.emf.importer.ui

4.1.109.

org.eclipse.emf.importer.util

4.1.110. org.eclipse.emf.mapping.action

4.1.111.

org.eclipse.emf.mapping.command

4.1.112.

org.eclipse.emf.mapping.domain

4.1.113. org.eclipse.emf.mapping.ecore2ecore.action

4.1.114.

org.eclipse.emf.mapping.ecore2ecore.impl

4.1.115. org.eclipse.emf.mapping.ecore2ecore

4.1.116. org.eclipse.emf.mapping.ecore2ecore.presentation

4.1.117.

org.eclipse.emf.mapping.ecore2ecore.provider

4.1.118. org.eclipse.emf.mapping.ecore2ecore.util

4.1.119. org.eclipse.emf.mapping.ecore2xml.action

4.1.120.

org.eclipse.emf.mapping.ecore2xml.impl

4.1.121.

org.eclipse.emf.mapping.ecore2xml

4.1.122. org.eclipse.emf.mapping.ecore2xml.presentation

4.1.123.

org.eclipse.emf.mapping.ecore2xml.provider

4.1.124.

org.eclipse.emf.mapping.ecore2xml.ui

4.1.125. org.eclipse.emf.mapping.ecore2xml.util

4.1.126.

org.eclipse.emf.mapping.impl

4.1.127.

org.eclipse.emf.mapping

4.1.128. org.eclipse.emf.mapping.presentation

4.1.129.

org.eclipse.emf.mapping.provider

4.1.130.

org.eclipse.emf.mapping.util

1.1. The Eclipse Modeling Framework (EMF) Overview

Last updated: June 16, 2005 (accessibility update)

This paper presents a basic overview of EMF and its code generator patterns. For a more complete description of

all the features of EMF, refer to

Eclipse Modeling Framework (Addison Wesley, 2003) or to the Javadoc for the

framework classes themselves.

Introduction

EMF is a Java framework and code generation facility for building tools and other applications based on a

structured model. For those of you that have bought into the idea of object-oriented modeling, EMF helps you

rapidly turn your models into efficient, correct, and easily customizable Java code. For those of you that aren't

necessarily sold on the value of formal models, EMF is intended to provide you with the same benefits and a very

low cost of entry.

So, what do we mean when we say model? When talking about modeling, we generally think about things like

Class Diagrams, Collaboration Diagrams, State Diagrams, and so on. UML (Unified Modeling Language) defines a

(the) standard notation for these kinds of diagrams. Using a combination of UML diagrams, a complete model of an

application can be specified. This model may be used purely for documentation or, given appropriate tools, it can

be used as the input from which to generate part of or, in simple cases, all of an application.

Given that this kind of modeling typically requires expensive Object Oriented Analysis and Design (OOA/D) tools,

you might be questioning our assertion, above, that EMF provides a low cost of entry. The reason we can say that

is because an EMF model requires just a small subset of the kinds of things that you can model in UML, specifically

simple definitions of the classes and their attributes and relations, for which a full-scale graphical modeling tool is

unnecessary.

While EMF uses XMI (XML Metadata Interchange) as its canonical form of a model definition

[1]

, you have several

ways of getting your model into that form:

Create the XMI document directly, using an XML or text editor

Export the XMI document from a modeling tool such as Rational Rose

Annotate Java interfaces with model properties

Use XML Schema to describe the form of a serialization of the model

The first approach is the most direct, but generally only appeals to XML gurus. The second choice is the most

desirable if you are already using full-scale modeling tools. The third approach provides pure Java programmers a

low-cost way to get the benefits of EMF and its code generator using just a basic Java development environment

(for example, Eclipse's Java Development Tools). The last approach is most applicable in creating an application

that must read or write a particular XML file format.

Eclipse Modeling Framework (EMF) Developer Guide http://127.0.0.1:50338/help/advanced/print.jsp?topic=/../nav/14_7_2

第4页共215页 2008-4-11 13:38

Once you specify an EMF model, the EMF generator can create a corresponding set of Java implementation

classes. You can edit these generated classes to add methods and instance variables and still regenerate from the

model as needed: your additions will be preserved during the regeneration. If the code you added depends on

something that you changed in the model, you will still need to update the code to reflect those changes; otherwise,

your code is completely unaffected by model changes and regeneration.

In addition to simply increasing your productivity, building your application using EMF provides several other

benefits like model change notification, persistence support including default XMI and schema-based XML

serialization, a framework for model validation, and a very efficient reflective API for manipulating EMF objects

generically. Most important of all, EMF provides the foundation for interoperability with other EMF-based tools and

applications.

EMF consists of two fundamental frameworks: the core framework and EMF.Edit. The core framework provides

basic generation and runtime support to create Java implementation classes for a model. EMF.Edit extends and

builds on the core framework, adding support for generating adapter classes that enable viewing and

command-based (undoable) editing of a model, and even a basic working model editor. The following sections

describe the main features of the core EMF framework. EMF.Edit is described in a separate paper,

The EMF.Edit

Framework Overview. For instructions on how to run the EMF and EMF.Edit generator, refer to Tutorial: Generating

an EMF Model.

EMF Relation to OMG MOF

For those of you that are familiar with OMG (Object Management Group) MOF (Meta Object Facility), you may be

wondering how EMF relates to it. Actually, EMF started out as an implementation of the MOF specification but

evolved from there based on the experience we gained from implementing a large set of tools using it. EMF can be

thought of as a highly efficient Java implementation of a core subset of the MOF API. However, to avoid any

confusion, the MOF-like core meta model in EMF is called Ecore.

In the current proposal for MOF 2.0, a similar subset of the MOF model, which it calls EMOF (Essential MOF), is

separated out. There are small, mostly naming differences between Ecore and EMOF; however, EMF can

transparently read and write serializations of EMOF.

Defining an EMF Model

To help describe EMF, we'll start by assuming we have a trivial, one-class model like this:

The model shows a single class called Book with two attributes: title of type String and pages of type int.

Our model definition, trivial as it is, can be provided to the EMF code generator in a number of ways.

UML

If you have a modeling tool that works with EMF

[2]

, you can simply draw the class diagram as shown above.

XMI

Alternatively, we could describe the model directly in an XMI document that would look something like this:

<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="library "nsURI="http:///library.ecore" nsPrefix="library">

<eStructuralFeatures xsi:type="ecore:EAttribute" name="title"

eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EString"/>

<eStructuralFeatures xsi:type="ecore:EAttribute" name="pages"

eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EInt"/>

</eClassifiers>

</ecore:EPackage>

The XMI document contains all the same information as the class diagram, but a little less compactly. Every class

and attribute in a diagram has a corresponding class or attribute definition in the XMI document.

Annotated Java

Eclipse Modeling Framework (EMF) Developer Guide http://127.0.0.1:50338/help/advanced/print.jsp?topic=/../nav/14_7_2

第5页共215页 2008-4-11 13:38

For those of you that have neither a graphical modeling tool nor an interest in trying to enter all the XMI syntax by

hand, a third option is available for describing your model. Since the EMF generator is a code-merging generator,

by providing partial Java interfaces (annotated with model information) ahead of time, the generator can use the

interfaces as its generation metadata and merge the generated code with the rest of the implementation.

We could have defined our Book model class in Java like this:

/**

* @model

public interface Book

{

/**

* @model

String getTitle();

/**

* @model

int getPages();

}

With this approach, we provide all the model information in the form of Java interfaces with standard get

methods

[3]

to identify the attributes and references. The @model tag is used to identify to the code generator which interfaces,

and parts of those interfaces, correspond to model elements and therefore require code generation.

For our simple example, all of our model information is actually available though Java introspection of this interface,

so no additional model information is needed. In the general case, however, the @model tag may be followed by

additional details about the model element. If for example, we wanted the pages attribute to be read-only (that is, no

generation of a set method), we would need to add the following to the annotation:

/**

* @model changeable="false"

int getPages();

Because only information that is different from the default needs to be specified, annotations can be kept simple

and concise.

XML Schema

Sometimes, you might want to describe a model with a schema that specifies how instance serializations should

look. This can be useful for writing an application that must use XML to integrate with an existing application or to

comply with a standard. Here is how we would specify a schema that's equivalent to our simple book model:

<xsd:schema targetNamespace="http:///library.ecore"

xmlns="http:///library.ecore" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<xsd:complexType name="Book">

<xsd:sequence>

<xsd:element name="title" type="xsd:string"/>

<xsd:element name="pages" type="xsd:integer"/>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

This approach differs somewhat from the other three, mainly because EMF must apply certain restrictions to the

serialization that it eventually uses, to ensure compliance with the schema. As a result, the model that is a created

for a schema looks slightly different from one specified in one of the other ways. The details of these differences

are beyond the scope of this overview.

In the remainder of this paper, we'll use UML diagrams for their clarity and conciseness. All of the modeling

concepts we'll illustrate could also be expressed using annotated Java or directly with XMI, and most have XML

Schema equivalents. Regardless of how the information is provided, the code generated by EMF will be the same.

Generating a Java Implementation

For each class in the model, a Java interface and corresponding implementation class will be generated. In our

example, the generated interface for Book looks like this:

public interface Book extends EObject

{

String getTitle();

剩余214页未读，继续阅读

评论收藏

内容反馈

普通网友

2012-04-10

EMF架构很好，集合了很多东西。

Eclipse Modeling Framework (EMF) Developer Guide

评论3

最新资源

Eclipse Modeling Framework (EMF) Developer Guide

评论3

最新资源

相关推荐

eclipse Modeling Framework

emf eclipse

用EclipseModelingFramework实现模型驱动开发，第1部分

eclipse+modeling+framework+2.0中文版(不全)

EclipseModelingFramework中文版

EMF_Eclipse_Modeling_Framework_2nd_Edition 源码

Eclipse Modeling Framework 2.0中文版 [（美）斯泰因贝格等著][清华大学出版社]

EMF Eclipse Modeling Framework 第二版

EMF Developer Guide

Eclipse.Modeling.Framework

EMF.pdf(Eclipse Modeing Framework)

High Availability Framework Developer's Guide

EMF.Eclipse Modeling Framework.2nd part1

Zend Framework 3 Developer's Guide azw3

A Developer's Guide to Data Modeling for SQL Server

Oracle Application Framework Developer's Guide R12

Zend Framework 3 Developer's Guide mobi

Oracle Application Framework Developer's Guide 12.1.3

JIDE_Action_Framework_Developer_Guide.pdf

Zend Framework 3 Developer's Guide epub

Eclipse Modeling Framework.[Addison Wesley].chm

EMF_Eclipse Modeling Framework 2ndEdition

EMF.Eclipse Modeling Framework.2nd part3

Eclipse Modeling Framework 2nd Edition

EMF.Eclipse Modeling Framework.2nd part2

Java第十五届蓝桥杯大赛软件JavaB组真题

SwitchHosts

安卓期末大作业（AndroidStudio开发），垃圾分类助手app，分为前台后台，代码有注释，均能正常运行

Notepad++安装包