[
https://issues.apache.org/jira/browse/BEANUTILS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509265
]
Martin van den Bemt commented on BEANUTILS-285:
-----------------------------------------------
The problem you are describing is actually the current behaviour of betwixt and
beanutils. People depend on that and if it was not working for them, there is
documentation on how to solve that problem. So if people want to do what you
describe they already need to work around that.
Based on above I am not creating more issues than I am resolving, I am just
making sure everything works as it always did.
That the solution in the trunk of beanutils solves a lot of other possible
problems (or prevents usage of hacks) and is an improvement over current
behaviour, is a different rationale altogether.
I am not saying your changes aren't an improvement which can also benefit
betwixt users, but I rather have the developer make that choice instead of
possibly breaking default behaviour. Don't forget that betwixt is kind of a
black box and any behaviour that can change the object<->xml mapping by
dropping in a new beanutils can an application.
To get to your example : if all of a sudden a comma instead of a period will
turn up in a value that can break the one who is expecting a period.
In any case, this whole reasoning doesn't mean that much when betwixt is
released after beanutils is :)
> 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]
