Have you ever evolved your metamodel in EMF and your models were no longer valid afterwards? Or have you avoided to evolve your metamodel in order not to invalidate your models? Or have you even deteriorated your metamodel so that it remains downwards compatible to previous versions in order to avoid these problems?
This site introduces COPE, a tool based on EMF that eases the migration of models in response to an evolving metamodel. COPE explicitly records the history of the metamodel as a sequence of changes and allows to attach information of how to migrate models (which is referred to as coupled evolution). The attached information can be used to automatically migrate models to the new version of the metamodel. COPE even goes one step further and allows to reuse combinations of metamodel adaptation and model migration steps across metamodels.
In order not to disturb EMF users in their habits, COPE seamlessly integrates into the Ecore editor. A demonstration of the tool in action can be looked at here. It is planned to contribute COPE to the Eclipse community.
Model-based Data Export Tool
Features
* Mass data export to XML and SQL.
* Generates hierarchically structured XML and topologically sorted SQL-DML.
* Exports consistent and referentially intact row-sets from your productive database and imports the data into your development and test environment.
* Removes and archives obsolete data from your productive database without violating integrity.
* Open Source. Entirely written in Java. Platform independent. DBMS agnostic.