From: "Erik Weber" <[EMAIL PROTECTED]> > Joe, thanks for your opinion. You and Rick have convinced me to stay > with one form page for add/update. I did this before in a non-struts > app, and despite all the conditionals I ended up with, the ensuing > layout revisions did make it worth it.
Take a look at LookupDispatchAction. That's what I use to control which CRUD action is happening, and all the code stays in one Action class. Instead of separate 'add' and 'update' Actions, they would be methods within your EditWhateverAction. Dynamic forms or not doesn't really matter... you just use the 'form' object that gets passed into your method. And since it's a reference to the form that's sitting in request or session scope, you don't have to "put" it anywhere, it's already there. -- Wendy Smoak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
