commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16525] - BeanUtils.setProperty is over-zealous at converting types
Date Tue, 04 Feb 2003 07:35:26 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16525>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16525

BeanUtils.setProperty is over-zealous at converting types

craig.mcclanahan@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Blocker                     |Enhancement



------- Additional Comments From craig.mcclanahan@sun.com  2003-02-04 07:35 -------
I've applied a more conservative version of the proposed patch to
copyProperty(), which covers about 80% of the use cases for indexed and mapped
properties, and 100% of the use cases for nested properties.  The existing
functionality of setProperty remains untouched.  This is available in nightly
build 20030204 of commons-beanutils, and is very likely to be made available in
a 1.6.1 patch release of commons-beanutils.

The concept of abstracting out a common BeanPropertySpecifier is an *excellent*
idea, and will offer many opportunities to reduce the code bloat that has grown
in the (nearly) three years of the existence of BeanUtils.  Yet, I agree with
Tim's assessment that this is more appropriate for a major (2.0) or minor (1.7)
version change, rather than a 1.6.1 patch release that is urgently desired by
several projects.

When we decide to formally review this idea, we should also evaluate whether it
makes sense to use something like the commons-clazz project APIs to represent
the metadata about a bean property that works across standard JavaBeans and
DynaBeans, or go ahead and implement a commons-beanutils-proprietary API like
BeanPropertySpecifier.

Because the majority of use cases are fixed by the checked-in patch, changing
this to an enhancement request so it won't get forgotten.

---------------------------------------------------------------------
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