simon, BeanUtils does the actual setting of properties. there are many other "JavaSpec conforming" utilities.
(i use castor for introspection and generating relevant information) you are right, i can always use new rules... i still feel the dependency on BeanUtils in the populate() and setProperty() cases is too much - while ok in CallMethodRule etc ricardo --- Simon Kitching <[EMAIL PROTECTED]> wrote: > On Wed, 2003-10-22 at 11:27, Ricky Panaglucci wrote: > > hello, > > > > is it by design, that SetPropertyRule and > > SetPropertiesRule use BeanUtils.populate()? > > it would be usefull to use other binders as well. > > Well, the term "property" in the name of these rules > is intended to > refer to the definition of a JavaBean property as > per the official > JavaBean specification. > > The BeanUtils library implements that specification, > so there doesn't > seem to be much need for allowing the user to > configure alternate > implementations. > > If you do wish to map xml attributes to class > methods in a way other > than the JavaBean spec defines, you can always > create your own rule, > like > SetRicardoPropertyRule(...) > which uses some other algorithm for determining > which method to invoke > on an object given an xml attribute or element name. > > What "other binder" do you have in mind? > > > Regards, > > Simon > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
