|
Re: Edapt migrate the class with slots in inverse order [message #1816168 is a reply to message #1816110] |
Wed, 23 October 2019 07:24 |
|
Hi,
Is the 1.6 version of your model the most current one? If so Edapt translates the dynamic model into the concrete model using the generated code as a last step. So there should be no difference when it comes to persistence.
Are you using some Resource-Save-Options or do you have a special Resource Implementation in your application? If you use Migrator.migrateAndSave you may pass in the save options as an additional parameter starting from version 1.1. If you have a special resource implementation, you may use Migrator.setResourceSetFactory(IResourceSetFactory) in order to make the Migrator use this one as well.
Cheers,
Johannes
Johannes Faltermeier
Get professional Eclipse developer support:
http://eclipsesource.com/en/services/developer-support/
|
|
|
Re: Edapt migrate the class with slots in inverse order [message #1816200 is a reply to message #1816168] |
Wed, 23 October 2019 13:53 |
Arun Kumar Messages: 14 Registered: January 2016 |
Junior Member |
|
|
Johannes,
Thanks for the prompt response, I am using some thing like below to migrate
String nsURI = ReleaseUtils.getNamespaceURI(resourceURI);
final Migrator migrator = MigratorRegistry.getInstance().getMigrator(nsURI);
if (migrator != null) {
final Release release = migrator.getRelease(resourceURI).iterator()
.next();
if (!release.isLatestRelease())
migrator.migrateAndSave(Collections.singletonList(resourceURI), release,null, monitor);
Please let me know what additional parameter your are suggesting to pass on save option.. I have been using edapt migrate from 1.1 -> 1.2 , 1.2 ->1.3 .. I never experienced reverse stuff. I am puzzled on why is it happening now.
I dont have any extra save option on my regular save.. and no special resourcefactory set too
Please guide me
[Updated on: Wed, 23 October 2019 14:56] Report message to a moderator
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.01898 seconds