commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (BEANUTILS-425) Support customization of introspection mechanism
Date Sat, 09 Nov 2013 18:02:18 GMT

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

Oliver Heger resolved BEANUTILS-425.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.9.0

Fixed in subversion in revision 1540352.

> 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
>             Fix For: 1.9.0
>
>         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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message