husted 2002/10/11 22:15:58
Modified: doc/userGuide building_controller.xml
Log:
New 1.1 sections contributed by Eddie Bush.
Revision Changes Path
1.32 +10 -9 jakarta-struts/doc/userGuide/building_controller.xml
Index: building_controller.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/building_controller.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- building_controller.xml 12 Oct 2002 05:05:26 -0000 1.31
+++ building_controller.xml 12 Oct 2002 05:15:58 -0000 1.32
@@ -321,7 +321,7 @@
process user requests, determine what the user is trying to achieve
according to the request, pull data from the model (if necessary) to
be given to the appropriate view, and then select the proper view
- to respond to the user. The Struts controller delegates most of this
+ to respond to the user. The Struts controller delegates most of this
grunt work to Action classes.
</p>
<p>
@@ -352,13 +352,14 @@
process method, passing the same request and response.
</p>
</section>
+
<section name="4.4.1 Request Processor" href="request_processor">
<p>
The RequestProcessor is where the majority of the core
processing occurs for each request. Let's take a look at the
helper functions the process method invokes in-turn:
- </p>
- ul>
+ </p>
+ <ul>
<li><code>processPath</code> Determine the path that invoked us. This
will be used later to retrieve an ActionMapping.</li>
<li><code>processLocale</code> Select a locale for this request, if one
@@ -366,7 +367,7 @@
<li><code>processContent</code> [:TODO:]</li>
<li><code>processNoCache</code> If appropriate, set the following response
headers: "Pragma", "Cache-Control", and "Expires".</li>
- <li><code>processPreprocess</code> This is one of the "hooks" the
+ <li><code>processPreprocess</code> This is one of the "hooks" the
RequestProcessor makes available for subclasses to override. The
default implementation simply returns true. If you subclass
RequestProcessor and override processPreprocess you should either
@@ -395,8 +396,8 @@
action's perform or execute method will be called.</li>
<li><code>processActionForward</code> Finally, the process method of the
RequestProcessor takes the ActionForward returned by your
- Action class, and uses to select the next resource (if any).
- Most often the ActionForward leads to the presentation page that
+ Action class, and uses to select the next resource (if any).
+ Most often the ActionForward leads to the presentation page that
renders the response. </li>
</ul>
</section>
@@ -415,10 +416,10 @@
the web application is starting up.
</p>
<p>
- At runtime, any resource setup by <code>init</code> would be accessed by
Actions
+ At runtime, any resource setup by <code>init</code> would be accessed by
Actions
or business tier classes. The PlugIn interface allows you to setup
- resources, but does not provide any special way to access them. Most
- often, the resource would be stored in application context, under
+ resources, but does not provide any special way to access them. Most
+ often, the resource would be stored in application context, under
a known key, where other components can find it.</p>
<p>
PlugIns are configured using <plug-in> elements within the
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
