JDK-4985020 : Named property methods need spec for when propertyName is null
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.beans
  • Affected Version: 5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2004-01-28
  • Updated: 2017-05-16
  • Resolved: 2004-03-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 b43Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Description
This bug is filed to track an issue brought up in bugs 4937059 and 4937062.  The issue is with PropertyChangeListeners for named properties.  Methods which take a property name should specify what happens when a null String is passed in.  Such methods are:

addPropertyChangeListener(String propertyName,
                          PropertyChangeListener listener)

removePropertyChangeListener(String propertyName,
                             PropertyChangeListener listener)

getPropertyChangeListeners(String propertyName)

hasListeners(String propertyName)

This applies to the following classes:

java.beans.PropertyChangeSupport
java.beans.VetoableChangeSupport
java.beans.beancontext.BeanContextChildSupport

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta2 FIXED IN: tiger-beta2 INTEGRATED IN: tiger-b43 tiger-beta2
14-06-2004

EVALUATION Also applies to methods: add/removeVetoableChangeListener in BeanContextChildSupport. ###@###.### 2004-02-17 Requires slight change - would be best to do for Tiger. ###@###.### 2004-02-23
17-02-2004