Thanks for these recommendations. The @Persist approach works fine, when the form is submitted in 'add' mode, I can store the newly created identifier temporarily for use on the next ajax call.
The form context parameter works as advertised, but I don't think solves my problem as the context is set to 'null' when you arrive at the form in 'add' mode, and this never changes. So @Persist it is. Thank you both for your advice. On 1 August 2012 16:14, Thiago H de Paula Figueiredo <thiag...@gmail.com>wrote: > On Wed, 01 Aug 2012 17:11:26 -0300, Michael Prescott < > michael.r.presc...@gmail.com> wrote: > > (posted) >> Okay, yes, I may just be running counter to the grain - ajax requests >> aren't supposed to change the context. I suppose (since the zone is in >> the form) I could have the zone contain a sort of 'custom context', so that >> when I move from adding to editing. >> > > The Form component does have a context parameter you can use to receive > the edited object in event handler methods when submitting. Or you can use > @Persist. > > > -- > Thiago H. de Paula Figueiredo > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > >
