The simplest way would be to save your form data into a bean, and use
the @Persist annotation on your bean so you can display it and then
subsequently save it 2 requests later. By default this will use your
session to store the bean.
Alternatively you can use the @SessionState annotation if you need to
use different pages for the data entry and confirmation pages.
http://tapestry.apache.org/session-storage.html
hope that helps, paul.
On 15/06/2012 9:26 AM, David Rees wrote:
I feel like this should be something dead-simple and am missing
something obvious - I'm sure you guys will have a slick solution here.
:-)
I'm creating a simple form which has a confirmation step. Use case
goes like this:
Step 1: Enter data
Step 2: Validate data show "confirmation" page if OK
Step 3: Submit and process data
I have this build on a single page - I'm trying to avoid storing any
data in the session. So Step 3 has a form with hidden fields with the
validated data.
Of course, there's nothing that keeps one from changing the submitted
data so the data should be revalidated again before processing the
data.
I thought it'd be easy by adding the same validate attributes to the
hidden fields, but that doesn't work.
Suggestions?
-Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
