Why is JSP -> .do -> .do -> JSP bad? I don't think you could make a case for doing population in the form bean constructor - too much logic. Besides, it wouldn't work, as that same constructor would be called when the user submitted the form - you wouldn't want to redo the database calls then, right? We don't do action -> action very often (don't need to), but when needed it works fine.
-- Voytek Jarnot Quidquid latine dictum sit, altum viditur. > -----Original Message----- > From: Bredesen, Chris - NA US HQ Delray > [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 29, 2003 2:43 PM > To: Struts Users Mailing List (E-mail) > Subject: [Newbie] ActionForm prepopulation > > > Hi group, > > There's one general struts concept that I haven't fully gotten my arms > around yet. I'm trying to design without using action > chaining, but I have > the following scenario: > > - JSP posts to an action which accesses a form bean and does > some business > logic > - The next JSP in the process has a DIFFERENT form bean on > it, and values on > that one must be prepopulated using ... another action? > > This would cause JSP -> .do -> .do -> JSP which we know is bad. > > So then do I pre-pop my Form bean values in the ActionForm > constructor? As > member variables? What happens when reset() is called ... > how do I make > sure they return to their proper initial values upon reset? > > Thanks for participating, > > Chris > *Struts Evangelist in Training* > > --------------------------------------------------------------------- > 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]
