> layout, current shopping cart composed objects etc). > > @Mark >>In that case, why not duplicate() (or write your own clone() method), >>on the user, and populate THAT with data? :D > > Could you explain this a bit further? Ideally the following would > happen: > > - Form loads with current session.User data loaded into the form > controls > - User edits form and submits > - Validation fails -> View reloads with the data the user edited in > the form > - BUT the session.User still retains the original data > > It's almost as if I shouldn't use: > > <input type="text" name="email" id="email" value="#oUser.getEmail()#" / >>
I would see the flow as (or something similar) - - put your current session.oUser in the request scope. - Form loads with <input type="text" name="email" id="email" value="#request.oUser.getEmail()#" /> - on submit duplicate() the session.oUser and put it in request scope - load in the form data into the request scope's object (the copy) - if validation fails, re-route back to the display page - page still loads with <input type="text" name="email" id="email" value="#request.oUser.getEmail()#" /> - session is still intact. Make sense? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" 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/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
