commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedikt Ritter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEANUTILS-474) FluentPropertyBeanIntrospector does not use the same naming algorithm as DefaultBeanIntrospector
Date Thu, 12 Mar 2015 09:04:38 GMT

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

Benedikt Ritter commented on BEANUTILS-474:
-------------------------------------------

Patches welcome! Don't forget to include a junit tests ;-)

> FluentPropertyBeanIntrospector does not use the same naming algorithm as DefaultBeanIntrospector
> ------------------------------------------------------------------------------------------------
>
>                 Key: BEANUTILS-474
>                 URL: https://issues.apache.org/jira/browse/BEANUTILS-474
>             Project: Commons BeanUtils
>          Issue Type: Bug
>          Components: Bean / Property Utils
>    Affects Versions: 1.9.2
>            Reporter: Michael Grove
>            Priority: Minor
>              Labels: naming, property
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> If you have a bean with the methods `URI getURI()` and `void setURI(URI)` the `DefaultBeanIntrospector`
will find the property `URI` with the expected getter and setter.  The `FluentPropertyBeanIntrospector`
will instead find the property `uRI`, which (imo) is incorrect; you end up with a duplicate
of the same property when using the two introspectors together.  
> `DefaultBeanIntrospector` uses `Introspector#decapitalize` whereas `FluentPropertyBeanIntrospector`
uses it's internal method `propertyName` which is where the difference arises from.  `FluentPropertyBeanIntrospector`
should just use `Introspector#decapitalize` when generating names.



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

Mime
View raw message