Eclipse Community Forums: Newcomers » EMF in-memory repo ?

Help

Home

Home » Newcomers » Newcomers » EMF in-memory repo ?

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

EMF in-memory repo ? [message #1101940]

Thu, 05 September 2013 06:04

John D

Messages: 6
Registered: August 2013

Junior Member

Hi,

I have a usecase where I create a lot of EMF objects (not belonging to the same resourceset) in memory. I need to store these objects in some kind of a repo(something like a hashmap) in memory so that the objects could be retrieved later. Currently I store the objects in a hashmap. I am sure there must be better way to do this.

Could someone please point me in the right direction to solve this in a right way ?

Thanks,
John D

Report message to a moderator

Re: EMF in-memory repo ? [message #1101975 is a reply to message #1101940]

Thu, 05 September 2013 07:05

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

John,

It's better to ask EMF questions on the eclipse.tools.emf forum. More
comments below.

On 05/09/2013 8:04 AM, John D wrote:
> Hi,
> I have a usecase where I create a lot of EMF objects (not belonging to
> the same resourceset) in memory. I need to store these objects in some
> kind of a repo(something like a hashmap) in memory so that the objects
> could be retrieved later.
How are they retrieved? I.e., what's the key for retrieving them? Are
they contained by a resource? Why do you need to do this?
> Currently I store the objects in a hashmap. I am sure there must be
> better way to do this.
What do you consider not-so-deal about your current approach?
>
> Could someone please point me in the right direction to solve this in
> a right way ?
It's not really clear the nature of your problem or the purpose of your
solution...

The method
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.delegatedGetResource(URI,
boolean) might be useful for specializing your resource set to delegate
to some "global" resource set that contains resources you wish to share
across many resource sets. Be careful with such an approach though,
e.g., if you allow such shared objects to be modified in an editor
that's likely to cause problems...

> Thanks, John D

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

Report message to a moderator