Re: Best practice for formbean scope and handling form validation errors

2005-02-04 Thread Jeff Beal
Adam Lipscombe wrote: In this instance the problem is this: Form1 has a logic:iterate tag that iterates over a List held in myActionForm. The List is setup by the initAction.do action. How do I preserve the List between actionform instances? (It's not referenced in the JSP other than the logic:iter

RE: Best practice for formbean scope and handling form validation errors

2005-02-04 Thread Adam Lipscombe
e JSP other than the logic:iterate tag) Tia -Adam -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Beal Sent: 04 February 2005 17:14 To: user@struts.apache.org Subject: Re: Best practice for formbean scope and handling form validation errors Adam Lipscombe wrote:

Re: Best practice for formbean scope and handling form validation errors

2005-02-04 Thread Jeff Beal
Adam Lipscombe wrote: But, if the scope of the "myActionForm" formbean is "request" a new instance of the formbean is constructed when Form1.jsp is re-displayed. Hence none of the data that it originally held in it is present and the form fails. The formBean was originally populated by /initAction

Best practice for formbean scope and handling form validation errors

2005-02-04 Thread Adam Lipscombe
Folks, I have 2 actions which look (sort of) like this: If the Form1.jsp is submitted the "/processAction.do" gets called. Validation occurs in either the "myActionForm" actionform or the "myAction" action. If the validation fails a struts ActionErrors object is populated and Form