Eclipse Community Forums: EMF » Side effects of setIntrinsicIDToEObjectMap

Home » Modeling » EMF » Side effects of setIntrinsicIDToEObjectMap

Side effects of setIntrinsicIDToEObjectMap [message #489128]

Thu, 01 October 2009 11:09

Eclipse User

So now after I got that HashMap speed up the loading it seem there are
some unwanted side effects.

After removing an element with an ID I could still see that element when
attempting to create a reference to it.

After restarting the workbench and opening the file that reference was
marked invalid as expected. In the same session I removed that file and
created a new one with the same name which now was known to contain the
object again. When opening that file the problems page again opened
claiming the references were invalid although they are not.

I guess these effects result from setIntrinsicIDToEObjectMap. Could I
avoid these effects by deleting or clearing the HashMap after the
resource is loaded or is there something else to tweak.

Thanks and Regards,
Dirk

Re: Side effects of setIntrinsicIDToEObjectMap [message #489140 is a reply to message #489128]

Thu, 01 October 2009 11:25

Eclipse User

Dirk,

Dirk Hoffmann wrote:
> So now after I got that HashMap speed up the loading it seem there are
> some unwanted side effects.
>
> After removing an element with an ID I could still see that element
> when attempting to create a reference to it.
Isn't detachedHelper kicking in during the removal?
>
> After restarting the workbench and opening the file that reference was
> marked invalid as expected. In the same session I removed that file
> and created a new one with the same name which now was known to
> contain the object again. When opening that file the problems page
> again opened claiming the references were invalid although they are not.
Doesn't it kick in during unload too?
>
> I guess these effects result from setIntrinsicIDToEObjectMap. Could I
> avoid these effects by deleting or clearing the HashMap after the
> resource is loaded or is there something else to tweak.
Yes, but I'm not sure why you're seeing these problems...
>
> Thanks and Regards,
> Dirk

Re: Side effects of setIntrinsicIDToEObjectMap [message #489252 is a reply to message #489140]

Fri, 02 October 2009 02:24

Eclipse User

Ed Merks schrieb:
> Dirk,
>
> Dirk Hoffmann wrote:
>> So now after I got that HashMap speed up the loading it seem there are
>> some unwanted side effects.
>>
>> After removing an element with an ID I could still see that element
>> when attempting to create a reference to it.
> Isn't detachedHelper kicking in during the removal?

What's that supposed to be? I did a full text search for
"detachedHelper" but didn't get anything. Is that something that came in
after version 2.2.3?

>>
>> After restarting the workbench and opening the file that reference was
>> marked invalid as expected. In the same session I removed that file
>> and created a new one with the same name which now was known to
>> contain the object again. When opening that file the problems page
>> again opened claiming the references were invalid although they are not.
> Doesn't it kick in during unload too?
>>
>> I guess these effects result from setIntrinsicIDToEObjectMap. Could I
>> avoid these effects by deleting or clearing the HashMap after the
>> resource is loaded or is there something else to tweak.
> Yes, but I'm not sure why you're seeing these problems...
>>
>> Thanks and Regards,
>> Dirk

Previous Topic:	[TENEO] Associate a GMF/EMF model with an Eclipse project
Next Topic:	EcoreUtil.delete()...

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Nov 06 13:51:59 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter