> Actually, problem is because the validation logic is happening
> on the server side and hence spawned on a different worker thread.
That sounds like a very different problem than what you described in your
previous message. But it certainly does present some challenges.
If you need to connect to a server to do some part of the validation, you
do not want to do that at the field level, at least not synchronously.
That would slow things down and it would freeze the UI if you have some
sort of network slowdown or failure.
The easiest solution would be to do these validations at the form level.
When the user presses OK or whatever he does to commit the changes, you
would then do the server-based validations. As an alternative, you could
do these in a background thread and use some sort of indicator in the UI,
such as changing the text color to red, to indicate errors in the values.
> My Event-Dispatch thread needs to wait till this thread returns back as
> it can't save the settings till then.
No, you do not want the Event Dispatch Thread waiting on any process that
is not guarateed to complete quickly. You should consider your validation
to be a "long-running process", so you need to do the validation in a
separate thread.

Signature
Regards,
John McGrath