|Re: Loading XMI fails due to unresolved references that are provided by the LazyLinker when using DS [message #1722041 is a reply to message #1722014]
||Tue, 02 February 2016 12:19
| Jason Pell
Registered: February 2011
This is just an example of the kind of model constructs my company uses in their model, but due to size an IP reasons, I had to create a fairly arbitrary model based on the class Entity modelling examples.|
When I tried to do serialisation to XMI with our real model I encountered a problem with the transient types, so extended the entity modelling to include them.
Christian Dietrich wrote on Tue, 02 February 2016 04:08
you dont move the builtin types to the xmi resource. why not? if they are not in a resource, not even an artifical one, this wont work. this is why in the serialized xmi there are xtext links.
I am not well versed in this particular part of EMF, so I did not realise this was required.
Christian Dietrich wrote on Tue, 02 February 2016 04:13
even if you make the reference untransient (and adopt transientvalueservice instead)
there is only any as type contained in the hidden list
Your suggestion worked a treat at least for this simple example. I added a transient value service and changed the post process ext file to set the built in types and hidden types to transient=false
I was able to serialize to and from XMI just fine
[Updated on: Tue, 02 February 2016 12:26]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01613 seconds