[
https://issues.apache.org/jira/browse/DBUTILS-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14220148#comment-14220148
]
Carl Hall commented on DBUTILS-121:
-----------------------------------
Using the attached patch, my implementation looks like this:
{code}
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;
}
{code}
> Allow influencing the setter method used
> ----------------------------------------
>
> Key: DBUTILS-121
> URL: https://issues.apache.org/jira/browse/DBUTILS-121
> 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
(v6.3.4#6332)
