commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <>
Subject [jira] Commented: (BEANUTILS-228) [beanutils] ConvertUtilsBean: register converter for specific property
Date Wed, 15 Nov 2006 01:06:38 GMT
    [ ] 
Henri Yandell commented on BEANUTILS-228:

I wonder if the destinationClass is necessary in this API. It seems that the user will get
all they need with:

register(Converter, Class beanClass, String propertyName).


> [beanutils] ConvertUtilsBean: register converter for specific property
> ----------------------------------------------------------------------
>                 Key: BEANUTILS-228
>                 URL:
>             Project: Commons BeanUtils
>          Issue Type: Improvement
>          Components: ConvertUtils & Converters
>    Affects Versions: 1.5
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Michael Schuerig
>            Priority: Minor
>             Fix For: 1.8.0
> Currently, converters are selected only based on the class to which they 
> convert objects. In general this works pretty well, but I've encountered 
> cases, where this doesn't work out.  
> For example, I'm using java.util.Date objects to represent points and 
> intervals in time that are not completely specific, such as day of the week 
> and month. Now I can easily write a Converter that uses SimpleDateFormat to 
> convert string representations of these dates ("Mon", "Feb") to Date objects.  
> When I register one of these converters with ConvertUtils(Bean), though, it 
> preempts any conversion to Date. Something I clearly don't want as I have to 
> deal with different kinds of dates. 
> As a solution, I'd like to be able to register a converter for a specific 
> property of a bean class, with a method this 
> ConvertUtilsBean#register(Converter converter, java.lang.Class 
> destinationClass, java.lang.Class beanClass, java.lang.String propertyName) 
> Michael

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message