The page <a href="http://wiki.squeak.org/squeak/2636" target="_blank">http://wiki.squeak.org/squeak/2636</a> says:<br><br>&quot;Thankfully, Magma will detect this conflict and signal a
MagmaCommitError back to user 2. This is because she tried to change an
object that was changed by User 1 since she began her transaction,
invalidating her changes. The failed result object has the challenging
objects that were in conflict (Object A) and the name of each user who
changed them (User 1). Additionally, User 2 can now see the new Object
A, as changed by User 1, because her commit attempt caused a crossing
of a transaction boundary. <br>
<br>
At this point, User 2 no longer has a transaction. She must reapply her changes under a new transaction, if appropriate. &quot;<br><br>Now I have a Debugger with a MagmaCommitError. As you can see from the attachement, the User2 session still has a transaction, so I have some questions:<br>
<br>-Is this transaction invalid in some way? I&#39;ve observed some possibly relevant protocol here (#restore? #changedObjects?)<br><br>-Supposing that it&#39;s appropiate to reapply User2 changes, do I have the chance to do it from the Debugger? <br>
<br>-If the Debugger isn&#39;t useful at this stage, how to apply the User2 changes?<br><br>Cheers,<br><br>Hernan<br><br><br>