DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32207>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32207


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




------- Additional Comments From [EMAIL PROTECTED]  2005-06-09 07:35 -------
BigDecimal (and BigInteger) are definitely inconsistent with the behaviour of
the other numerical converters. With any other numerical type, passing a null to
the converter will cause a zero-value to be returned. 

In no case will nulls be "preserved" by the converters installed by a default
ConvertUtilsBean.

Fixing BigDecimal and BigInteger to return zero instead of throwing an exception
would potentially break backwards compatibility. And changing all the converters
to return null when passed null is definitely not possible.

So unfortunately I will have to close this as WONTFIX. I have, however, updated
the javadoc on class ConvertUtilsBean to describe more clearly the behaviour of
the default converter setup when handling nulls.

Please note, however, that you can register your own set of converters to
replace the default ones, in order to customise the behaviour of data conversion
as you wish.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to