[
https://issues.apache.org/jira/browse/BEANUTILS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509228
]
Niall Pemberton commented on BEANUTILS-285:
-------------------------------------------
I understand you're trying to avoid issues - but the more I think about it the
more issues I see. I believe you're probably creating as many issues(if not
more) as you're resolving. For example the BeanUtils DoubleConverter can now be
configured for a French Locale - using a comma as the decimal separtor. It
would convert to and from a String value using a comma. Problem now is for
betwixt - conversion from String to BigDecimal by DoubleConverter would expect
a comma - which if DoubleConverter had handled the conversion to a String it
would have - in Betwixt though it will delegate the conversion to String to the
converter registered for Strng - which the default registerd implementation
would just use the Double's toString() method (and therefore have a period for
the decimal separator).
> Consider options for BeanUtils compatibility in light of Conversion
> improvements
> --------------------------------------------------------------------------------
>
> Key: BEANUTILS-285
> URL: https://issues.apache.org/jira/browse/BEANUTILS-285
> Project: Commons BeanUtils
> Issue Type: New Feature
> Components: ConvertUtils & Converters
> Affects Versions: 1.8.0
> Reporter: Niall Pemberton
> Assignee: Niall Pemberton
> Attachments: betwixt-beanutils-gump-fix.patch
>
>
> The Conversion improvements associated with BEANUTILS-258 potentially create
> compatibility issues - this was highlighted by Betwixt's tests failing
> recently in the gump run - see http://tinyurl.com/2mxbv8 for more details.
> Quite a bit of effort has been put into making the new conversion facilities
> as painless as possible for existing users. However it is not fully backwards
> compatible in terms of behaviour (stiil binary compatible). Need to give this
> some consideration before a BeanUtils release - at the moment there are two
> options on the table (more welcome!):
> 1) The compatibility as it stands is good enough (covers most cases) - so do
> nothing
> 2) Provide a "compatibility option" - so that users can choose either the new
> behaviour or behaviour compatible with BeanUtils 1.7.0. This probably
> involves quite a bit of work - adding back the old behaviour alongside the new
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
