commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Hall (JIRA)" <>
Subject [jira] [Commented] (DBUTILS-121) Allow influencing the setter method used
Date Thu, 20 Nov 2014 22:40:33 GMT


Carl Hall commented on DBUTILS-121:

Using the attached patch, my implementation looks like this:

  protected Method findWriteMethod(Object target, PropertyDescriptor prop, Object value) {
    Method method;
    try {
      method = target.getClass().getMethod(prop.getWriteMethod().getName(), value.getClass());
    } catch (NoSuchMethodException e) {
      method = prop.getWriteMethod();
    return method;

> Allow influencing the setter method used
> ----------------------------------------
>                 Key: DBUTILS-121
>                 URL:
>             Project: Commons DbUtils
>          Issue Type: Bug
>    Affects Versions: 1.6
>            Reporter: Carl Hall
>         Attachments: dbutils-121.patch
> I have cases where the field in a bean doesn't quite match the column it is stored as.
 e.g. {{Timestamp}} in the database but {{org.joda.DateTime}} in the bean.  It would be nice
to allow the bean processor to have influence over which setter method is used, so that a
setter can take a parameter that's the type of the database column but convert it to the internally
stored type.

This message was sent by Atlassian JIRA

View raw message