On Sat, 2005-03-19 at 07:21 -0500, James Carman wrote: > The only problem I would have with it (and this might be a stretch) is that > it sort of goes against the nature of beans, static methods. The BeanUtils > package is for dealing with JavaBean-like objects. The MethodUtils class > (or the methdods in it) really belongs in the Commons Lang project, as it > really doesn't pertain to JavaBeans per se. It's a language-level utility > class for finding methods and stuff (that's the technical term, "stuff"). I > could actually see all of the methods in BeanUtils moving to the ClassUtils > class in Commons Lang.
That's a fair point. The javadoc for class BeanUtils describes its purpose as "Utility methods for populating JavaBeans properties via reflection", which rather excludes invoking static methods. However this library is really a bundle of several pieces of functionality: * bean-property manipulation (BeanUtils) * Beans with dynamic property sets (DynaBeans) * type conversion facilities (ConvertUtils) * reflection helpers (MethodUtils) The MethodUtils class that this patch would affect describes itself as "Utility reflection methods focussed on methods in general rather than properties in particular", so I think this class is fair game for static-method-invoking functionality. I agree that long-term it would be a good idea to think about whether MethodUtils stuff should move to commons.lang. But in the meantime I'm in favour of adding the static-method stuff to MethodUtils, as long as the functionality isn't exposed via the BeanUtils class (and it won't be). Cheers, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
