Author: husted
Date: Thu Nov 3 16:54:05 2005
New Revision: 330674
URL: http://svn.apache.org/viewcvs?rev=330674&view=rev
Log:
Update the "How Struts Core Works" FAQ for 1.3
Modified:
struts/core/trunk/xdocs/faqs/index.xml
struts/core/trunk/xdocs/faqs/works.xml
Modified: struts/core/trunk/xdocs/faqs/index.xml
URL:
http://svn.apache.org/viewcvs/struts/core/trunk/xdocs/faqs/index.xml?rev=330674&r1=330673&r2=330674&view=diff
==============================================================================
--- struts/core/trunk/xdocs/faqs/index.xml (original)
+++ struts/core/trunk/xdocs/faqs/index.xml Thu Nov 3 16:54:05 2005
@@ -21,11 +21,11 @@
</li>
<li>
- <a href="helping.html">How to Help FAQ</a>
+ <a href="http://struts.apache.org/helping.html";>How to Help FAQ</a>
</li>
<li>
- <a href="works.html">How does Struts work?</a>
+ <a href="works.html">How does Struts Core work?</a>
</li>
</ul>
Modified: struts/core/trunk/xdocs/faqs/works.xml
URL:
http://svn.apache.org/viewcvs/struts/core/trunk/xdocs/faqs/works.xml?rev=330674&r1=330673&r2=330674&view=diff
==============================================================================
--- struts/core/trunk/xdocs/faqs/works.xml (original)
+++ struts/core/trunk/xdocs/faqs/works.xml Thu Nov 3 16:54:05 2005
@@ -1,22 +1,22 @@
<?xml version="1.0"?>
<document url="./newbie.xml">
<properties>
-<title>How Does Struts Work? - Apache Struts</title>
+<title>How Does Struts Core Work? - Apache Struts</title>
</properties>
<body>
-<section href="faq" name="How does Struts work?">
+<section href="faq" name="How does Struts Core work?">
-<subsection href="how" name="How does Struts work?">
+<subsection href="how" name="How does Struts Core work?">
<p>
Java Servlets are designed to handle requests made by Web browsers.
- Java ServerPages are designed to create dynamic Web pages that can turn
billboard sites into live applications.
- Struts uses a special Servlet as a switchboard to route requests from Web
browsers to the appropriate ServerPage.
+ Server pages are designed to create dynamic Web pages that can turn
billboard sites into live applications.
+ Struts Core uses a special Servlet as a switchboard to route requests from
Web browsers to the appropriate server page.
This makes Web applications much easier to design, create, and maintain.
</p>
<p>
- Here is some more detail on the mechanisms and dependencies of Struts:
+ Here is some more detail on the mechanisms and dependencies of Struts Core:
</p>
<ul>
@@ -28,8 +28,8 @@
mappings to servlets (path or extension name), and parameters to those
servlets.<br/>
- In this file, you configure the Struts
- <a
href="../api/org/apache/struts/action/ActionServlet.html"><code>ActionServlet</code></a>
+ In this file, you configure the Struts Core
+ <a
href="../apidocs/org/apache/struts/action/ActionServlet.html"><code>ActionServlet</code></a>
as the servlet that will handle all requests for a given mapping (usually
the extension <code>.do</code>). This is the "switchboard" mentioned
above.<br/>
@@ -45,10 +45,10 @@
<a href="http://java.sun.com";>Java site</a>.<br/>
</li>
<li>
- In the Struts configuration file(s), you associate paths with
+ In the Struts Core configuration file(s), you associate paths with
the controller components of your application, known as
<a
href="../api/org/apache/struts/action/Action.html"><code>Action</code></a>
- classes (i.e. "login" ==> LoginAction class). This tells the Struts
+ classes (i.e. "login" ==> LoginAction class). This tells the
<code>ActionServlet</code> that when the incoming request is
<code>http://myhost/myapp/login.do</code> it should invoke your
controller component <code>LoginAction</code>.<br/>
@@ -60,7 +60,7 @@
executed.<br/>
</li>
<li>
- For each <code>Action</code>, you also configure Struts with the names of
+ For each <code>Action</code>, you also configure Struts Core with the
names of
the resulting page(s) that can be shown as a result of that action. There
can be more than one view as the result of an action (often, there are at
least two: one for success, and one for failure).<br/>
@@ -68,19 +68,19 @@
Your <code>Action</code> (the controller component you write) is based on
these <em>logical</em> result mapping names. It reports back to the
<code>ActionServlet</code> using words like "success", "failure",
- "ready", "ok", "UserIsIncompetent", etc. The Struts system (through the
+ "ready", "ok", "UserError", et cetera. Struts Core (through the
configuration that you wrote) knows how to forward to the proper
<em>specific</em> page. This has the added advantage of reconfiguration
of
- the view layer by simply editing the Struts XML configuration file.<br/>
+ the view layer by simply editing the XML configuration file.<br/>
- At this point Struts knows how to delegate to your controller components,
+ At this point Struts Core knows how to delegate to your controller
components,
and what to show as a result of your controller processing. The "model"
part of the application is completely up to you, and is called from
within your controller components.
</li>
<li>
You may also associate a Java Bean with an action (or set of actions) in
- the Struts configuration file. The Java Bean is used as a repository for
+ the Struts Core configuration file. The Java Bean is used as a
repository for
form or display data that can be communicated between the view and
controller layer.<br/>
@@ -88,29 +88,29 @@
(like <code>LoginAction</code>) and any view page that is associated with
that controller. <br/>
- These Beans can also be validated with the help of the Struts system to
+ These Beans can also be validated with the help of Struts Core to
help insure that the user is putting good data in the form. They can be
carried along with a session, allowing forms to span multiple pages of
the view, and Actions in the controller.<br/>
<strong>Note</strong>: You must be using some sort of server-side
technology (JSP, Velocity, XSLT) for the view layer (going <em>to</em>
the
- client) to see this data (plain HTML won't work). Struts works on the
+ client) to see this data (plain HTML won't work). Struts Core works on
the
server side, so the client's view has to be composed there.<br/>
The client feeds the data back through normal form submission (POST/GET)
- methods, and the Struts system updates that data in the Bean before
+ methods, and Struts Core updates that data in the Bean before
calling your controller components.
</li>
<li>
Within your web application will be pages that represent the view your
users will see. These can be JSP pages, Velocity Templates,
XSLT pages, and so forth.
- A set of JSP tags is bunded with the Struts distribution so that you
+ Sets of JSP and JSTL tags are available for Struts Core so that you
can get started right away, but any standard presentation technology
- can be used with Struts.<br/>
+ can be used with Struts Core.<br/>
- Even plain HTML files can be used within your Struts application,
+ Even plain HTML files can be used within your Struts Core application,
although they will not take full advantage of all of the dynamic
features.<br/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
