On Tue, 25 Feb 2003, robert burrell donkin wrote:
> Date: Tue, 25 Feb 2003 22:45:16 +0000 > From: robert burrell donkin <[EMAIL PROTECTED]> > Reply-To: Jakarta Commons Developers List <[EMAIL PROTECTED]> > To: Jakarta Commons Developers List <[EMAIL PROTECTED]> > Subject: [beanutils] beans for static utility classes > > beanutils has a fair number of utility classes which are composed of > static methods. i'd like to create proper beans containing the > implementation code and have the static methods call an instance. > > this would allow users to create different instances with - for example - > different registered convertors. see > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14848 > > and > > http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=104613177905644&w=2 > > it would also allow normal inheritance to be used to improve the structure > of the code allowing - for example - the easier maintenance of the locale > beanutils code: > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16038 > > it would also allow improved and more flexible caching to be developer to > improve performance. see: > > http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=103929482023502&w=2 > > comments? > > anyone objections to me implementing these changes? > +1. We should, however, create a factory method (perhaps based on commons-discovery technology) to create an appropriate implementation of the proper beans for you. That way, we could support pluggable replacements for the standard implementation classes quite easily. Finally, the factory should be configurable to (or default to) creating an instance per class loader. That way, for example, the cache of introspected beans that PropertyUtils maintains for one webapp won't conflict with the cache for a different webapp, even if commons-beanutils is loaded from a parent class loader. > - robert > Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
