Jason, Maybe I'm thinking about this wrong, but ...
On Tue, Aug 24, 2010 at 9:49 AM, Jason Durham <[email protected]> wrote: > Of course, the Registrant won't be saved until after step 3. > ... why not? If you save the Registrant after Step 1 (where you have all the information for the Registrant in your model), you could then pass the ID of the new entity back to the next page (or persist the ID in the session). Then, as a Car is submitted, you retrieve the Transfer object using the ID (probably from the cache, if you're allowing Transfer to cache its object), create and add the Car object to the Registrant object (or vice versa, depending on your Transfer config). You could keep the Registrant "inactive" (with some sort of flag) until s/he's paid. Or you could keep the ID in the session, using it to delete the Objects if the person doesn't complete the registration. -- Thanks, Tom Tom McNeer MediumCool http://www.mediumcool.com 1735 Johnson Road NE Atlanta, GA 30306 404.589.0560 -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search: http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8 You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en
