[BBB-USERS] JTableBinding and the EDT
- From: Ruben Laguna <ruben.laguna@gmail.com>
- To: BBB-USERS <users@betterbeansbinding.kenai.com>
- Subject: [BBB-USERS] JTableBinding and the EDT
- Date: Tue, 19 Jan 2010 23:34:28 +0100
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=XBgn1XuI8TEwdfcJpsTFpTZK3cSPq1Uly8yfqVSzOk2xjpjMe5XGDOHcBphLYEtSjc vyckESH/AlJAwvoREiQ2Vpzom/RQgz6+mBmA3+tCLctSKcIcocLKNatYv36zuU0Dx7FV Z3EUSKEnTrodD36lM5tVO8xeeCl9mevCQx3Do=
Maybe I should have asked the question here before I submitted the issue http://kenai.com/jira/browse/BETTERBEANSBINDING-56...
I guess it's never too late to do it right.
The fact (correct me if I'm wrong): if you have a List<Customer> bound to a JTable (by means of JTableBinding) and those Customer beans get updated in a thread other than the EDT then the changes to the JTable will be made in that thread (so the changes will be outside of the EDT)
Is there anyway to make the JTable to happen in the EDT? (Other than the obvious solution of doing the changes to Customer in the EDT)
As I understand it should be the JTableBinding (via its EntryWrapper) itself the one that ensures that the JTable is updated in the EDT (the patch contained in the issue could be one way of doing it).
Second question: Is BBB still being actively developed/managed? I was checking some of the bug reports in kenai and some bug were reported in June 2009 and they haven't been commented yet.
--
/Rubén
--
/Rubén
|
[BBB-USERS] JTableBinding and the EDT |
Ruben Laguna | 01/19/2010 |
