[ 
https://issues.apache.org/jira/browse/BEANUTILS-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14155438#comment-14155438
 ] 

Oliver Heger commented on BEANUTILS-465:
----------------------------------------

Do you have a proposal how to solve this problem?

The stricter validation performed by these converters is also enforced by the 
introduction of generics; the old behavior is probably no longer possible 
because it would require returning an object which is incompatible with the 
expected return type. One could even argue that the old behavior was 
problematic because of this.

I guess the change in behavior is related to the issues BEANUTILS-445 and 
BEANUTILS-446.

> Indexed List Setters no longer work
> -----------------------------------
>
>                 Key: BEANUTILS-465
>                 URL: https://issues.apache.org/jira/browse/BEANUTILS-465
>             Project: Commons BeanUtils
>          Issue Type: Bug
>          Components: ConvertUtils & Converters
>    Affects Versions: 1.9.2
>            Reporter: Daniel Atallah
>         Attachments: BeanUtilsTest.java
>
>
> After upgrading to commons-beanutils 1.9.2 from 1.8.3, I ran into a bug where 
> indexed List setters no longer work.
> Per the documentation at:
> http://commons.apache.org/proper/commons-beanutils/javadocs/v1.9.2/apidocs/org/apache/commons/beanutils/package-summary.html
> " As an extension to the JavaBeans specification, the BeanUtils package 
> considers any property whose underlying data type is java.util.List (or an 
> implementation of List) to be indexed as well."
> This no longer appears to be an accurate statement.
> The cause appears to be more strict validation in both 
> org.apache.commons.beanutils.converters.StringConverter.convertToType() and 
> in org.apache.commons.beanutils.converters.AbstractConverter.
> There is now an explicit cast to the target type, which throws an Exception 
> instead of the previous behavior of simply returning the input value 
> unconverted.
> I'll attach a test case that works with 1.8.3, but no longer works with 1.9.2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to