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

Chris Wells updated BEANUTILS-159:
----------------------------------
    Reporter: Henning Schmiedehausen  (was: Henning Schmiedehausen)

> beanutils 1.7.1 and properties with different types and the same name
> ---------------------------------------------------------------------
>
>                 Key: BEANUTILS-159
>                 URL: https://issues.apache.org/jira/browse/BEANUTILS-159
>             Project: Commons BeanUtils
>          Issue Type: Bug
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Henning Schmiedehausen
>            Priority: Major
>         Attachments: ASF.LICENSE.NOT.GRANTED--testcase.zip
>
>
> Attached you will find a test case for beanutils, where I have the
> following problem:
> Consider a bean which has three properties, one simple, one indexed
> and one mapped. As long as these have three different names, they differ
> in the names of their getters and setters (e.g. with an Integer property):
> e.g.
> Integer getSimpleProperty() / void setSimpleProperty(Integer)
> Integer getIndexedProperty(int) / void setIndexedProperty(int, Integer)
> Integer getMappedProperty(String) / void setMappedProperty(String, Integer)
> Now it is still possible, that a bean has three different properties
> (simple, indexed. mapped) with the *same* name:
> Integer getProperty() / void setProperty(Integer)
> Integer getProperty(int) / void setProperty(int, Integer)
> Integer getProperty(String) / void setProperty(String, Integer)
> And for this case, BeanUtils does not work (this is an actual bug that
> I've found in a program where a simple and an indexed property of the
> same name exist). 
> Attached are test cases for this. MultiBean is a bean where all three
> properties have the same name and MultiPropertyBean has properties
> with different names. The TestCases both use the same parent class
> (BeanTester), so the behaviour should be similar for both
> beans. However, it is not. MultiPropertyBeanTestCase succeeds,
> MultiBeanTestCase fails.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to