That's exactly why we want nested DataContexts. :-)
You do your wizard/multi-step process in a nested DataContext and if
they finish the last step, you can commit it all. If they run off
elsewhere, no harm done and it falls out.
/dev/mrg
-----Original Message-----
From: Cris Daniluk [mailto:cris.danilu..mail.com]
Sent: Tuesday, May 03, 2005 9:17 AM
To: cayenne-use..bjectstyle.org
Subject: Re: Tapestry integration options
[snip]
I also agree, by the way, that its a bad general idea to span like
that. I'm not worried so much about the commit not coming (that
problem takes care of itself... ) as I am about the user browsing to
an entirely function without completing the multi-step process, thus
leading to all sorts of inconsistency.
Cris
This archive was generated by hypermail 2.0.0 : Tue May 03 2005 - 09:53:18 EDT