Hi George! What I am doing for this is following the Jumpstart example...I store all of my entities in the Conversation, and on the last page of the Wizard I write them to the database. It's worked out very well so far. Check out http://jumpstart.doublenegative.com.au/jumpstart/examples/wizard/usingpages1 for the example I am using.
There's also a page there for different techniques for passing data between pages...check http://jumpstart.doublenegative.com.au/jumpstart/examples/state/passingdatabetweenpages Another big thanks to Geoff for providing this valuable resource! On Fri, May 25, 2012 at 9:02 AM, George Christman <gchrist...@cardaddy.com>wrote: > Hello, I'm building a small little wizard that consist of a few pages. The > wizard allows for updates as well. I'm a hibernate user with a fairly > complex data structure consisting of many joined entities. I do not want to > save/update the data until the last page of the wizard which has caused me > to lose my data from one page to the next. I thought there was a way to > persist it with hibernate and retrieve it on the next page, but I've failed > miserably with that. "Maybe I'm missing something". So my question is there > a alternative solution such as SessionState or Persist where I could store > the object in memory and then later save? > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Building-object-through-wizard-tp5713417.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
