Bug 77410

Comment 1 Nick Brett 2004-11-16 08:38:22 EST

Hi,

Will this framework make it any easier to write arbitrary transformations
between UML2 models rather than just migrating UML model versions?

My particular interest is in transformations for model compilers but there are
of course a number of scenarious where transforming a UML2 model into another
UML2 model is important, refactoring for example in which case no meta-model
change has occured.

Or as another example migration between models with profiles applied rather than
just core UML2.

Also will it have any relation to QVT or other more general model transformation
work?

Comment 2 Kenn Hussey 2004-11-18 15:56:46 EST

This enhancement is not intended as a generic transformation framework, but 
rather a mechanism to support migration between versions of an EMF-based 
metamodel. However, a similar approach (that of using a custom resource 
implementation with extended metadata) could possibly be used to support 
transformations (e.g. Ecore - EMOF conversion).

Comment 3 Steve Speicher 2004-11-29 09:32:11 EST

Regarding Nick Brett's comment on a generic transformation framework...

There is an Eclipse technology project looking at that problenm GMT (Generative
Transformation Framework) http://www.eclipse.org/gmt/ based on QVT, EMF, etc.

I think that is where the generic framwork will arrise.

Comment 4 Dusko 2004-12-03 15:40:14 EST

I assume that those UML2 schema based resources include both models and 
profiles. In case of profiles I think it would be worthwhile to provide "the 
best effort" migration algorithm based on names in absence of the mapping 
file. It would probably be useful for models as well but it is more important 
for profiles as they internally create schemas every time the profile 
is 'defined'. These internal schemas can (and are) be programmatically deleted 
thus forcing authors to create a mapping file even for simple updates.

Comment 5 Kenn Hussey 2004-12-23 15:34:34 EST

A new mapping capability, Ecore2XML (plug-ins 
org.eclipse.uml2.mapping.ecore2xml.*; subject to change), has been added as of 
build 1.1M2. In combination with resource pre/post-processors and the 
XMLResource.OPTION_RECORD_UNKNOWN_FEATURE load option, this capability can be 
used to migrate between different versions of a given (Ecore-based) schema or 
in fact transform between two entirely different (Ecore-based) schemas.

An example (plug-in org.eclipse.uml2.examples.emof2ecore), which transforms a 
resource from the EMOF schema to the Ecore schema, has also been provided as 
part of the examples feature. Documentation to follow.

Auto-migration of profiles based on name matching will be addressed separately, 
time permitting.

Comment 6 Kenn Hussey 2005-02-21 13:47:48 EST

The Ecore2XML capability is being moved to EMF (see 85979). Refactor UML2 (and 
example) code as required.

Comment 7 Kenn Hussey 2005-03-18 16:18:32 EST

The changes have been committed to CVS.

Comment 8 Kenn Hussey 2005-03-31 14:00:04 EST

The necessary refactoring has been done as of build I200503311223.

Comment 9 Nick Boldt 2008-01-28 16:34:12 EST

Move to verified as per bug 206558.