-
Bug
-
Resolution: Fixed
-
P4
-
5.0
-
b46
-
generic
-
generic
In java.beans.PropertyChangeEvent spec is written:
*------------------------------------------------
public void fireIndexedPropertyChange(String propertyName,
int index,
boolean oldValue,
boolean newValue)
Report a boolean bound indexed property update to any registered listeners.
No event is fired if old and new values are equal and non-null.
*----------------------------------------------------------
public void fireIndexedPropertyChange(String propertyName,
int index,
int oldValue,
int newValue)
Report an int bound indexed property update to any registered listeners.
No event is fired if old and new values are equal and non-null.
*--------------------------------------------------------
But int or boolean newValue and oldValue can't be null or non-null.
"... and non-null. " seems to be redundant.
###@###.### 2005-05-11 09:34:15 GMT
*------------------------------------------------
public void fireIndexedPropertyChange(String propertyName,
int index,
boolean oldValue,
boolean newValue)
Report a boolean bound indexed property update to any registered listeners.
No event is fired if old and new values are equal and non-null.
*----------------------------------------------------------
public void fireIndexedPropertyChange(String propertyName,
int index,
int oldValue,
int newValue)
Report an int bound indexed property update to any registered listeners.
No event is fired if old and new values are equal and non-null.
*--------------------------------------------------------
But int or boolean newValue and oldValue can't be null or non-null.
"... and non-null. " seems to be redundant.
###@###.### 2005-05-11 09:34:15 GMT