Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Struts Wiki" for change 
notification.

The following page has been changed by MichaelJouravlev:
http://wiki.apache.org/struts/StrutsManualActionClasses

------------------------------------------------------------------------------
   * Update the server-side objects that will be used to create the next page 
of the user interface. These objects would typically be request scope or 
session scope beans, depending on how long you need to keep these items. 
   * Return an appropriate !ActionForward object that identifies the next web 
resource.
  
+ The flip side of Struts flexibility is greater complexity of a most common 
use case of a web application.
- The flip side of Struts flexibility is greater complexity of a most common 
request/response cycle comparing to similar ASP.NET request/response cycle:
- 
- inline:asp_render_submit.gif
  
  == Action As Event Dispatcher ==
  
@@ -114, +112 @@

   * handles different commands and events corresponding to a web resource 
(submit phase), and
   * selects an appropriate view based on current state of web resource (render 
phase).
  
- inline:web_resource.gif
+ Implementing both input and output phases as well as event handlers in one 
Action class brings the complexity of Struts web form management down to the 
level of ASP.NET.
  
- 
- == Action As Stateful Web Resource Manager ==
- 
- A stateful web resource stores its data in a session scope, usually in a 
session-scoped form bean associated with Action. This allows to use redirection 
without losing the data. Redirection can be used to render a view: submit 
action redirects to setup action instead of forwarding to it.
- 
- If you can live with session-scoped data, your web application will sport 
much cleaner and user-friendly interface:
- 
- * A web resource will have only one URL, the setup URL. Submit URL will be 
cleared by browser right after redirection.
- * Navigating back and forward, as well as reloading a view is safe and does 
not cause resubmit.
- * Several unsuccessful submit attempts to not accumulate in browser page 
history.
- 
- inline:stateful_web_resource.gif
+ inline:web_resource_asp.gif
  
  == Action As Web Component Manager ==
  

Reply via email to