Download the latest nightly build and test with that. DbUtils 1.0 shipped
with a rather simple bean population implementation that causes this
problem. DbUtils 1.1 will ship with a smarter version that should handle
numbers correctly.
The actual cause of the problem is that Oracle is returning BigDecimal
objects for numeric columns and your bean has an int property so DbUtils
doesn't call the setter method.
David
--- Patrick Hess <[EMAIL PROTECTED]> wrote:
>
> Hi there,
>
> I'm trying at the moment to replace some my JDBC code with DbUtils.
> Currently I have a problem with the BeanHandler. I'm using an Oracle
> 8.1.7 database with thin driver on JDK 1.3 on Windows.
>
> My problem: except with the BeanHandler everything works fine, my
> results are like expected. When using the BeanHandler all numeric fields
>
> are 0 while string values are set. I tried different variations of the
> bean like using int, long, Integer or Long for the numeric properties.
>
> I didn't found any references to such a problem on google so I think I
> did some mistake. Can anyone give me a hint to find out what's going on?
>
> Thanks in advance, have a nice day
> Patrick
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
