You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Ian Joyce <Ij...@aafp.org> on 2004/01/31 08:28:34 UTC
request attributes and failed validation
In my Action I am populating an ActionForm with data from a database. I am also setting some additional request attributes with Lists of beans. The purpose of these Lists are to create various drop down boxes in the form. This works well, however when the form is submitted and validation fails these attributes are no longer in the request and the drop down boxes aren't created.
What is the best way to have these Lists avaiable when the validation fails?
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: request attributes and failed validation
Posted by Michael McGrady <mi...@michaelmcgrady.com>.
One way is to put them temporarily in the session. But, why not just do it
again? Is it too slow?
At 11:28 PM 1/30/2004, you wrote:
>In my Action I am populating an ActionForm with data from a database. I
>am also setting some additional request attributes with Lists of
>beans. The purpose of these Lists are to create various drop down boxes
>in the form. This works well, however when the form is submitted and
>validation fails these attributes are no longer in the request and the
>drop down boxes aren't created.
>
>What is the best way to have these Lists avaiable when the validation fails?
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org