🚀 go-pugleaf

On Sat, 30 Jun 2001 13:08:04 -0400, "CLG" <lamont_gilbert @ 
rigidsoftware.com> wrote:

> I disagree.  I am writing a bean, and I am the one responsible
> for creating the methods.  So i dont have any such objects
> premade and handed to me.  I am the maker in this event. 
> So my question is what should the maker of this object do.

You create the PropertyChangeEvent *before* the veto can occur.
The oldValue property is the previous (actually current) value
of the property, and the newValue property is the proposed new
value for the property.  This event is "fired" at all of the 
VetoableChangeListeners.

The VetoableChangeListeners receive that event in the vetoableChange() 
method, and throw a PropertyVetoException if they do not like the 
proposed change.  The constructor for PropertyVetoException takes a 
PropertyChangeEvent as an argument, which should be passed the same 
value that was passed to vetoableChange() as an argument.

No PropertyChangeEvent should ever be constructed by the listener
that vetoes the property change.

-- 
Regards,

John McGrath [TeamB]

---------------------------------------------------
Before sending me e-mail, please read:
    http://www.JPMcGrath.net/newsgroups/e-mail.html