Patterns for JavaBean and GUI interaction

Question

Forgive the newbie feel to this question.
I have a number of JavaBeans-compliant classes for several entities that will end up persisted. I can use any of a number of technologies to persist these to a database or serialize to disk. If, now, I want to add a GUI for interaction with these beans, it seems there are at least a couple of ways to go. The first is to encapsulate the code for doing so in the bean itself, perhaps extending JComponent. The second is to make a "view" for each Bean that uses multiple PropertyChangeListeners(?) to/from the Bean to maintain state within the bean. The latter seems to separate the model from the view better.
I am curious from a design point-of-view how best to go about solving this generic problem. I have done similar things in other languages with varying degrees of satisfaction with the resulting maintainability of the resulting product. So, I am aiming for something that balances complexity with maintainability and flexibility (to change a view or to change the underlying model).
Thanks
Sean

Answer 1

Well, thanks for your reply. My program is kind of large to be entered online.
In any case, I tried again with the synchronized keyword for the method that accesses the shared member (between the two threads) and things look good now and I do not see the problem I was seeing earlier.
One question I have is w.r.t the usage of the synchronized keyword - can this be used for methods as well as members of a class ?
I mean for example, if I have a static variable declared in a class and this static needs to be accessed outside the declaring class in a different thread, then should this static member be declared as synchronized too?
Thanks.