thanks for sharing. My setup currently uses only one transaction for the
whole lifecycle of my application. I wonder now a bit if I will run in
trouble with that.
As the wizard is modal (and therefore the user can't interact with the
view and the wizard at the same time), another option would be to to
tell the view to stop listening to model changes (by removing the
eAdapter or whatever) while the wizard is running.
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?
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?