Internally there are two types of actions that get processed in the running of a WebApp.
These two actions are page and method. When a WebApp is run it is through these actions that the execution takes place.
All of the non-page execution code such as Method, ActionList/Action and Method Call are converted to Java source code. The code is compiled to generate a single java class for each unique variation of a WebApp. At runtime, the class is instantiated and can then be executed by using the WebAppAccess callMethod API. The same method action that runs the generated Java methods is also used to invoke linked Java object methods. Page
All Page execution goes through the page action, which will detect the page type and pass the processing to the correct page processor. Currently there are two types of page processor. One is the JSP page processor, which will be executed by the host server, and the second is a static page processor, which does no real processing, but does send the page directly back to the client.Action Lists
Action lists hold a list of action items such as method call, assignment operations, process page calls, and return statements. ActionLists are converted to Java methods, so as far as the runtime is concerned they are treated just like any other method described above.
Parent topic: WebApp execution: wpf7