On Fri, Jun 15, 2012 at 12:57 AM, Geoff Callender
wrote:
> See if this helps: the Wizard Using Form Fragments example on:
>
> http://jumpstart.doublenegative.com.au/jumpstart
Yeah - don't know how I missed that before - that looks like the
perfect solution and is nearly exactly the app flow I
I'm pretty sure that hidden fields will not be validated by tapestry.
You can wrap non-hidden fields in a
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Adding-confirmation-step-to-form-tp5713910p5713922.html
Sent from the Tapestry - User mailing list archi
See if this helps: the Wizard Using Form Fragments example on:
http://jumpstart.doublenegative.com.au/jumpstart
Cheers, Geoff
On Friday, 15 June 2012, Paul Stanton wrote:
> The simplest way would be to save your form data into a bean, and use the
> @Persist annotation on your bean so you c
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 yo
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
St
