Hi, I thought I'd have a stab at some requirements for Reflection/Bean tools which we seem to be talking about.
Scope: Reflection - Class, Method, Field, ... Bean - Introspector, javabeans Need: - Performance on java1.3 and earlier - J2ME - Current reliance on javabean spec version 1 that was designed to replace ActiveX, not be a domain model. - Boring coding of javabean gets/sets (I know tools can help, but I still see bugs in gets and sets) - Auto generated event methods (bound/constrained properties) - Desire for dynamicly created javabeans/ properties (from databases, xml etc.) - Desire to pass around an object representing a property - Desire to change the bean Introspector's lookup mechanism, such as to allow private get/set methods to be treated as properties - Desire to handle collections properly (they aren't handled at all by beans Introspector at the moment - Desire to dynamically make a property read only once setup (like const in C) Bean types: - Coder writes interface with coded get and set methods, BCEL generates implementation on the fly - Coder writes abstract class with coded get and set methods, BCEL generates implementation on the fly - Coder writes real class with coded get and set methods, BCEL modifies parts on the fly - A general purpose bean, to be used where all the data is dynamic, similar to a HashMap - A mixture object, where some fields have coded get and set methods, others are dynamically created as the application requires OK, so if you haven't guessed, I'm more interested in Beans than Reflection on its own (Reflection is fine and useful, but its very low level). Most of these ideas come from the Joda project, but I think they represent a good idea of what people are using beans for now. Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
