A good practice is to NEVER use the same form name unless the action is related and you are expecting the data to pass through. Of course the class can be reused.
Edgar > -----Original Message----- > From: Raible, Matt [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 26, 2003 6:18 PM > To: 'Struts Users Mailing List' > Subject: RE: form scope question > > > I've seen this a lot with Struts - it seems you can't have > forms with the same name in any two scopes. To work around > this issue, I name my forms differently. For instance, I > store the logged-in user's form in the session as > "currentUserForm" and when I edit a user, I call it "userForm." > > HTH, > > Matt > > > -----Original Message----- > > From: Kevin Williams [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 26, 2003 4:12 PM > > To: [EMAIL PROTECTED] > > Subject: form scope question > > > > > > Hi, > > > > I am hoping someone can clarify what is exactly happening in my > > application. I was trying to retrieve a form object in a > custom tag > > through the pageContext.findAttribute method, but with no > success. I > > discovered the reason that I wasn't retrieving the value > was because I > > had set the form object at the session level, and for some > reason an > > additional form object existed at the request level. Why > is there a > > duplicate form object at the request level (whose values > are NOT set) > > when I have never specified request scope on any of my > action objects > > that use this form? > > > > Thanks, > > > > Kevin Williams > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
