You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Brian McGovern <bm...@imediainc.com> on 2005/04/04 15:57:02 UTC
Multi Step Forms
I have a situation where i need to have a multi screen form, lets say 3 steps. On the successfull validation of the 3rd step. I want to save the data into the DB. This data would have been collected starting on step one, through step 3 and ecapsulated in 1 or more objects.
My question is whats the best way to do this from a design standpoint without using actionForms, thats not in option in my case. Specifically is there a clean way to save a partially filled object from step 1 and pass it to step 2. Basically the functionality like Server.Transer in .NET.
-Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Multi Step Forms
Posted by Brandon Mercer <br...@eutonian.com>.
Brian McGovern wrote:
>I have a situation where i need to have a multi screen form, lets say 3 steps. On the successfull validation of the 3rd step. I want to save the data into the DB. This data would have been collected starting on step one, through step 3 and ecapsulated in 1 or more objects.
>
>My question is whats the best way to do this from a design standpoint without using actionForms, thats not in option in my case. Specifically is there a clean way to save a partially filled object from step 1 and pass it to step 2. Basically the functionality like Server.Transer in .NET.
>
>
yes there is. I've got a similar setup right now. What I've done is
setup three Actions, one for each step, and I save information to a
temporary DB table. This information could also be saved in the
session, or on each page. Because of how I setup my DAO I actually have
an object per page ( this is much cleaner in the long run). On the last
page the information is reviewed by the client and I have another action
that pulls the information out of wherever you put it, and stores it
into the "primary" table.
Brandon
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org