commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedikt Ritter (JIRA)" <>
Subject [jira] [Commented] (BEANUTILS-425) Support customization of introspection mechanism
Date Sun, 10 Mar 2013 14:59:12 GMT


Benedikt Ritter commented on BEANUTILS-425:

Hi Oliver,

I've had a look at your patch. The following things should IMHO be changed before applying:
 * Rename IntrospectionContextImpl to DefaltIntrospectionContext
 * Rename IntrospectionContext.getCurrentClass() to getClass()
 * Add generics
 * Add unit tests for DefaultBeanIntrospector

What I like very much is, that we can externalize the bug fix for bugzilla 28358 into a separate
object. BeanUtils has the problem that to much is going on in some of its methods.
> Support customization of introspection mechanism
> ------------------------------------------------
>                 Key: BEANUTILS-425
>                 URL:
>             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:

View raw message