Undo with Memento pattern vs swing undo

Question

I was tempted to add this question to the end of http://forum.java.sun.com/thread.jsp?forum=425&thread=440740&tstart=0&trange=15 but I've had a poor response in the past by adding a question to the end of an existing thread.
I am working on a project with a rather poor implementation of undo where every Action has to extend an UndoableAction and a copy of the Action itself is stored on the undo queue. This gives me the following problems -
1. Only Actions are undoable, not events such as scolling the display area.
2. We can't make use of an other Action hierarchy other than one with an UndoableAction ancestor.
I'm familiar with the idea of implementing undo/redo using the memento pattern.
My plan is to modify this code so that Actions record current state in a Memento and store that memento in an undo queue instead. Events such as scrolling can then create and store mementos also.
In my plans to implement this someone brought up the swing undo mechanism. I've had little success in finding how to implement swing undo on anything other than a simple text field. It also seems to be something that is based around the control rather than the model.
We have various complex models to keep in synch plus several views onto those models. It seems simpler to me to generate mementos on Actions that effect the model (at least it's something I understand). When a memento gets undone all views listening to model changes will update anyway.
Can anyone see an argument to use swing undo in preference? If so can anyone point me to a better example for implementing swing undo on anything other than text edit controls.
Thanks
Bob.

Answer 1

I don't know much about the Swing undo but it seems unlikely that it would handle anything complex. It would only be able to keep track of changes in the graphical representation of you data, not the model behind it.