commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (JIRA)" <>
Subject [jira] [Resolved] (DBUTILS-91) Enhance BasicRowProcessor to have row mapping easier to configure
Date Fri, 06 Jul 2012 15:09:35 GMT


Simone Tripodi resolved DBUTILS-91.

       Resolution: Fixed
    Fix Version/s: 1.5
         Assignee: Simone Tripodi

Patch applied, see r1358253, thanks for contributing.

Please, for future patches, remind the following:

 * respect the original file format - no tabs;
 * javadoc was not complete (the new constructor didn't have the argument documented);
 * when adding new methods/constructors, add the {{@since}} tag

> Enhance BasicRowProcessor to have row mapping easier to configure
> -----------------------------------------------------------------
>                 Key: DBUTILS-91
>                 URL:
>             Project: Commons DbUtils
>          Issue Type: Improvement
>    Affects Versions: 1.4
>            Reporter: Stevo Slavic
>            Assignee: Simone Tripodi
>             Fix For: 1.5
>         Attachments: DBUTILS-91.patch
> {{BasicRowProcessor}} by default makes use of {{BeanProcessor}} for mapping result set
row columns to bean property names. {{BeanProcessor}} uses bean property names, and performs
case-insensitive matching of those names to column names.
> Currently {{BasicRowProcessor}} can be configured with custom {{BeanProcessor}} extension
to customize the row mapping, but it gets rather ugly.
> It would be great if {{BeanProcessor}} was configurable with column name to bean property
name strategy. Besides current strategy, DbUtils should also bundle strategy implementation
configurable with a property name to column name (or other way around) map.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message