|Re: [Edapt] Proxy related issues on deserialization [message #1729390 is a reply to message #1729268]
||Wed, 13 April 2016 15:55
| Johannes Faltermeier
Registered: December 2013
Pretty wild stuff.
There is currently no way to influence the loading code of Edapt like that.
If you want to take a look at the loading code and maybe play around a bit:
org.eclipse.emf.edapt.internal.common.ResourceUtils.loadResourceSet(List<URI>, List<EPackage>, IResourceSetFactory)
Otherwise performing a "pre-migration" without edapt could be an option.
So, you get the NS-URI from your XMI file. If this is the version which still contains those proxy references, you manually replace those with a new attribute + string and update the ns uri using some kind of XMI-tool.
When you create/adjust your Ecore to be able to load this model, you can start your edapt history with the actual model refactorings from this metamodel version.
Get professional Eclipse developer support:
Powered by FUDForum
. Page generated in 0.01671 seconds