Hen reminded me I promised to do this, so here is a first crack at a mandate for the proposed Convert sandbox component. One thing I was thinking about is the name. Convert is rather dull, how about calling it Morph instead?
I don't know what format we want this mandate in, so for now I have a copy in M$ Word that I will convert (pun intended) to the appropriate format later. Here is a text copy of it: INTRODUCTION Convert is a framework for converting an arbitrary Java object into any other arbitrary Java object. The framework grew out of the conversion mechanism provided by the ConvertUtils class of the BeanUtils framework. One goal of the Convert framework is to integrate seamlessly with BeanUtils. POTENTIAL FEATURES - Provides a simple mechanism for converting an arbitrary Java object into any other arbitrary Java object. - Seamlessly integrates with BeanUtils. - Provides local-sensitive conversions for internationalization. - Allows converters to be written at an arbitrary level of granularity. For example, fine-grained converters can only convert objects of a single class to objects a single other class. Course-grained converters can convert an object of a single class to objects of a multitude of different classes. - (Related to the point above) Provides an automated conversion lookup mechanism that allows conversions for types that have not been specifically registered to be attempted by traversing the inheritance hierarchy of the classes involved in the conversion. - (Related to the point above) Provides a Go4 Strategy that defines how inheritance hierarchies are searched for converters. Some obvious Strategies are included in the Convert framework. - Allows different converters to be used under different circumstances. For example, one module of an application might require dates to be converted to strings one way while another part of the application requires a different standard for a different sent of users. - Provides a library of converters that may be extended by users of the Convert framework. - Provides a converter configuration mechanism that alleviates users from the task of building their own configuration structures. - Provides converters that operate on collections. For example, such a converter might change a List of Person into a List of String. - Allows the identity conversion (for example, String to String) to be turned on or off. PROJECT NAME This project is still in the conceptual phase and a name has not yet been decided upon. Possible names include: - Convert - Morph Matt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
