[tests] Get the ModelMorf MiToSi example working

[eclipse-qvtd-bot]

| --- | --- | | Bugzilla Link | 512737 | | Status | NEW | | Importance | P3 normal | | Reported | Feb 26, 2017 11:53 EDT | | Modified | Mar 02, 2017 04:23 EDT | | Depends on | 512738 | | Blocks | 512682 | | Reporter | Ed Willink |

Description

MiToSi does not work straight off.

---

Needs an

import ecoreMM : 'http://www.eclipse.org/emf/2002/Ecore';

uml:{umlmmmi,ecoreMM}

since the UML mm uses EString.

---

The "when X(...) or Y(...)" requires a change to associate variables with TypedModel rather than RelationDomain which are not unique.

---

The above "or" goes bang when the RelationCallExp is copied to QVTc.

How is an alternation of when predicates expressed in QVTc?

[eclipse-qvtd-bot]

By Ed Willink on Feb 26, 2017 12:04

(In reply to Ed Willink from comment #0)

How is an alternation of when predicates expressed in QVTc?

Bug 512738

[eclipse-qvtd-bot]

By Ed Willink on Feb 27, 2017 12:36

The alternation is perhaps poor style. Rwriting in a sensible style and many other problems arise....

It is really disturbing how a nominally supported example needs so much steering/debugging. The eventual JUnit test can probably have three or four different implementations.

Bur are we really ready for version 1.0 in June???

[eclipse-qvtd-bot]

By Ed Willink on Feb 28, 2017 11:40

(In reply to Ed Willink from comment #2)

Rewriting in a sensible style

and fixing the problems: => MiToSiSimple.qvtr.

This appears to work and perhaps explains why the expected transportjava.xml is not part of the ModelMorf distribution. ModelMorf does not work as documented, even after allowing for the mak=gic root dummy.

The write up suggests 4 result classes, 5 result interfaces and three class-implements relationships.

MiToSiSimple.qvtr also creates 3 class-extends and 4 interface-extends relationships.

(In reply to Ed Willink from comment #2)

The eventual JUnit test can probably have three or four different implementations.

Two or three to go.