-
Bug
-
Resolution: Fixed
-
P2
-
7
-
b38
-
generic
-
generic
-
Not verified
The spec on the method java.beans.VetoableChangeSupport.fireVetoableChange states:
===
public void fireVetoableChange(String propertyName,
Object oldValue,
Object newValue)
throws PropertyVetoException
Report a vetoable property update to any registered listeners. If anyone vetos the change, then fire a new event reverting everyone to the old value and then rethrow the PropertyVetoException.
===
But the fireVetoableChange no longer fires a new event to all listeners, if a listener vetos the change. The spec should accommodate the behavior change.
Note: VetoableChangeSupport contains 4 overloaded methods fireVetoableChangeXXX with similar behavior.
This spec issue is probably caused by the fix for 5004188 "Refactor listener management in [Property|Vetoable]ChangeSupport.java"
===
public void fireVetoableChange(String propertyName,
Object oldValue,
Object newValue)
throws PropertyVetoException
Report a vetoable property update to any registered listeners. If anyone vetos the change, then fire a new event reverting everyone to the old value and then rethrow the PropertyVetoException.
===
But the fireVetoableChange no longer fires a new event to all listeners, if a listener vetos the change. The spec should accommodate the behavior change.
Note: VetoableChangeSupport contains 4 overloaded methods fireVetoableChangeXXX with similar behavior.
This spec issue is probably caused by the fix for 5004188 "Refactor listener management in [Property|Vetoable]ChangeSupport.java"
- relates to
-
JDK-5004188 Refactor listener management in [Property|Vetoable]ChangeSupport.java
-
- Resolved
-
-
JDK-4425885 java.beans.VetoableChangeSupport.fireVetoableChange incorrectly handles vetos.
-
- Closed
-