DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15673>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15673

Default Action in ActionMapping





------- Additional Comments From [EMAIL PROTECTED]  2002-12-26 23:49 -------
The global success doesn't really work for me since I prefer to leave the data 
on the screen that resulted in a success.  I am using the ValidationErrors to 
return 'success' to the page which satisfies that need.  Also, I am using the 
controller for smaller actions which don't necessarily result in a 'success'.

Suppose you have a 'customer entry' series of screens surrounding a fairly 
complex form.  Also suppose you would like to write generic action classes for 
complex forms.  Also assume that the action class is decomposing standard form 
data to determine the action to perform (there are dozens of potential 
actions).  The first requirement is an extension of ActionForm which has all 
the 'standard' actions and also maintains action state.  You start the action 
sequence with a populate action to fill the form and forward to the action 
controller.  After the first action the action controller will know the jsp 
page to forward to since the page would be requesting a page change.  The 
problem is for the first page, since there could be multiple jsp's required to 
fill the form, which one do you start the entry on?  As I mentioned, my current 
implementation starts with input (normally used for validation).

Hope, that helps.

Edgar

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to