Yes BeanValidatorForm is just a DynaBean wrapper - it can wrap either other DynaBean or POJO beans. FormBeanConfig has become the ActionForm factory (since Struts 1.2) which makes it straight forward to plug in your own mechanism by overriding the createActionForm() method. You can get it to default to your own config implementation either by having your own ModuleConfig flavour or through the struts-config...
<form-beans className="myPackage.MyFormBeanConfig"> .... </form-beans> Niall ----- Original Message ----- From: "Joe Hertz" <[EMAIL PROTECTED]> Sent: Wednesday, February 09, 2005 4:59 AM > How about a simpler case then.... > > My real goal is to have DynaForms that are backed my experimental > "semi-lazy-dynabean". > > BeanValidatorForm (while an impressive piece of work IMHO) isn't actually > subclass of a DynaForm (even though it seems like it can be used in almost > the same way). > > The way I see it, the "easiest" way is to implement a FormBeanConfig that > identifies my DynaBean and have all my beans use it? (I can get it to > default by mucking with the ModuleConfig object, right?) > > Sorry for asking so many questions on this. I am delving into the innards of > Struts on a level I haven't before, and I think I'm *this* close to fixing > the thing about Struts that I seem to whine about incessantly. > > If I have a DynaForm Object backed with my own brand of DynaBean, I'm most > of the way home. > > Tx again --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
