[
https://issues.apache.org/jira/browse/BEANUTILS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509223
]
Martin van den Bemt commented on BEANUTILS-285:
-----------------------------------------------
This is what I did at first, but the problem with that approach is that I am
fixing the testcase, which in turn doesn't really fix the problem. If
conversion changes when using a new beanutils version, people are not able to
deserialize their xml anymore (or with weird results), which is the reason of
the copy&paste of the beanutils 1.7 method. Don't forget that the test is for
internal betwixt use. Even if people use beanutils directly the betwixt
behaviour will not change if they going to use the new version. If they chose
to depend on the new behaviour in beanutils they will hit problems when
developing instead of getting into trouble at runtime when someone decides to
use the latest and greatest dependencies..
So in short : I prefer a developer to get into trouble when he chooses to (=
working on code that depends on betwixt) and not when someone else chooses to
(the person that needs this version of beanutils to do something else)
> 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]
