For my needs, that sounds sufficient. Any ETA on when someone might be looking at this? I'm more than willing to put some time in to help.
Are you concerned about backwards compatibility? It seems if the methods on BeanUtils change from static to instance, it may take longer to get the new release adopted since it will require everyone using the library to undergo code changes to upgrade. Perhaps you could consider refactoring the code in such a way that backwards compatibility is maintainable, yet this new feature could be added in. I would really like to be able to just drop a new beanutils.jar file into my struts application and have the new functionality, without having to wait for struts to adopt it. I think this will be a great feature for BeanUtils. The ConverterSets I implemented have really helped to remove a lot of the tedious coding in our mapping layer. Thanks, Erik > ----- Message from [EMAIL PROTECTED] --------- > Date: Mon, 24 Feb 2003 20:44:48 +0000 > From: robert burrell donkin <[EMAIL PROTECTED]> > Reply-To: Jakarta Commons Developers List <[EMAIL PROTECTED]> > Subject: Re: [PATCH] [BeanUtils] Addition of ConverterSet > To: Jakarta Commons Developers List <[EMAIL PROTECTED]> > > hi erik > > thanks for hanging around while we cut the 1.6.1 release. > > i think that some of the changes to beanutils we're (tentatively) got > planned will mean that what you need will probably already be provided as > a byproduct of the refactoring. > > the idea is that the static utility classes in beanutils will be converted > into proper beans. the static methods will then call an instance (in the > start these will be singletons). you should be able to create two > different BeanUtils instances and then add different convertors to the > ConvertUtils associated with each. > > how does this sound? > > - robert > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
