Cleanup PropertyChangeEvent stuff

Use java.beans.PropertyChangeEvent instead of own implementation. This removes some classes from
SC and removes ambiguities with respect to PropertyChangeEvent handling.
Rename SC's own PropertyVetoException to ConfigPropertyVetoException to show the difference
in usage and implementation. ConfigPropertyVetoException is a subclass of Runtime exception
(intentionally) to simplify handling.

1 files changed, 3 insertions, 3 deletions

diff --git a/src/net/java/sip/communicator/util/swing/SIPCommFrame.java b/src/net/java/sip/communicator/util/swing/SIPCommFrame.java
index e2741f3..3a7c856 100644
--- a/src/net/java/sip/communicator/util/swing/SIPCommFrame.java
+++ b/src/net/java/sip/communicator/util/swing/SIPCommFrame.java
@@ -11,7 +11,7 @@ import java.awt.event.*;
 import java.awt.image.*;
 import java.net.*;
 import java.util.*;
-
+import java.beans.*;
 import javax.swing.*;
 
 import net.java.sip.communicator.service.configuration.*;
@@ -192,7 +192,7 @@ public abstract class SIPCommFrame
         {
             saveSizeAndLocation(this);
         }
-        catch (PropertyVetoException e)
+        catch (ConfigPropertyVetoExceoption e)
         {
             logger
                 .error(
@@ -212,7 +212,7 @@ public abstract class SIPCommFrame
      * <tt>PropertyVetoListener</tt>s.
      */
     static void saveSizeAndLocation(Component component)
-        throws PropertyVetoException
+        throws ConfigPropertyVetoExceoption
     {
         Map<String, Object> props = new HashMap<String, Object>();
         String className