2/16/06, Matt Benson <[EMAIL PROTECTED]> wrote: > > --- Craig McClanahan <[EMAIL PROTECTED]> wrote: > > > On 2/16/06, Matt Benson <[EMAIL PROTECTED]> > > wrote: > > > > > > Hi all, > > > what are the primary reasons why DynaBean support > > has > > > not yet been implemented for these PropertyUtils > > > methods in beanutils? I assume there are some > > > concerns involved in how to implement this... what > > are > > > they? > > > > > > Although it's also due to lack of time on the part > > of developers :-), there > > is indeed a technical issue. What do you specify > > for the readMethod and > > writeMethod properties? Tools that use property > > descriptors are going to > > assume that these map to real methods that can be > > used to get and set the > > property values via reflection, but there are > > (obviously) no methods with > > the correct method signatures on the DynaBean base > > class itself. > > > > Craig: thanks for your quick reply. My (possibly > naive) impression was that you would specify > DynaBean's get(String) and set(String, Object) > methods... :) Now, tell me why that won't work as > expected. ;)
Because a tool like Java Studio Creator (my day job is architect for this) is going to assume that these methods conform to the JavaBeans design patterns for properties ... a getter that takes zero arguments, and a setter that takes one argument (the value). Trying to use these methods will cause the tool's reflective get or set call to fail because the argument types and counts won't match. -Matt Craig
