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 ------------------------------------------------------------------------------ * 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:action_code_behind.gif + + It is possible to combine processing of both submit and render phases in one Action class, or to split this functionality into two Action classes. Instead of relying on one execute() method a code-behind class uses event handlers for different incoming events. + {{{<action path = "/login" type = "samples.login.LoginAction" name = "loginform" @@ -76, +80 @@ <forward name = "loggedin" path = "/logout.jsp" /> </action>}}} - It is possible to combine processing of both submit and render phases in one Action class, or to split this functionality into two Action classes. Instead of relying on one execute() method a code-behind class uses event handlers for different incoming events. - == Action As A Web Component == A web component differs from a web resource in that a component is visually a part of a larger ''composite page''. As such a web component does not need to navigate to a next location. Instead, a web component must either update itself on a composite page in place or reload the whole page after the component updated its state. In-place updating is facilitated using Javascript/XMLHttpRequest (Ajax mode), while full page reload is used if Javascript is turned off on a browser.
