You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2025/01/07 14:07:01 UTC

[jira] [Updated] (BEANUTILS-279) Allowing Multiple Converters Per Destination Class

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

Gary D. Gregory updated BEANUTILS-279:
--------------------------------------
    Fix Version/s: 2.0.0-M2
                       (was: 2.0.0-M1)

> Allowing Multiple Converters Per Destination Class
> --------------------------------------------------
>
>                 Key: BEANUTILS-279
>                 URL: https://issues.apache.org/jira/browse/BEANUTILS-279
>             Project: Commons BeanUtils
>          Issue Type: New Feature
>          Components: ConvertUtils &amp; Converters
>    Affects Versions: 1.7.0
>            Reporter: Bradley M. Handy
>            Priority: Minor
>             Fix For: 2.0.0-M2
>
>         Attachments: ConvertUtils-1.7.0-patch.tgz, ConvertUtils-20070519-patch.tgz
>
>
> Currently only one Converter may be registered per destination class.  It may be prudent for an application to have the ability to use multiple "named" Converter instances to convert values to a destination type.  By adding a second-level Map keyed by Converter name, this can be accomplished without affecting existing behavior.  A "default" name is used for the default Converter which will allow for emulation of the previous single Converter implementation.
> Patch files for both BeanUtils 1.7.0 and the current Head revision of the affected files has been provided.



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