I haven't looked at DynaActionForm yet, but we are just starting to use DynaBeans - isn't the beauty of all this stuff that you don't have to use the provided DynaActionForm, but just go create your own version that suits your needs - sub-class ActionForm, implement the DynaBean interface and Bob's your uncle, it'll all work for you too - if its good and you think others would use it, submit it back to struts - I'm sure theres room for more than one implementation.
Niall > -----Original Message----- > From: Bryan Field-Elliot [mailto:[EMAIL PROTECTED]] > Sent: 15 March 2002 21:26 > To: Struts Developers List > Subject: Re: DynaActionForm questions > > > Thanks Craig, > > On Fri, 2002-03-15 at 14:19, Craig R. McClanahan wrote: > > Pretty slick, huh? :-) > > > > It is slick indeed. The intended focus could just use a little more > refining (perhaps in the users manual). > > If you know what your app needs to ask for, then DynaActionForms are a > new and easier way to express it. > > On the other hand, if your application doesn't know what it's going to > be asking for until runtime, then DynaActionForms aren't the complete > solution, although they will probably be part of the solution I > ultimately build. > > The two scenarios are pretty different, and the use of the "dyna" > keyword could lead over-eager developers like me to assume something > that isn't there. > > Thanks, > > Bryan > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
