You'd need a descendant of ActionForm, yes. It would have a property for each image button (an instance of ImageButtonBean) that you needed to have on your form. It kind of yanks dyna-forms out from under you a little bit. I'm not entirely sure, but possibly you could specify a formbean that descended from the dyna* stuff and had your button properties -- which could be reused and still have dynamic fields as well. I'd have to dig and I'm kind of in the middle of something else right now :-(
Sorry. I didn't see your reply or I'd have answered sooner. The most straight-forward implementation would build a new ActionForm descendant that had properties for each of your required fields, and a property for each button - yes. HTH, Eddie Cohan, Sean wrote: >NeverMind. Brain freeze. > >-----Original Message----- >From: Cohan, Sean [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, September 10, 2002 2:57 PM >To: 'Struts Users Mailing List' >Subject: Tip #1 > > >Should we be extending ActionForm for this tip? > >I'm guessing yes since the sample Action code was listed as: > > String selected = ((myForm) form).getSelected(); > > if (Constants.CANCEL.equals(selected)) ... > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
