In most cases I've used, putting them in application scope works great. I know that won't work for a list setup by what role someone might have or other such case, in those cases I would use session scope (but I don't see that much with what I do).
-- James Mitchell Web Developer/Struts Evangelist http://www.apache.org/struts/ > -----Original Message----- > From: Rick Reumann [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 27, 2003 3:07 PM > To: Struts Users Mailing List > Cc: Robert Taylor > Subject: [Q] Revisiting: Repopulating Lists after validation > returns false > > > A while back there was a good discussion going about the best practice > for repopulating lists that a JSP form needs after validation returns > false and you need to be returned to the initial JSP form. > > The problem of course is if you have an options collection that is not > in session or application scope, you some how need to have this > collection repopulated. > > Popular belief seems to be to not do this in the reset method of an > ActionForm (or any of it's sub classes). > > I really liked Robert Taylor's solution of setting the input attribute > in your config file to be that of the action that sets up > your form, so > that if validation fails you form collections are reset. > > The problem, though, I'm running into with that approach is > that what if > your setUp action also is used to set fields in the > ActionForm? You will > end up reseting anything the user submitted for those fields. > > Is there a good work around to this problem? or other suggestions of > where/when to repopulate lists after validation? > > > -- > Rick Reumann > > --------------------------------------------------------------------- > 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]
