Eclipse Community Forums: EMF » Overriding persistence behaviour of an EMF resource

Help

Home

Home » Modeling » EMF » Overriding persistence behaviour of an EMF resource

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

Overriding persistence behaviour of an EMF resource [message #694035]

Thu, 07 July 2011 16:59

saurav sarkar

Messages: 428
Registered: July 2009

Senior Member

Hi,

In EMF we have seen the attributes of the parent object get persisted first then the subclass attributes.
I am just taking XML as an use case.

During the save of any XML resource, I have seen the XMLSaveImpl saves the features of the classes.These features are retrieved by getEAllStructuralFeatures() of any EClass and this list is populated by putting the super type attributes first.
Same we see in the toString() implementation of any object.

Could these behaviour be somehow overriden or changed such that the sublcass attributes are persisted first ?.

cheers,
Saurav

My Blog http://codifyit.blogspot.com/
Follow me: http://twitter.com/sauravs

[Updated on: Thu, 07 July 2011 17:00]

Report message to a moderator

Re: Overriding persistence of an EMF resource [message #694057 is a reply to message #694035]

Thu, 07 July 2011 17:40

Ed Merks

Messages: 33137
Registered: July 2009

Senior Member

Saurav,

Comments below.

On 07/07/2011 10:00 AM, saurav wrote:
> Hi,
>
> In EMF we have seen the attributes of the parent object get persisted
> first then the subclass attributes.
> I am just taking XML as an use case.
Generally they'll be done in the order in which they appear in
EClass.eAllStructuralFeatures.
>
> During the save of any XML resource, I have seen the XMLSaveImpl saves
> the features of the classes.These features are retrieved by
> getEAllStructuralFeatures() of any EClass and this list is populated
> by putting the super type attributes first.
Yep.
> Same we see in the toString() implementation of any object.
>
> Could these behaviour be somehow overriden or changed such that the
> sublcass attributes are persisted first ?.
No. Though you could specialize the Lookup.listFeatures in combination
with OPTION_USE_CACHED_LOOKUP_TABLE.
>
> cheers,
> Saurav
>
>

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

Report message to a moderator