Character wasn't forgotten; it wasn't included because ResultSet doesn't
provide a getChar() method. IMO, BasicColumnProcessor should not start
adding custom logic for types not supported directly by ResultSet getters.
It would be simple to subclass BasicColumnProcessor and override the
process() method to support characters.
David
--- "Rafael U. C. Afonso" <[EMAIL PROTECTED]> wrote:
> Hello again:
>
> I think that I know cause of my bug.
> In process() mehtod in
> BasicColumnProcessor a column in
> ResultSet is converted in its
> apropriate type (like Integer,
> Boolean, Float, etc). But Character
> classs was "forgotten". So it is
> necessary include these lines:
>
> } else if
> (propType.equals(Character.TYPE) ||
> propType.equals(Character.class)) {
> return new
> Character(rs.getString(index).charAt(0));
> } else {
>
> I did not tested this but I think that
> it works.
>
> Thanks,
>
> Rafael Ubiratam Clemente Afonso
> [EMAIL PROTECTED]
> ---------------------------------
> Where is Debug?
> Debug is on the Table!
>
>
> ---
> Acabe com aquelas janelinhas que pulam na sua tela.
> AntiPop-up UOL - � gr�tis!
> http://antipopup.uol.com.br
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
