[jira] [Updated] (BEANUTILS-425) Support customization of introspection mechanism

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] [Updated] (BEANUTILS-425) Support customization of introspection mechanism

Peter Lee (Jira)

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

Oliver Heger updated BEANUTILS-425:

    Attachment: beanutils-425.patch

Added a new patch incorporating most of the suggested improvements. Some Java 5 features were added, too.

Regarding code coverage of {{DefaultBeanIntrospector}}: Cobertura shows a coverage of about 82%. This is not too high, but the missing lines are mainly related to exception handling and therefore hard to test. I have no clue how {{java.beans.Introspector}} can be provoked to throw specific exceptions.

> Support customization of introspection mechanism
> ------------------------------------------------
>                 Key: BEANUTILS-425
>                 URL: https://issues.apache.org/jira/browse/BEANUTILS-425
>             Project: Commons BeanUtils
>          Issue Type: New Feature
>          Components: Bean / Property Utils
>    Affects Versions: 1.8.3
>            Reporter: Oliver Heger
>            Assignee: Oliver Heger
>            Priority: Minor
>         Attachments: beanutils-425.patch
> So far BeanUtils can cope with properties conforming to the Java Beans specification. In some situations it makes sense to relax this requirement and allow the detection of other forms of get and set methods as well.
> For instance, fluent APIs have become popular. Here you have a set method which does not return *void* and thus violates the Java Beans specification. Objects using such an API cannot be dealt with by BeanUtils currently.
> For reasons of backwards compatibility the current behavior should remain the default. But it would be cool if there was an option to set a custom introspection policy. The policy would be invoked during property discovery and can decide which properties to include or not.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira