Brian,

But you don't HAVE to define a COMPLETE form in the configuration. At
least if you want to give up DynaActionForm you don't. You can define
your own form in a class that extends ActionForm. Granted you have to
add this to the config but with Xdoclet, or even just a gui editor
(James Holme's has one on his site) it is pretty easy. Personally I like
DynaActionForm since it means not touching code when a parameter is
added to the form, but there are those who maintain that they should not
be used in production. 

As far as using Session objects... I'll stay out of that one because its
just an endless debate. Every architect/lead/developer has their own
opinion, and you aren't going to change those opinions regardless of any
argument for or against Session objects :)

Al




-----Original Message-----
From: Brian McGovern [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 04, 2005 1:02 PM
To: Struts Users Mailing List
Subject: RE: Multi Step Forms

I think i have a fundemental misunderstanding of ActionForms not having
used them that much.  So forget everything i said about ActionForms, i
was wrong.  I still dont like em partially cause im stubborn, but also
because i dont like that you have to define you whole form in your
struts config.  Im gonna have alot of forms in my app but none of them
are used in more than 1 screen.  Seems like an implementation detail and
not a configuration issue.  

Whatever. The crux of this thread really can be summed up in  "At what
point does using session cease being a good practice and  become a lazy
man's shortcut."  And i think woodchuck is 100% right, there is no
correct answer.  Small apps or lightly used apps can use the session for
just about anything whereas larger apps or heavy hit apps really should
not use it much at all.  



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to