Eclipse Community Forums: EMF » [CDO] limitations on what to program in statechange handler?

Help

Home

Home » Modeling » EMF » [CDO] limitations on what to program in statechange handler?

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

[CDO] limitations on what to program in statechange handler? [message #756733]

Mon, 14 November 2011 20:46

Ronald Krijgsheld

Messages: 41
Registered: November 2010

Member

Hello,

I found that the following does not work. As a side effect of an CDO
object going to TRANSIENT state we remove some other CDO objects. It
looks like that is not possible if that object is a child of the CDO
object that went to transient state.

What effectively happens is that during a detach process our client code
starts detach process in the objectStateChanged(). But the outer detach
process has already build up some state to remove all children. if the
inner process removes an object that is already in part of the outer
detach, the outer detach will fail because some of the objects to detach
already have been detached an have no id anymore.

Are we using the objectStateChanged() in a wrong way? are the
limitations on what is allowed to do within this method?

Thanks,

Ronald

Report message to a moderator

Re: [CDO] limitations on what to program in statechange handler? [message #756799 is a reply to message #756733]

Tue, 15 November 2011 07:21

Eike Stepper

Messages: 6682
Registered: July 2009

Senior Member

Hi Ronald,

As I'm currently with a customer I can not dig into your issue before next week. In the mentime you could try to use a
CDOTransactionHandler1. If that doesn't work pplease submit a bugzilla to remind me...

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Am 14.11.2011 21:46, schrieb Ronald Krijgsheld:
>
> Hello,
>
> I found that the following does not work. As a side effect of an CDO object going to TRANSIENT state we remove some
> other CDO objects. It looks like that is not possible if that object is a child of the CDO object that went to
> transient state.
>
> What effectively happens is that during a detach process our client code starts detach process in the
> objectStateChanged(). But the outer detach process has already build up some state to remove all children. if the
> inner process removes an object that is already in part of the outer detach, the outer detach will fail because some
> of the objects to detach already have been detached an have no id anymore.
>
> Are we using the objectStateChanged() in a wrong way? are the limitations on what is allowed to do within this method?
>
> Thanks,
>
> Ronald
>

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator

Previous Topic:	[CDO] org.eclipse.emf.cdo.util.ObjectNotFoundException dangling EReference?
Next Topic:	Teneo - Map issue

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 23:05:27 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter