I hope you don't mind if I jump in on this thread, after reading the
documentation refered to below.
What is the S2 convention for loading up objects for use by the JSPs or other
view logic?
Imagine a common-place user story where the user sees a list of items, and can
choose one item, go to the 'edit item' page, submit changes, and be returned to
the item list.
On the edit submit, my action processes the edit and does a save, and does a
Post-Redirect-Get back to the list.
Where do I put the logic fetching the list again? Obviously I don't want it in
the edit action. Do I put it in an action of its own, or do I put it in an
interceptor or even a PreResultListener?
It seems that I can use a RedirectAction result type to do a Post-Redirect
straight back to the name of the action I want without needing to quote its URL.
That's the one I'm after, correct?
Adam
Wesslan on 05/11/06 06:19, wrote:
A REALLY simple architecture overview picture:
http://cwiki.apache.org/WW/home.html
A more detailed architecture overview:
http://cwiki.apache.org/WW/architecture.html
Hth,
Peter
-----Original Message-----
From: Mike Duffy [mailto:[EMAIL PROTECTED]
Sent: den 4 november 2006 18:04
To: user@struts.apache.org
Subject: Struts 2.0 Application Lifecycle
I've done a quick scan of the Struts 2.0 documentation. I did not find a
reference to the Struts 2.0 application life cycle.
Does anyone know of a reference that would be similar to the JSF article at
the link below?
http://www-128.ibm.com/developerworks/java/library/j-jsf2/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
