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

------------------------------------------------------------------------------
  
  == Improving Setup/Submit Pattern ==
  
-  * Use !ActionForm object to store both input and output data. Use the same 
!ActionForm object in both setup and submit actions. Declaratively (via 
{{{struts-config.xml}}}) associate the action form with submit action only, do 
not associate the action form with setup action.
+ Use !ActionForm object to store both input and output data. Use the same 
!ActionForm object in both setup and submit actions. Declaratively (via 
{{{struts-config.xml}}}) associate the action form with submit action only, do 
not associate the action form with setup action.
+ 
-  * On setup phase, prepare the action form with output data and forward to a 
view. When a user submits HTML form, Struts will populate the action form that 
is associated with submit action. This is the same form that was used to render 
a page.
+ On setup phase, prepare the action form with output data and forward to a 
view. When a user submits HTML form, Struts will populate the action form that 
is associated with submit action. This is the same form that was used to render 
a page.
+ 
-  * If input data is not valid, do not redisplay the page from submit action. 
Instead, update application state if needed, generate error messages, and 
forward control to setup action. It is the job of setup action to prepare and 
display views; the job of submit action is to handle the input and to update 
application state.
+ If input data is not valid, do not redisplay the page from submit action. 
Instead, update application state if needed, generate error messages, and 
forward control to setup action. It is the job of setup action to prepare and 
display views; the job of submit action is to handle the input and to update 
application state.
+ 
-  * If action form was associated with setup action, it would be repopulated 
by Struts. Remember, that action form has not been associated with setup 
action, so it will not be repopulated when control is forwarded to setup action 
from submit action. Setup action will render the page along with error messages 
that have been generated by submit action.
+ If action form was associated with setup action, it would be repopulated by 
Struts. Remember, that action form has not been associated with setup action, 
so it will not be repopulated when control is forwarded to setup action from 
submit action. Setup action will render the page along with error messages that 
have been generated by submit action.
+ 
-  * Instead of forwarding to success '''page''', forward to '''setup action''' 
of success web resource.
+ Instead of forwarding to success '''page''', forward to '''setup action''' of 
success web resource.
  
  The above steps will allow to cleanly separate concerns between actions, as 
well as to keep input/output data in one place.
+ 
+ inline:setup_submit_improved.gif
  
  == Action As Event Dispatcher ==
  

Reply via email to