|ExtendedMetadata unmapped structuralFeature [message #991567]
||Wed, 19 December 2012 18:40
| Ruben Faelens
Registered: December 2012
I am working on backwards compatibility using Ecore2XML files. So far, this is going great.|
However, I now have the following mapping:
* feature1 (derived)
OldFoo <-> NewFoo
OldFoo::feature1 <-> NewFoo::feature2
UNMAPPED <-> NewFoo::feature1
I expected OldFoo::feature1 to be mapped correctly to OldFoo::feature2. Instead, the ExtendedMetaData object tries to map NewFoo::feature1 first. Instead of marking it 'unmapped', a fallback maps it to OldFoo::feature1, based on similarity on containingClass and feature name.
How can I make the ExtendedMetadata execute the above mapping correctly?
[Updated on: Wed, 19 December 2012 18:49]
Report message to a moderator
|Re: ExtendedMetadata unmapped structuralFeature [message #991974 is a reply to message #991969]
||Thu, 20 December 2012 15:21
| Ed Merks
Registered: July 2009
Yes, that's a nice way and it lets you do arbitrarily complex things...
On 20/12/2012 7:14 AM, Ruben Faelens wrote:
> Instead of using the ExtendedMetadata solution, I ended up modifying
> EcoreUtil.Copier to integrate with the Ecore2Ecore file.
> This way, backwards compatibility is much more stable; it is not
> dependent on XML serialization options but just works.
> Thank you for the help though.
Powered by FUDForum
. Page generated in 0.04832 seconds