🚀 go-pugleaf

dnoyeB > schrieb in Nachricht <3b3cee8f$1_2@dnews>...
>When I fire a property veto exception it requires a property change object
>within it.
>
>Now since this change is vetoed, should oldvalue and newvalue both be
>oldvalue?? since I really am not setting the newvalue?

you don't create a new PropertyChangeEvent, rather you throw a
PropertyVetoException inside a vetoableChange method of a
VetoableChangeListener implementation. You get the PropertyChangeEvent as a
parameter, inspect the property change and fire a PropertyVetoException if
you are not happy with the change. You send the original PropertyChangeEvent
with your exception.

Here's some pseudo code (I have no JDK available at the moment, so don't
mind any syntax errors):

class SomeClass implements VetoableChangeListener {
    ...
    public void vetoableChange(PropertyChangeEvent pce) {
        if (!pce.getNewValue().isWhatYouHadExpected()) {
            throw new  PropertyVetoException("I don't like this new value",
pce);
        }
    }
    ...
}

Torsten