On Wednesday 10 December 2003 22:35, Leo Sutic wrote: > When DefaultConfiguration.setAttribute(key,value) is called with a null > as the value parameter, it should... > > 1. ...throw a NullPointerException. > > 2. ...throw an IllegalArgumentException. > > 3. ...act as if called with DefaultConfiguration.setAttribute( key, "" > ). > I.e. set the attribute to the empty string. > > 4. ...remove the attribute if it exists. > > My vote is for 4. Why? Because setValue(null) removes any existing > value from a DefaultConfiguration.
1. [ ] 2. [ ] 3. [ ] 4. [ x ] Also, most folks are used to that behavior in HashMap. Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
