I've been looking at the memory leaks described in BEANUTILS-291[1] and am considering making API changes that will break compatibility with the BeanUtils 1.8.0-BETA release to remove one of the issues. The changes however are in new Converter implementations added after the previous BeanUtils 1.7.0 release and so compatibility with that version will not be broken.
Briefly, I want to remove the Class parameter from AbstractConverter's constructors (will also impact other implementations that derive from it) and make the protected getDefaultType() method abstract. IMO breaking compatibility with a *Beta* release is OK, but does anyone have any objections to doing that? Niall [1] https://issues.apache.org/jira/browse/BEANUTILS-291 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
