On 6/22/05, Michael Taylor <[EMAIL PROTECTED]> wrote:
> Michael,
>
> It appears from your
> articles that your solution depends upon tight integration with the
> application model. There are two down sides to this. The obvious one
> is writing more code, where it might be generated from a model.
Michael,
Thanks. Your solution was very interesting. It is very similar to what
I wound up building, although you took the time to generalize it and
write some great articles. One thing that I didn't like about my
previous attempts was dependence upon writing Java code to model the
transit
Just cannot help it; I am sorry, just cannot keep it inside ;) On the
other hand, maybe not everyone knows about it yet?
Homepage: http://www.superinterface.com/easywizard.htm
Live demo: http://www.superinterface.com/wizard/signupWizard.do
Now back to the regular programming (c) Frank ;-)
P.S. T
Alternatively, you can use one action form in session scope with a
series of actions representing each page. Each page in the wizard would
have a series of forward representing the transition links from that
state to others, basically modeling a FSM with actions as states and
forwards as trans
I have not used it yet, but you may want to take a look at spring web flow, it
is designed for these 'wizard' scenarios, and supposedly integrates well with
struts.
If you want to use Struts components only, one suggestion:
1 big action
1 big action form
Several jsps
The jsp form always posts
5 matches
Mail list logo
