Within struts, are wizards just a progression of actions/actionforms? Is there a
framework for building wizards
or does everyone just do their own thing?
I've got a situation where I have multiple wizards and many of them may be invoked
from other wizards,
creating a cascade of wizards. What I mean is that while completing wizard A, one may
be able to branch
to wizard B, etc. When completing the last wizard, I need to be able to make sure
that I go back to which ever
wizard the last one was launched from. This means that the action mapping (forward
map???) is not fixed,
but programmatically variable. Please don't ding me on design principles here, this
is a customer requirement,
since we're trying to integrate with another product that does this and their users
are used to being able to do this.
Am I on my own as far as making this work, or is there some sort of struts mechanism
to do this???
Wayne Christian
Sr. Staff Software Engineer
Genesys Telecommunications Labs
2100 Gateway Centre Blvd. Suite 300
Morrisville, NC 27560
? Office: (919) 466-6151
Fax: (919) 466-6157
? EMail: mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
