In my applications authentication event, we check to see if the user submitted a form. If they did, we store it in session and then check for it later after they login, and then push it back into the form scope.
The idea is this: 1) User just typed in a whole lot of data. 2) << in the mean time, user has timed out>> 3) User submits form, and instead is confronted with a login screen since they timed out (and we've stored there data into session) 4) user logs in, and is redirected to the "save action". 5) we pull the data out of session, put it back into form, and all is well. This works great until file attachments come into play. Railo stores them in webroot/WEB-INF/railo/temp and the file doesn't seem to exist after the login. Is there a best practice way to handle this sort of thing so file uploads can be preseved? -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en
