Hi Mark, Am Freitag, den 03.02.2006, 12:19 +0100 schrieb Mark Wielaard: > Hi, > > This should get rid of the last regression that builder is complaining > about (technically it isn't a regression, the test got changed to not > expect a NullPointerException). It simply changes the Hashtable that > doesn't allow null keys to a HashMap. The class wasn't thread-safe in > the first place.
Now that you say it, the point of the SwingProperyChangeSupport class is to be not thread safe. It's even specified in the API docs. So we should probably remove all the synchronization from this class. In Swing it is ok to be not thread safe, since normally all operations should be performed from the Event dispatch thread. /Roman
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
