You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2014/10/07 22:25:34 UTC

[jira] [Resolved] (BEANUTILS-465) Indexed List Setters no longer work

     [ https://issues.apache.org/jira/browse/BEANUTILS-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliver Heger resolved BEANUTILS-465.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.3

I created a unit test based on your test class and committed your patch in revision 1629975. Many thanks!

Do you want to be added to the contributors section in pom.xml?

> 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
>             Fix For: 1.9.3
>
>         Attachments: BeanUtilsBean.java.patch, 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)