Hi,
I'm currently building a Registration form for my MonoRail application and
there is a LOT of data to be entered by the user.
So I decided to split it through using a Wizard interface.
I just feel a bit at a loss what the best way would be to carry that
intermediary data from Step to Step.
I
A multi-step wizard *is* a session-wide action.
options:
1. do all steps in Ajax way, aggregating the data on the client. not easily
supported within the MR wizard infra.
2. use session to keep data between steps. easy, simple, scaling issues
(unless using a farm-aware session storage)
3. use
I'm not used to the MR wizard but here are some thoughts:
- instead of validating a fullfledged DB entity, you could validate
plain Form DTO that match each registration steps, monorail controller
has a validator runner that you can use on any DTO bringing validation
attributes
- if session feel
Thanks!
The Form-DTO idea is really good. I'll do that.Also I agree Ken, it's a
Session-wide operation so that's probably the best way to go about that.
I guess what impaired my thinking on this one was that every step of the
Wizard corresponded to one Component in my Entity.
My current approach
Splitting the registration into two cases is also a very good Idea. I could
let them complete their profile through the member area. Thanks for the
suggestion.
Now, off to something else. I tried the DTO approach and just found out
something peculiar: I can't really use the ActiveRecord
Forget the last part about the Validator requiring a AR mapping. I just used
it wrong.
On Fri, Sep 11, 2009 at 12:48 PM, Daniel Hölbling hoelblin...@gmail.comwrote:
Splitting the registration into two cases is also a very good Idea. I could
let them complete their profile through the member
