This issue contains a patch that will change the behavior of DefaultValueParser. All of the methods wheich would return an object type would return NULL is the value is not prsent. Currently methods such as getInteger(key) will return an Integer with a value of 0. Methods such as getInt(key) would remain unchanged.
Since this will change the current behavior in a way that could break existing code, I wanted to get everyone else's opinion on it before appling the patch. One other thing, should this also be applied to the 2.2.1 verion as well as 2.3? > -----Original Message----- > From: Scott Eade [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 24, 2003 8:44 AM > To: Scott Eade > Cc: [EMAIL PROTECTED] > Subject: [SOURCE] Issue #TTWS38 - Update ValueParsers to > return null when appropriate > > > You can view the issue detail at the following URL: > <http://scarab.werken.com/scarab/issues/id/TTWS38> > > Type : Patch > Issue Id : TTWS38 > Reported by: Scott Eade > [EMAIL PROTECTED] - ([EMAIL PROTECTED]) > > Details: > > Platform: All > Operating system: windows 2000 > Summary: Update ValueParsers to return null when appropriate > Description: For some Object return types > ValueParser/BaseValueParser currently return Object > equivalents of uninitialised primitive values when the keys > are not included in the underlying HashTable. To be more > useful and to be consistent with the other Object types, the > Bool, BigDecimal and Integer return types should return null > when the key is not found. > Status: New > Priority: High > > > -- > To unsubscribe, e-mail: > <mailto:turbine-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
