Mark Menard has done some work in this area for struts2:
http://www.vitarara.org/cms/node/84
For webwork I implemented something similar called a model repository.
The problem that's being solved is that when the domain model reaches a
certain complexity, using the null instantiation feature and reading the
model from the database again fail to work. The basic idea of the model
repository was to save off the domain model somewhere (e.g. serial to a
hidden field on the client, in an ehcache cache, in the session) before
you go to the edit screen. When the data is posted back, before the
parameter interceptor runs, you restore the model. This allows you to
set the parameters back onto exactly the same model you edited.
I like the idea of expanding the model repository idea to include the
concept of conversation scope, but I don't want to loose simplicity of
model repository. I'll probably create a plugin at some point to
provide this functionality.
Finally, there's also the scope interceptor that Don wrote that is still
in the sandbox.
Of course, all of this is for struts 2, so it doesn't do you any good
for 1.4. :o)
Paul Benedict wrote:
How often do people develop wizards with Struts? I have a custom
form/action which allows me to do that. Perhaps I should think about
putting it into Struts 1.4?
Strachan, Paul wrote:
Hi,
I'm looking at implementing a struts wizard flow (of about 12 pages)
into my struts-1.2.9 application. The struts dialogue project seems
to be along the lines of what I need (pattern-wise). I have some
extra quirements such as:
1. A progress menu (synch with the wizard)
2. Some pages have options (eg radio buttons) which alter the later flow
3. The usual next/previous buttons + ability for user to navigate
directly to some pages
4. A review page which allow user to 'amend' sections (eg button to
navigate back to that page)
5. Once the wizard is complete (ie "submitted for processing"), the
user can still make changes to some pages while not others (actually
this depends a bit on the current state of the internal processing) -
I suspect each page needs to obtain its own state dynamically and
present a read-only or update view.
Can anyone advise there experience with struts-dialog (sourceforge)
or some other wizard or workflow framework/model that would suit this
requirement?
Thanks,
Paul
**********************************************************************
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
