I do my rendering using DOM and server side java code. While a lot of it is now done in abstract superclasses (making use of PropertyUtils to get stuff from the form) a lot is also still making direct use of specific actionForms, and I find having real methods in my action form is useful in catching typos at compile time, and also means JBuilder (shame on me for not using vi!) gives me nice drop down boxes with all the method names, which is rather useful since my brain's small cache can't remember more than half the fields on a given form at any one time...
Furthermore , one can spend ages typing all the getters and setters with ones brain in nuetral yet still feel one has been getting work done ;-) (On the other hand once I make time to actually learn the syntax for DynaForms I will probably be switching ...) -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 09, 2002 06:40 To: Struts Users Mailing List Subject: Re: DynaActionForm Advantages On Mon, 8 Jul 2002 [EMAIL PROTECTED] wrote: > > Tell me again why I should use the standard form beans? > > > I'm trying to understand because it seems to add complexity having two > different ways of doing Form Beans. Why not polish up the Dyna bean stuff > and then dump (er, deprecate) normal Form Beans? > If DynaActionForm had been around from the very beginning, I doubt we would have ever invented the standard ActionForm bean approach. At the same time, I can't necessarily justify deprecating something that 100% of existing 1.0 applications are required to use, especially when the rest of Struts doesn't care at all which way you do things -- and you can even make your Actions not care if you use PropertyUtils methods to get and set the property values. > One advantage I will give the normal Form Beans is that they are easier for > a newbie to pick up and learn. They shorten the learning curve to get > productive with Struts initially. But if DynaBeans were made to be very > easy, then this advantage may disappear as well. > It's also a little premature to conclude that DynaActionForm beans are good replacements for all scenarios where standard ActionForm beans are currently used - at least in a 1.1 time frame. We need more real world experience with them to validate this first. > > > Kevin > Craig -- 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]>
