MDT/New and Noteworthy/1.0
Model Development Tools Release 1.0 New and Noteworthy Items.
For more details about the development plan, see the MDT 1.0 draft plan.
Back to Modeling Development Tools.
- 1 EMF Ontology Definition Metamodel (EODM) Component
- 2 Object Constraint Language (OCL) Component
- 2.1 Release 1.1 M4
- 2.2 Release 1.1 M5
- 2.3 Release 1.1 M6
- 2.4 Release 1.1 M7
- 3 Unified Modeling Language 2.x (UML2) Component
- 3.1 2.1 M4
- 3.2 2.1 M5
- 3.3 2.1 M6
- 3.4 2.1 M7
- 4 UML2 Tools Component
- 5 XML Schema Infoset (XSD) Component
EMF Ontology Definition Metamodel (EODM) Component
- EODM 2.0.0 code is checked in after CVS access rights problem is solved.
- EODM 2.0.0 code has big changes in package structure and API to adapt/conform to the latest ODM specification.
- EODM 2.0.0 code also introduces the new "dynamic typing" capability.
- Use Modeling project logo instead of default Eclipse logo in features
- Javadoc is compiled and added to the doc plugin
- All plugins are named mdt-eodm-* and all their version numbers are upgraded to 0.8.0.
- Two bug fixes:
- Code base is moved to MDT CVS and the new MDT build system is used to produce this release.
Object Constraint Language (OCL) Component
Release 1.1 M4
LPG Java Runtime Restructuring
Stand-alone Deployment Support
The OCL Downloads page now includes a stand-alone ZIP containing just the JARs required for deployment in a non-Eclipse environment. The EMF stand-alone deployment that is also required is available separately.
Other Bug Fixes
For other bug fixes, see the 1.1 M4 release notes.
Release 1.1 M5
EMF 2.3 Adoption and Generics
This milestone introduces a significant refactoring of the OCL Parser/Interpreter API, with the adoption of EMF 2.3 and its support for generic types. Using Ecore's generics, a new generic Abstract Syntax model for OCL is defined in the org.eclipse.ocl plug-in:
This new model, and the OCL Parser/Interpreter core API, are thus freed from the dependency on the Ecore metamodel. The org.eclipse.emf.ocl plug-in is now deprecated and is supplanted by an Ecore binding (and environment implementation) of the generic model in the org.eclipse.ocl.ecore plug-in. The deprecated API delegates to the new Ecore binding for parsing of constraints, translating the resulting ASTs to the old Ecore-centric model. Utilities are also provided to convert existing ASTs in the old model to the new. The org.eclipse.emf.ocl API remains fully supported.
OCL Document Parsing API
org.eclipse.ocl.OCL generic class is the focal point
of OCL parsing and evaluation. Besides creating
for parsing embedded constraints and
for evaluating constraints, it can also parse OCL documents (text files external to the model). The
content of an OCL document is encapsulated by the
The parser supports the package and classifier context declarations, as well as all of the
kinds of constraints supported by the
- classifier invariants
- operation pre-, post-, and body conditions
- attribute initial and derived values
- def: expressions for additional attributes and properties
package ocltest context Fruit inv not_black: self.color <> Color::black def property_helper: otherFruits : Set(Fruit) = Fruit.allInstances()->excluding(self) def operation_helper: getOtherFruits1(fruit : Fruit) : Set(Fruit) = Fruit.allInstances()->excluding(fruit) context Apple::preferredLabel(text : String) : String pre text_not_null: not text.oclIsUndefined() pre text_not_label: text <> label body compute_label: if text = label then '' else text endif post label_is_changed: label <> label@pre post label_is_set: label = text context Apple::name : String init: '' derive: if label.oclIsUndefined() then '' else label endif endpackage
OCL Constraints on UML Models
The new generic OCL implementation lays the ground-work for support for the UML metamodel (as opposed to Ecore). This is implemented in the new org.eclipse.ocl.uml feature (and plug-in of the same name). This consists of
- UML bindings for the generic parameters of the core OCL API, including a UML implementation of the
- a specialization of the OCL Types package for OCL metatypes that are consistent with UML
- UML models of the abstract syntax model, UML binding, and OCL Standard Library (works in progress)
The UML environment supports the following UML-specific OCL concepts that the Ecore environment does not:
- isQuery property of operations
- qualified association navigation
- association-class navigation
- state expressions (using UML state machines)
- constraints defined on stereotypes
The UML evaluation environment (for evaluation of OCL constraints) supports two kinds of instance models:
instance specifications in the UML model (as
and run-time instances (as
EObjects) of an API generated by the UML2
code generator. Evaluation on instance specifications supports association-class and qualified association
navigation but not operation calls (except where those operations have body conditions specified in OCL).
As a special case of the evaluation on
EObjects, for the UML metamodel itself, the UML
environment allows constraints defined on stereotypes to be evaluated on
Elements to which they are applied, as well as on the stereotype instances.
In either case, the constraint must be expressed in the context of the stereotype, navigating
the appropriate metaclass extension(s) to access the base element.
Other Bug Fixes
For other bug fixes, see the 1.1 M5 release notes.
In particular, additional operations and attributes defined by def: expressions (parsed from OCL documents or via the helper) are no longer "global" (attached to the model context classifier). They are now local to the org.eclipse.ocl.OCL environment in which they were parsed.
Release 1.1 M6
In M6, the generic Abstract Syntax model binding strategy was completed by implementing metamodel bindings for the Expressions package as was done for the Types package in M5. This allows the OCLExpression, Variable, TupleLiteralPart, and CollectionLiteralPart metaclasses that all specialize TypedElement to specialize the definition particular to the target metamodel. For more details, see the OCL 1.1 API Changes page for more details of what this means for clients.
The platform:/plugin/org.eclipse.ocl.uml/model/OCLUML.uml model was regenerated from its Ecore counterpart using the final version of the Ecore-to-UML converter's support for Ecore generics in the MDT UML2 component. Thus, it is now sufficiently "clean" to serve as the source model for code generation. This model was also updated with the feature subsets required to define ownership of operations and attributes in metaclasses such as MessageType, for which the Classifier metaclass only provides derived unions. With these changes, the entire UML binding implementation is now generated from the UML model.
Other Bug Fixes
For other bug fixes, see the 1.1 M6 release notes.
Release 1.1 M7
The major theme of this milestone was improvements to the SDK documentation. This includes both the Programmer's Guide documentation and the examples.
Programmer's Guide Enhancements
The OCL Programmer's Guide is much expanded, covering all major aspects of the OCL APIs from a parser/interpreter client perspective, and even some advanced subjects for extenders of the APIs. The documentation includes UML class diagrams for easy reference and plenty of code snippets providing code snippets.
Interactive OCL Console Enhancements
The Interactive OCL Console example plug-in (org.eclipse.emf.ocl.examples.interpreter) now demonstrates the content-assist support provided by the OCLHelper API:
It is also reworked to use the generic parsing APIs (OCL, OCLHelper, Query) instead of their Ecore specializations. With this change, the example now also demonstrates using the UML metamodel binding in addition to Ecore, to show how applications using OCL can make their own APIs likewise generic, so that their clients can use either metamodel implementation.
A final enhancement demonstrates how to use the OCL APIs to parse constraints on Ecore and UML models rather than the meta-models. The new Modeling Level selection on the action bar toggles between M2 (the metamodel), which is suitable for querying the model and printing the results of a query, and M1 (the model), which parses a constraint in the context of the selected element.
The input expression is parsed as a constraint, and a success or error message printed in the console, according to the selected context element:
- when a class is selected, the OCL expression is parsed as an invariant constraint
- when an operation is selected, a post-condition constraint (being a superset of the syntax of pre-conditions and body expressions)
- when an attribute is selected, a derivation expression
Other Bug Fixes
For other bug fixes, see the 1.1 M7 release notes.
Unified Modeling Language 2.x (UML2) Component
Eclipse 3.3 / EMF 2.3 Compatibility
In keeping with the “Release Currency” theme, the UML API has been given a facelift. Many methods within the UML API are now specified using Java 5.0 generics and are consistent with EMF’s changes for Java 5.0.
This could have potential impact on users calling the UML API, for example when working with lists of a specific meta-type. For details see bug 160679
Eclipse 3.3 / EMF 2.3 Compatibility
Starting in 2.1M5 users can convert UML models with templates to Ecore models with generics and vice versa. UML concepts such as templates, template bindings, etc., have a direct impact on the resulting Ecore model and ultimately the generated code. Likewise, Ecore models with EGenericTypes or ETypeParameters (new meta-types in the Ecore metamodel) can be converted to UML models that make use of the corresponding UML concepts.
For a more detailed explanation of generics in EMF and updates to the EMF metamodel see EMF 2.3 Generics.
Consider the following Ecore model and corresponding UML model.
In the Ecore model above we have a simple ETypeParameter and property typed by that parameter. The corresponding UML model has a template signature with classifier template parameter, and property typed by the corresponding parametered element.
Next, we have a generic supertype with eClassifier set to FourWheelCar. Also, we have two parameters of an operation with a bound templated classifier specified.
The corresponding UML model results in a bound classifier as follows.
In order to capture generics-related concepts in Ecore that have no counterpart in UML, the Ecore profile (Ecore.profile.uml) has been updated with new stereotypes, EGenericType and ETypeParameter. The EGenericType stereotype captures upperBound and lowerBound information not expressible in UML, and the ETypeParameter stereotype captures bounds on type parameters. In addition to capturing missing information, the EGenericType stereotype acts as a marker that such classifiers, although required in the UML model, are not required in the Ecore model and can hence be discarded.
Ant Task for Ecore Importer
In keeping with the “completeness” theme, a new Ant task has been created that allows users to generate code based on a UML model. From the Ant task, users can provide UML-specific code generation options for the generator model, generator package, and converter, in addition to passing an input UML model. The user is then one click away from running the Ant task and generating code directly from a UML model. Details can be found in bug 160680
Other Bug Fixes
For other bug fixes, see the 2.1 M5 release notes.
Create Child/Sibling Menu Reorganization
The 'Create Child' and 'Create Sibling' menus have been reoganized so that items are grouped by feature. This allows for quicker creation and easier navigation.
Static Profile Definition
In the "classical" approach to profiles, users typically create an Ecore representation by calling Profile#define(). When applying stereotypes from such a profile, a dynamically-generated EMF representation of the stereotype is retrieved from an annotation on the profile.
In M6, the ability to use statically defined profiles has been introduced. Users now have the option to convert their profiles to Ecore just as they would any other model. They can then generate code from that model and provide implemenations for operations and derived features. If the model is then registered in the EPackage registry, the UML API will discover the Ecore definition instead of looking for it in an annotation. In such a scenario, the "define" step on the profile is not needed - the conversion to Ecore replaces it.
Details on how this all works will be provided in a future article.
As part of this work, the Profile#define() method has been overloaded to accept options. New UML-to-Ecore conversion options have been introduced, including the ability to specify whether comments should be converted to code generator documentation in the resulting Ecore representation.
New API to Create Usage Dependencies
An additional convenience method has been introduced to create usage dependencies on named elements. Although the ability to create usage dependencies existed in the past, this new convenience method makes it even easier.
Other Bug Fixes
For other bug fixes, see the 2.1 M6 release notes.
[draft] Now users can specify invariant constraints in OCL or operation bodies.
- Two new converter options have been introduced to take into account body conditions or opaque behaviors. We now process body and add "body" annotation.
- Ecore representation now contains new annotations.
- Code generation takes new annotations into account and adds dependencies on OCL components.
User will have to have ocl plugins in his workspace for this to work. There is a runtime dependency on one component.
Details can be found in bug 105199
Updated Schema for Metamodel Changes
The namespace URI for the UML metamodel in UML2 2.1 has been changed to http://www.eclpse.org/uml2/2.1.0/UML.
This change was required to reflect changes to the metamodel. The metamodel changes address issues with bidirectional associations between Vertex#incoming/outgoing and Transition#source/target in addition to the bidirectional association between ConnectableElement#end and ConnectorEnd#role.
At the OMG, issues 10537 and 10536 have been raised.
The underlying motivation behind this issue has to do with fixing problems that were discovered while trying to implement redefinition, however, there is a more fundamental problem regarding the impact that bidirectional associations in the metamodel have on modeling in practice.
The goal of these changes is to break the requirement for bi-directional associations. Currently, when we modify the source and target of a transition, we do not directly modify the incoming and outgoing properties of Vertex which could be in another model.
Refer to: 185602
Export Wizard Improvements
The UML export wizard used to output new resources for every nested EPackage in a model. This no longer is the case.
Also, if the ecore model that is being converted contains references to types in other metamodels, the corresponding UML representation of that referenced metamodel will also be generated.
Details can be found in bug 172503
Validate action should validate stereotype applications
Migration issue for ActivityGroup.subgroup
Other Bug Fixes
For other bug fixes, see the 2.1 M7 release notes.