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 ------------------------------------------------------------------------------ throws Exception;}}} Since the majority of teams using the framework are focused on building web applications, most projects will only use the "!HttpServletRequest" version. A non-HTTP execute() method has been provided for applications that are not specifically geared towards the HTTP protocol. - - '''Example''' - - Consider the Action that performs a search. The author of this code should not bother neither about how exactly the search criteria is obtained, nor about how the search results are presented. His only job is to say "what happened" after the search took place. - - There are three interesting outcomes: - * No results were found => outcome "none". - * Exactly one result was found => outcome "single". - * More than one result was found => outcome "multiple". - - The search Action should return these three results as three separate logical outcomes. It is up to the application architect to decide to send all three outcomes to the "here's the list of responses" table page. It's also up to the application architect (perhaps later, in response to user feedback) to say "let's do this instead": - - * If there's no results, go to a page that says "sorry, no results were found, please try your search again." - * If there's exactly one response, go to the details page to display the corresponding data. - * If there's more than one response, go to the list page (as per the previous behavior). - - Note that the code of the search action is not affected by this decision. In Struts the outcomes returned by an action are much more stable than the presentation locations. On contrary, in ASP.NET the outcome is simply the page that was requested. == Using Action To Display A Web Page ==
