I use this pattern (SessionState cleared after successful processing), but:
The form values get not set in my object, because the form has not been filled out completely. I want to save the (unvalidated) state of the form, to repopulate the component values at a later point in time.
Currently the users of the application have to fill out all fields (so that the form validates and the values of the components are written in my business object) before they can go to a sub-page.
Thiago H. de Paula Figueiredo schrieb:
Why don't you use @SessionState in the complex object you're editing? When done, persist it to the database and then clear the object in @SessionState.
-- Felix Gonschorek GG-Media Kirchstr. 18 69115 Heidelberg Tel: +49 6221 187 18 10 Fax: +49 6221 187 18 99 Mobil: +49 176 2234 1338 fe...@gg-media.biz http://www.gg-media.biz Vertretungsberechtigte Gesellschafter: Felix Gonschorek & Jochen Greiner Umsatzsteuer-Identifikationsnummer gemäß § 27a Umsatzsteuergesetz: DE232906440 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
