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

[Sebastian Paul <sebastian.paul.ext@xxxxxxxxxxx>]

> On the other side, is it so bad that the UI of the view updates while 
> the wizard is used. Ok, it's not good design, but it doesn't break 
> anything, or?
This is at least uncommon. But as long as your UI correctly tracks the 
model state, rolling back should bring the UI into the state before the 
wizard was started.
> I can't really follow with your last part. Committing what 
> transaction? That of the wizard? I guess you mean as you use the 
> MemStore, the document is not persisted (in a database or file). Right?
> In my setup for example a document is saved as I use the DerbyStore. 
> When I commit a transaction (when the wizard is finished), the model 
> is stored to the database. Or do you mean something different?
Yes exactly, committing does not mean saving in my example app. There is 
no persistence at all, yet. The Store just holds the current state of 
the model.
When persistence should be done with CDO, too, my approach seems not to 
be appropriate.

I' wondering whether an application can deal with two sessions - one 
session with MemStore and one Session for the DbStore. Work is done on 
the MemStore session, and saving/persisting is done on the DbStore 
session. This would be similar to a nested transaction, where the outer 
transaction saves the model, while inner transactions encapsulate things 
like wizards. But I have no idea how to pass the final changes to the 
DbStore.

Sebastian