[news.eclipse.tools.emf] Re: [CDO] CDOSavePoint and rollback question

[Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>]

Hi,

I'm using EditingDomain and the CommandStack for this kind of because it
makes my Code free from CDO dependencies (and sometimes I want to undo
changes step by step instead of a big rollback) but the CDO
implementation is also working very nice.

Tom

Kai Schlamp schrieb:
> Hello Simon,
> 
> thank you for the crystal clear answer and the nice improvement of my
> scenario. Yes, it was absolutely what I meant.
> Comments below.
> 
>>> Now when client 1 rolls back to the save point (without transmitting
>>> anything before), all changes in Element1 (made by client 1) and
>>> Element2 (by client 2) are undone.
>> False, setSavePoint only apply the changes made locally. in this case
>> only element.setName("sss") will be rolled back.
>>
>>> Is that right? If yes, is there a way to only roll back those changes
>>> that were done by client 1 itself (in this case only undo Element1
>>> changes).
>> If this is what you observed it is a problem... it should not be like
>> that. Did you experienced such things ?
> 
> No, I just liked to know in advance how the rollback behaves. And it's
> perfect in my case that it does it the way you described.
> 
>> When you said you had two clients.... I assumed you had 2
>> transactions... is it the case?
> 
> Yes, that is what I meant. I am designing my app at the moment for
> single user, but keep a multi user setup in the back of my mind.
> CDO makes this very easy, but it also has many advantages for single
> user applications.
> I use the rollback for example to undo all changes of a bigger model
> that is modified by a large wizard dialog when the cancel button is
> pressed.
> 
> Best regards,
> Kai