Eclipse Community Forums: EMF » How to serialze intrinsic ids as attributes?

Help

Home

Home » Modeling » EMF » How to serialze intrinsic ids as attributes?

Show: Today's Messages :: Show Polls :: Message Navigator

How to serialze intrinsic ids as attributes? [message #1488065]

Wed, 26 November 2014 09:33

Jan Rosczak

Messages: 53
Registered: July 2009
Location: Hamburg, Germany

Member

Hello,

I am trying to convert a legacy xml format into an EMF model.
The one problem I face is serializing local references. I have conditions which can reference other conditions.

EMF would serialize this as:

<condition varName="cond1"/>
<condition varName="cond2">
  <condition>cond1</condition>
</condition>

But I need to parse something like that:

<condition varName="cond1"/>
<condition varName="cond2">
  <condition vaName="cond1"/>
</condition>

Is there a way to tell EMF to store a reference not as content of an element but as an attribute of that element?

Thanks
Jan R.

Report message to a moderator

Re: How to serialze intrinsic ids as attributes? [message #1488079 is a reply to message #1488065]

Wed, 26 November 2014 09:48

Ed Merks

Messages: 33217
Registered: July 2009

Senior Member

Jan,

Comments below.

On 26/11/2014 10:33 AM, Jan Rosczak wrote:
> Hello,
>
> I am trying to convert a legacy xml format into an EMF model.
> The one problem I face is serializing local references. I have
> conditions which can reference other conditions.
>
> EMF would serialize this as:
>
> <condition varName="cond1"/>
> <condition varName="cond2">
> <condition>cond1</condition>
> </condition>
That seems surprising. Is this using an XMIResourceImpl?
>
>
> But I need to parse something like that:
>
> <condition varName="cond1"/>
> <condition varName="cond2">
> <condition vaName="cond1"/>
That will be a challenge. I doubt the legacy format itself was defined
with XML Schema...
> </condition>
>
>
> Is there a way to tell EMF to store a reference not as content of an
> element but as an attribute of that element?
org.eclipse.emf.ecore.xmi.XMLResource.OPTION_USE_ENCODED_ATTRIBUTE_STYLE
though I have to wonder what options you've set that's making it
serialize this way. It's not what I'd expect by default (for an XMI
serialization). If you're using an XML serialization using a resource
factory like the one generated for an XML Schema-based model, an
extended metadata annotation for the reference feature as produced by
org.eclipse.emf.ecore.util.ExtendedMetaData.setFeatureKind(EStructuralFeature,
int) with org.eclipse.emf.ecore.util.ExtendedMetaData.ELEMENT_FEATURE
should do the trick, but the serialization you show above would need
specialized code to handle and produce...
>
> Thanks
> Jan R.

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator