简体   繁体   English

EMF:跟上不同版本的ecore模型

[英]EMF : Keeping up with different version of ecore model

When we made initial release of our model we had the following model 1. Person:String:Name,String :Address 2. Version : 1.0 最初发布模型时,我们具有以下模型1. Person:String:Name,String:Address 2.版本:1.0

so export /import was easy using EMF's persistent APIs(Storing them as xmls). 因此使用EMF的持久性API(将它们存储为xmls)可以轻松进行导出/导入。

Now we have changed the model to 1. Person :String:Name,Address 2. Address: String:House Number, String:Stree Name, String:City 3. Version : 2.0 现在我们将模型更改为1。Person:String:Name,Address 2. Address:String:House Number,String:Stree Name,String:City3。Version:2.0

The same thing explained below 同样的事情在下面解释

在此处输入图片说明

Now how to support older xml files(which are exported using old model) in the new Model. 现在如何在新模型中支持较旧的xml文件(使用旧模型导出)。

Is there any support in EMF to do this? EMF中是否有任何支持来做到这一点?

There are some tools/frameworks to help with model migration. 有一些工具/框架可帮助模型迁移。 Edapt is probably the most well-known (and an official Eclipse project). Edapt可能是最著名的(也是正式的Eclipse项目)。 Basically, it includes tooling and runtime support that tracks the history of your metamodels and can migrate instances at runtime. 基本上,它包括工具和运行时支持,可跟踪您的元模型的历史并可在运行时迁移实例。 There was a talk about it at EclipseCon earlier this year. 今年早些时候在EclipseCon上有关于它讨论

I've also heard of another project, EMF Migrate , but I don't know much about it. 我也听说过另一个项目EMF Migrate ,但是对此我不太了解。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM