commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (BEANUTILS-285) Consider options for BeanUtils compatibility in light of Conversion improvements
Date Mon, 02 Jul 2007 02:05:04 GMT

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

Niall Pemberton resolved BEANUTILS-285.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.8.0

I have added new BeanUtilsBean (BeanUtilsBean2) and ConvertUtilsBean (ConvertUtilsBean2) implementations
which take full davantage of the improved Converter implementations. The default behaviour
is compatible with BeanUtils 1.7.0, but these new implementations can be configured by calling
BeanUtilsBean.setInstance(new BeanUtilsBean2()).

http://svn.apache.org/viewvc?view=rev&revision=552381

Closing this as resolved

> 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
>             Fix For: 1.8.0
>
>         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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message