In our application, we send our form object off for asynchronous calculation and, when it returns, we update the form with the new form object. This works very well. The problem is that when a user is in the process of editing a form field when the calculation returns, we're currently blowing away their work. Obviously not good.
One thought I have on this is, when the calculation returns, to register a VetoablePropertyChangeListener for the field with focus (assuming it's in my form and a bound control) and veto the update request, the drop the listener. Seems kind of hokey, but I was thinking that it would keep the field from getting updated nicely. However, with the SwingFormModel I can't add a veto listener.
Anyone have any thoughts on this? I'm going to keep trying other things, but I thought I'd enlist the help of the experts.