Well, actually talked about metamodel evolution at EclipseCon last week in the end. A not-so-surprising 2/3rd of the room was full and provided interesting questions, even met Sven of the Edapt project proposal that also includes COPE contributions (see http://www.eclipse.org/proposals/edapt/ ).

Session and slides at http://www.eclipsecon.org/2010/sessions/?page=sessions&id=1207

So all in all thanks for helping provide the idea !

Regards,
Marc

which XSLT-processor do you use? Do you use XSLT 2.0?

Cheers, Tobias.

Feels like model evolution is fated to become a prominent topic…

At Eclipse JWT (Java Workflow Tooling http://eclipse.org/jwt ) we’ve written an ATL-based converter to ease migrating existing models to new versions of our EMF metamodel. Basically, when trying to open an older model, it deduces which ATL transformations have to be applied before being able to open it.

We also do XSL but on very specific topics, however, I didn’t know about COPE.

Maybe an interesting talk topic for the next EclipseCon ?

Regards,
Marc

I worked with XSLT for the plain XML transformation and with ATL for the model transformation.

IMHO I would use ATL for dealing with EMF model (instances).

the problem with the XSLT stuff is that you are doing the transformation on the persistence format. This will only work until you are using the (less performant) XML or XMI resources. I’d go with ATL, QVT, Xpand or Cope, depending on your needs…

Bernd