You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by hu...@apache.org on 2004/03/12 06:19:46 UTC
cvs commit: jakarta-struts/web/example/WEB-INF struts-config-registration.xml struts-config.xml validation.xml
husted 2004/03/11 21:19:46
Modified: web/example Registration.jsp changePassword.jsp footer.jsp
index.jsp logon.jsp mainMenu.jsp subscription.jsp
tour.html welcome.jsp
web/example/WEB-INF struts-config-registration.xml
struts-config.xml validation.xml
Log:
Conform case.
Revision Changes Path
1.5 +4 -4 jakarta-struts/web/example/Registration.jsp
Index: Registration.jsp
===================================================================
RCS file: /home/cvs/jakarta-struts/web/example/Registration.jsp,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Registration.jsp 9 Mar 2004 04:35:01 -0000 1.4
+++ Registration.jsp 12 Mar 2004 05:19:45 -0000 1.5
@@ -24,7 +24,7 @@
<html:errors/>
-<html:form action="/saveRegistration" focus="username"
+<html:form action="/SaveRegistration" focus="username"
onsubmit="return validateRegistrationForm(this);">
<html:hidden property="action"/>
<table border="0" width="100%">
@@ -156,10 +156,10 @@
<bean:write name="subscription" property="autoConnect"/>
</td>
<td align="center">
- <app:linkSubscription page="/editSubscription.do?action=Delete">
+ <app:linkSubscription page="/EditSubscription.do?action=Delete">
<bean:message key="registration.deleteSubscription"/>
</app:linkSubscription>
- <app:linkSubscription page="/editSubscription.do?action=Edit">
+ <app:linkSubscription page="/EditSubscription.do?action=Edit">
<bean:message key="registration.editSubscription"/>
</app:linkSubscription>
</td>
@@ -168,7 +168,7 @@
</table>
-<html:link action="/editSubscription?action=Create" paramId="username"
+<html:link action="/EditSubscription?action=Create" paramId="username"
paramName="RegistrationForm" paramProperty="username">
<bean:message key="registration.addSubscription"/>
</html:link>
1.4 +1 -1 jakarta-struts/web/example/changePassword.jsp
Index: changePassword.jsp
===================================================================
RCS file: /home/cvs/jakarta-struts/web/example/changePassword.jsp,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- changePassword.jsp 7 Mar 2004 20:29:31 -0000 1.3
+++ changePassword.jsp 12 Mar 2004 05:19:45 -0000 1.4
@@ -10,7 +10,7 @@
<body bgcolor="white">
<bean:message key="change.message"/>
-<html:link action="/logon">
+<html:link action="/Logon">
<bean:message key="change.try"/>
</html:link>
1.2 +1 -1 jakarta-struts/web/example/footer.jsp
Index: footer.jsp
===================================================================
RCS file: /home/cvs/jakarta-struts/web/example/footer.jsp,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- footer.jsp 9 Mar 2004 04:35:01 -0000 1.1
+++ footer.jsp 12 Mar 2004 05:19:45 -0000 1.2
@@ -1,4 +1,4 @@
<%@ taglib uri="/tags/struts-bean" prefix="bean" %>
<%@ taglib uri="/tags/struts-html" prefix="html" %>
<hr />
-<p><html:link action="welcome"><bean:message key="index.title"/></html:link></p>
+<p><html:link action="/Welcome"><bean:message key="index.title"/></html:link></p>
1.22 +4 -4 jakarta-struts/web/example/index.jsp
Index: index.jsp
===================================================================
RCS file: /home/cvs/jakarta-struts/web/example/index.jsp,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- index.jsp 9 Mar 2004 04:35:01 -0000 1.21
+++ index.jsp 12 Mar 2004 05:19:45 -0000 1.22
@@ -1,5 +1,5 @@
<%@ taglib uri="/tags/struts-logic" prefix="logic" %>
-<logic:redirect action="/welcome"/>
+<logic:redirect action="/Welcome"/>
<%--
Redirect default requests to Welcome action.
By using a redirect, the user-agent will change address to match the path of our Welcome action.
1.27 +2 -2 jakarta-struts/web/example/logon.jsp
Index: logon.jsp
===================================================================
RCS file: /home/cvs/jakarta-struts/web/example/logon.jsp,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- logon.jsp 12 Mar 2004 02:44:34 -0000 1.26
+++ logon.jsp 12 Mar 2004 05:19:45 -0000 1.27
@@ -10,7 +10,7 @@
<html:errors/>
-<html:form action="/submitLogon" focus="username"
+<html:form action="/SubmitLogon" focus="username"
onsubmit="return validateLogonForm(this);">
<table border="0" width="100%">
@@ -46,7 +46,7 @@
</html:form>
-<html:javascript formName="logonForm"
+<html:javascript formName="LogonForm"
dynamicJavascript="true"
staticJavascript="false"/>
<script language="Javascript1.1" src="staticJavascript.jsp"></script>
1.17 +1 -1 jakarta-struts/web/example/mainMenu.jsp
Index: mainMenu.jsp
===================================================================
RCS file: /home/cvs/jakarta-struts/web/example/mainMenu.jsp,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- mainMenu.jsp 7 Mar 2004 20:29:31 -0000 1.16
+++ mainMenu.jsp 12 Mar 2004 05:19:45 -0000 1.17
@@ -15,7 +15,7 @@
<h3><bean:message key="mainMenu.heading"/>
<jsp:getProperty name="user" property="username"/></h3>
<ul>
-<li><html:link action="/editRegistration?action=Edit"><bean:message key="mainMenu.registration"/></html:link></li>
+<li><html:link action="/EditRegistration?action=Edit"><bean:message key="mainMenu.registration"/></html:link></li>
<li><html:link forward="logoff"><bean:message key="mainMenu.logoff"/></html:link></li>
</ul>
1.32 +10 -10 jakarta-struts/web/example/subscription.jsp
Index: subscription.jsp
===================================================================
RCS file: /home/cvs/jakarta-struts/web/example/subscription.jsp,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- subscription.jsp 7 Mar 2004 20:29:31 -0000 1.31
+++ subscription.jsp 12 Mar 2004 05:19:45 -0000 1.32
@@ -7,15 +7,15 @@
<html:html>
<head>
-<logic:equal name="subscriptionForm" property="action"
+<logic:equal name="SubscriptionForm" property="action"
scope="request" value="Create">
<title><bean:message key="subscription.title.create"/></title>
</logic:equal>
-<logic:equal name="subscriptionForm" property="action"
+<logic:equal name="SubscriptionForm" property="action"
scope="request" value="Delete">
<title><bean:message key="subscription.title.delete"/></title>
</logic:equal>
-<logic:equal name="subscriptionForm" property="action"
+<logic:equal name="SubscriptionForm" property="action"
scope="request" value="Edit">
<title><bean:message key="subscription.title.edit"/></title>
</logic:equal>
@@ -25,7 +25,7 @@
<html:errors/>
-<html:form action="/saveSubscription" focus="host">
+<html:form action="/SaveSubscription" focus="host">
<html:hidden property="action"/>
<table border="0" width="100%">
@@ -43,11 +43,11 @@
<bean:message key="prompt.mailHostname"/>:
</th>
<td align="left">
- <logic:equal name="subscriptionForm" property="action"
+ <logic:equal name="SubscriptionForm" property="action"
scope="request" value="Create">
<html:text property="host" size="50"/>
</logic:equal>
- <logic:notEqual name="subscriptionForm" property="action"
+ <logic:notEqual name="SubscriptionForm" property="action"
scope="request" value="Create">
<html:hidden property="host" write="true"/>
</logic:notEqual>
@@ -95,19 +95,19 @@
<tr>
<td align="right">
- <logic:equal name="subscriptionForm" property="action"
+ <logic:equal name="SubscriptionForm" property="action"
scope="request" value="Create">
<html:submit>
<bean:message key="button.save"/>
</html:submit>
</logic:equal>
- <logic:equal name="subscriptionForm" property="action"
+ <logic:equal name="SubscriptionForm" property="action"
scope="request" value="Delete">
<html:submit>
<bean:message key="button.confirm"/>
</html:submit>
</logic:equal>
- <logic:equal name="subscriptionForm" property="action"
+ <logic:equal name="SubscriptionForm" property="action"
scope="request" value="Edit">
<html:submit>
<bean:message key="button.save"/>
@@ -115,7 +115,7 @@
</logic:equal>
</td>
<td align="left">
- <logic:notEqual name="subscriptionForm" property="action"
+ <logic:notEqual name="SubscriptionForm" property="action"
scope="request" value="Delete">
<html:reset>
<bean:message key="button.reset"/>
1.8 +55 -50 jakarta-struts/web/example/tour.html
Index: tour.html
===================================================================
RCS file: /home/cvs/jakarta-struts/web/example/tour.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- tour.html 12 Mar 2004 02:44:34 -0000 1.7
+++ tour.html 12 Mar 2004 05:19:45 -0000 1.8
@@ -60,9 +60,9 @@
<a href="#subscription.jsp">registration.jsp</a>
<ul>
- <li><a href="#registrationForm.java">RegistrationForm.java</a></li>
+ <li><a href="#RegistrationForm.java">RegistrationForm.java</a></li>
- <li><a href="#editRegistrationAction.java">EditRegistrationAction.java</a></li>
+ <li><a href="#EditRegistrationAction.java">EditRegistrationAction.java</a></li>
<li><a href="#LinkSubscriptionTag.java">LinkSubscriptionTag.java</a></li>
@@ -90,6 +90,14 @@
<p>The premise of the MailReader is that it is the first iteration of a portal application. This version allows users to register themselves and maintain a set of accounts with various mail servers. When completed, the application would let users read mail from their accounts.</p>
+ <p>The MailReader application demonstrates registering with an application, logging into an application, maintaining a master record, and maintaining child records. This document walks through the JSP pages, Struts Java classes, and Struts configuration elements needed to do these things.</p>
+
+ <blockquote>
+ <p>Note that for compatability and ease of deployment, the MailReader uses "application-based" authorization. However, use of the standard Java Authentication and Authorization Service (JAAS) is recommended for most applications. (See the <a href="http://jakarta.apache.org/struts/userGuide/preface.html">Preface to the Struts User Guide</a> for more about authentification technologies.)</p>
+ </blockquote>
+
+ <p>The walkthrough starts with how the initial welcome page is displayed, and then steps through logging in, adding and editing subscriptions, and creating a new registration.</p>
+
<h3><a name="index.jsp" id="index.jsp">index.jsp</a></h3>
<p>A web application, like any other web site, can specify a list of welcome pages. When you open a web application without specifying a particular page, a welcome page is used by default.</p>
@@ -120,7 +128,7 @@
</pre>
<hr />
- <p>If someone asked for the welcome action ("/welcome.do"), the welcome.jsp page would be displayed in return.</p>
+ <p>If someone asked for the welcome action ("/Welcome.do"), the welcome.jsp page would be displayed in return.</p>
<h4><a name="WelcomeAction.java" id="WelcomeAction.java">WelcomeAction.java</a></h4>
@@ -266,9 +274,7 @@
<p>If you choose the logon link, the Logon action forwards control to the logon.jsp page. The logon page displays a form that accepts a username and password. You can use the default username and password to logon (user and pass). Note that both the username and password are case sensitive. Better yet, try omitting or misspelling the username and password in various combinations and see how the application reacts.</p>
- <p>Once you enter the correct username and password combination, the LogonAction will send you to the main menu. Note that whatever username you entered before is defaulted on the form.</p>
-
- <p>Now that we've gotten through a logon, let's backtrack and take a look at the logon.jsp.</p>
+ <p>Here's how the login.jsp is coded:</p>
<hr />
<pre>
<code><%@ page contentType="text/html;charset=UTF-8" language="java" %>
@@ -319,7 +325,7 @@
</html:form>
-<html:javascript formName="logonForm"
+<html:javascript formName="LogonForm"
dynamicJavascript="true"
staticJavascript="false"/>
<script language="Javascript1.1" src="staticJavascript.jsp"></script>
@@ -332,17 +338,17 @@
<p>We saw some of these tags on the welcome page. Let's focus on the new tags.</p>
- <p>The first new tag on the logon page is html:errors. If a person enters incorrect credentials, then the LogonAction will post an appropriate error message. If the html:errors tag sees that one or more messages were posted, the tag ouputs the messages to the page. The text of the messages can be specified in the MessageResource bundle, making them easy to internationalize.</p>
+ <p>The first new tag on the logon page is "html:errors". The credentials you entered are processed by a "LogonAction" class. If the credentials are incorrect, the LogonAction posts an appropriate error message and forwards back to the input page. If the html:errors tag sees that one or more messages were posted, the tag ouputs the messages to the page. The text of the messages can be specified in the MessageResource bundle, making them easy to internationalize.</p>
- <p>The second new tag is html:form. This tag renders a html form tag. The "action" element tells the tag to use "logonSubmit.do" for the form's action. The "focus" attribute tells the tag to generate a little Javascript after the form that sets its focus to the "username" field. The "onsubmit" attribute tells the form to run a Javascript when the form is submitted. (Just like the corresponding attribute on the standard form tag.)</p>
+ <p>The second new tag is "html:form". This tag renders a html form tag. The "action" element tells the tag to use "SubmitLogon.do" for the form's action. The "focus" attribute tells the tag to generate a little Javascript after the form that sets its focus to the "username" field. The "onsubmit" attribute tells the form to run a Javascript when the form is submitted. (Just like the corresponding attribute on the standard form tag.)</p>
<p>Within the html:form tag, we see four other new tags: "html:text", "html:password", "html:submit", and "html:reset".</p>
<p>The html:text tag renders a "input type=text" tag. The "property" attribute becomes the input tag's "name" attribute.</p>
- <p>The html:password tag renders a "input type=password" tag. The "redisplay" attribute tell the tag not to render the password back into the file, if the submit fails. The html:submit and html:reset tags renders buttons of the corresponding types.</p>
+ <p>The html:password tag renders a "input type=password" tag. The "redisplay" attribute tell the tag not to render the password back into the file, if the submit fails. The html:submit and html:reset tags render buttons of the corresponding types.</p>
- <p>Following the form is a html:javascript tag. This tag works with the Struts Validator component to generate a JavaScript that can validate input before it is submitted to the LogonAction.</p>
+ <p>Following the form is a "html:javascript" tag. This tag works with the Struts Validator component to generate a JavaScript that can validate input before it is submitted to the LogonAction.</p>
<blockquote>
<p><font class="note">Most of these tags have many more options than the ones we use in this application. For the complete documentation for each tag, see the Tag Developers Guides in the Struts documentation bundle.</font></p>
@@ -350,23 +356,23 @@
<p>But, how do these tags know so much? How does the Javascript tag know what scripts to write? How do the text and password tags know what values to redisplay?</p>
- <p>For the answers, we need to turn to the Struts configuration files.</p>
+ <p>For the answers, we need to turn to the Struts configuration files, "struts-config.xml" and "validation.xml".</p>
<h4><a name="struts-config.xml" id="struts-config.xml">struts-config.xml</a></h4>
- <p>In the struts-config.xml file, we find an element for the "/logonSubmit" action</p>
+ <p>In the struts-config.xml file, we find an element for the "/SubmitLogon" action</p>
<hr />
<pre>
<code><!-- Process a user logon -->
<action path="/submitLogon"
type="org.apache.struts.webapp.example.LogonAction"
- name="logonForm"
+ name="LogonForm"
scope="request"
input="logon">
<exception
key="expired.password"
type="org.apache.struts.webapp.example.ExpiredPasswordException"
- path="/expiredPassword.do"/>
+ path="/ExpiredPassword.do"/>
</action></code>
</pre>
<hr />
@@ -375,10 +381,10 @@
<p>The "name" attribute specifies something Struts calls an "ActionForm". The ActionForm buffers input from a form and delivers it to an Action class as an object. The ActionForm can also validate the input. If validation fails, the tags can rewrite the input values from the ActionForm.</p>
- <p>The ActionForms are defined in the "formbeans" section of the configuration file. Here's the formbean element for the "logonForm".</p>
+ <p>The ActionForms are defined in the "formbeans" section of the configuration file. Here's the formbean element for the "LogonForm".</p>
<hr />
<pre>
-<code><form-bean name="logonForm"
+<code><form-bean name="LogonForm"
type="org.apache.struts.validator.DynaValidatorForm">
<form-property name="username" type="java.lang.String"/>
<form-property name="password" type="java.lang.String"/>
@@ -397,7 +403,7 @@
<p>Struts can also validate the ActionForm automatically. If validation fails, Struts looks for the forward specified by the "input" attribute. In this case, the "logon" forward sends control back to the input.jsp page.</p>
<hr />
<pre>
-<code><forward name="logon" path="/logon.do"/></code>
+<code><forward name="logon" path="/Logon.do"/></code>
</pre>
<hr />
@@ -405,10 +411,10 @@
<h4><a name="validations.xml" id="validations.xml">validations.xml</a></h4>
- <p>In the logon.jsp, we mentioned that the html:javascript tag confers with the Struts Validator components. The Validator is configured through another XML document, the "validation.xml". Here's the element for our logonForm:</p>
+ <p>In the logon.jsp, we mentioned that the html:javascript tag confers with the Struts Validator components. The Validator is configured through another XML document, the "validation.xml". Here's the element for our LogonForm:</p>
<hr />
<pre>
-<code><form name="logonForm">
+<code><form name="LogonForm">
<field property="username"
depends="required">
@@ -442,13 +448,12 @@
<h4><a name="LogonAction.java" id="LogonAction.java">LogonAction.java</a></h4>
- <p>If validation passes, the logonForm is forwarded to the LogonAction. The LogonAction interacts with the database to see if the credentials are valid. If so, the user is logged on, and control passes to the "success" forward. Otherwise, control is forwarded to the input page and the list of error messages displayed.</p>
+ <p>If validation passes, the LogonForm object is forwarded to the LogonAction. The LogonAction interacts with the database to see if the credentials are valid. If so, the user is logged on, and control passes to the "success" forward. Otherwise, control is forwarded to the input page and the list of error messages displayed.</p>
<p>Here's the LogonAction (sans comments):</p>
-
<hr />
-
-<pre><code>package org.apache.struts.webapp.example;
+ <pre>
+<code>package org.apache.struts.webapp.example;
import ...
public final class LogonAction extends BaseAction {
@@ -468,7 +473,7 @@
}
else {
user = database.findUser(username);
- if ((user != null) && !user.getPassword().equals(password)) {
+ if ((user != null) && !user.getPassword().equals(password)) {
user = null;
}
if (user == null) {
@@ -522,9 +527,9 @@
return (findSuccess(mapping));
- }</code></pre>
-
- <hr />
+ }</code>
+</pre>
+ <hr />
<h4><a name="mainMenu.jsp" id="mainMenu.jsp">mainMenu.jsp</a></h4>
@@ -536,10 +541,10 @@
<li>Log off MailReader Demonstration Application</li>
</ul>
- <p>If you check the page path shown by your browser, you will see that it shows "logon.do" not "mainMenu.jsp". This is because the page was loaded as the ultimate result of the logon.do request, so for all the browser knows, that's where you are. This is why the base custom tag is important. If your page included relative links to images, your browser would be trying to make them based on the path to "logon.do". So the Struts base tag saves the day by telling the browser to resolve relative links based on the path to the file Struts returned, rather than on the "file" the browser requested.</p>
+ <p>If you check the page path shown by your browser, you will see that it shows "Logon.do" not "mainMenu.jsp". This is because the page was loaded as the ultimate result of the Logon.do request, so for all the browser knows, that's where you are. This is why the base custom tag is important. If your page included relative links to images, your browser would be trying to make them based on the path to "Logon.do". So the Struts base tag saves the day by telling the browser to resolve relative links based on the path to the file Struts returned, rather than on the "file" the browser requested.</p>
<blockquote>
- <p><i>If you have a sharp eye, you also may have noticed that logon.do is not followed by any parameters from the login form (logon.do?username=user). The default method for a from created with the Struts form tag is POST, which does not append form parameters to the request path, as GET does. This is the opposite of the HTML form tag, which uses GET by default.</i></p>
+ <p><i>If you have a sharp eye, you also may have noticed that logon.do is not followed by any parameters from the login form (Logon.do?username=user). The default method for a from created with the Struts form tag is POST, which does not append form parameters to the request path, as GET does. This is the opposite of the HTML form tag, which uses GET by default.</i></p>
</blockquote>
<h3><a name="mainMenu.jsp" id="mainMenu.jsp">mainMenu.jsp</a></h3>
@@ -562,7 +567,7 @@
<p><i>Unfortunately, some of the application's model is exposed by this page view. Struts goes a long way toward minimizing this sort of thing, but in some cases it is unavoidable.</i></p>
</blockquote>
- <p>The other links we've seen have either gone directly to a JSP file, or to a Struts action path, like login.do. The "Edit your user registration profile" link is a little different, since it also uses a parameter, as in editRegistration.do?action=Edit. When the Struts ActionServlet processes this link, it will ignore the parameter for the purpose of matching the request, but still pass the parameter along to action's object.</p>
+ <p>The other links we've seen have either gone directly to a JSP file, or to a Struts action path, like Login.do. The "Edit your user registration profile" link is a little different, since it also uses a parameter, as in EditRegistration.do?action=Edit. When the Struts ActionServlet processes this link, it will ignore the parameter for the purpose of matching the request, but still pass the parameter along to action's object.</p>
<blockquote>
<p><i>This means that in Struts, an action object must be able to handle every valid parameter for it's base path. (In the Example, editRegistration <b>must</b> handle both Edit and Create.)</i></p>
@@ -570,17 +575,17 @@
<p><i>You may want to check for invalid parameters too. (And be careful of differences in case if your comparisons are not case insensitive!)</i></p>
</blockquote>
- <p>If you check the struts-config.xml, you'll see that the editRegistration action is mapped to the (surprise again!), the EditRegistrationAction; it uses a registrationForm bean, and registration.jsp for input.</p>
+ <p>If you check the struts-config.xml, you'll see that the editRegistration action is mapped to the (surprise again!), the EditRegistrationAction; it uses a RegistrationForm bean, and registration.jsp for input.</p>
<blockquote>
<p><code><!-- Registration form bean --><br />
- <form-bean name="registrationForm"<br />
+ <form-bean name="RegistrationForm"<br />
type="org.apache.struts.webapp.example.RegistrationForm"/></code></p>
<p><code><!-- Edit user registration --><br />
<action path="/editRegistration"<br />
type="org.apache.struts.webapp.example.EditRegistrationAction"<br />
- name="registrationForm"<br />
+ name="RegistrationForm"<br />
scope="request"<br />
validate="false"<br />
input="/registration.jsp"><br />
@@ -606,7 +611,7 @@
<blockquote>
<p><code><logic:equal<br />
- name="registrationForm"<br />
+ name="RegistrationForm"<br />
property="action"<br />
scope="request"<br />
value="Edit"<br />
@@ -614,10 +619,10 @@
<app:checkLogon/><br />
</logic:equal></code></p>
- <p><i>Note that the Struts html:form tag will refer to properties set by struts-config.xml and automatically create a registrationForm bean if one is not present. However, that does not happen until the form tag is processed within the page. Since this block appears before the html:form tag, a runtime error is exposed if you try to access registration.jsp directly (rather then going through the editRegistration.do action).</i></p>
+ <p><i>Note that the Struts html:form tag will refer to properties set by struts-config.xml and automatically create a RegistrationForm bean if one is not present. However, that does not happen until the form tag is processed within the page. Since this block appears before the html:form tag, a runtime error is exposed if you try to access registration.jsp directly (rather then going through the EditRegistration.do action).</i></p>
</blockquote>
- <p>registation.jsp continues to use logic tags throughout the page so that a single JSP can be used to perform more than one task. For example, if you are editing the form (action == "Edit"), the page inserts your username from the registrationForm bean. If you are new user (action == "Create"), the page creates an empty field, so you can pick your username.</p>
+ <p>registation.jsp continues to use logic tags throughout the page so that a single JSP can be used to perform more than one task. For example, if you are editing the form (action == "Edit"), the page inserts your username from the RegistrationForm bean. If you are new user (action == "Create"), the page creates an empty field, so you can pick your username.</p>
<blockquote>
<p><i>The Struts logic tags are a very convenient way to express application logic within your pages. This prevents user error and reduces the number of JSPs your application needs to maintain, among other benefits.</i></p>
@@ -627,7 +632,7 @@
<blockquote>
<p><code><logic:equal<br />
- name="registrationForm"<br />
+ name="RegistrationForm"<br />
property="action"<br />
scope="request"<br />
value="Edit"<br />
@@ -690,11 +695,11 @@
<bean:write name="subscription" property="autoConnect"/><br />
</td><br />
<td align="center"><br />
- <app:linkSubscription page="/editSubscription.do?action=Delete"><br />
+ <app:linkSubscription page="/EditSubscription.do?action=Delete"><br />
<bean:message key="registration.deleteSubscription"/><br />
</app:linkSubscription><br />
- <app:linkSubscription page="/editSubscription.do?action=Edit"><br />
- <bean:message key="registration.editSubscription"/><br />
+ <app:linkSubscription page="/EditSubscription.do?action=Edit"><br />
+ <bean:message key="registration.EditSubscription"/><br />
</app:linkSubscription><br />
</td><br />
</tr><br />
@@ -710,7 +715,7 @@
<p>The Example application uses a subscription's host name (e.g. yahoo.com) as a primary key, which means you can only have one subscription for each host. It also means that to edit a subscription, all you need to know is the user and host. In fact, the editSubscription action is designed to create, edit, or delete a subscription if provided a user and host names in the request. The goal of LinkSubscriptionTag is then to output a block like:</p>
<blockquote>
- <p><code><A HREF=[path]editSubscription.do?action=[action]&username=[user]&host=[host]">[action]<br />
+ <p><code><A HREF=[path]EditSubscription.do?action=[action]&username=[user]&host=[host]">[action]<br />
</A></code></p>
</blockquote>
@@ -718,7 +723,7 @@
<blockquote>
<p><code><app:linkSubscription<br />
- page="/editSubscription.do?action=Delete">Delete<br />
+ page="/EditSubscription.do?action=Delete">Delete<br />
</app:linkSubscription></code></p>
</blockquote>
@@ -742,7 +747,7 @@
<p>Meanwhile, back on registration.jsp, there is one more link on the page. This uses yet another custom tag, the app:linkUser tag.</p>
<blockquote>
- <p><code><app:linkUser page="/editSubscription.do?action=Create"><br />
+ <p><code><app:linkUser page="/EditSubscription.do?action=Create"><br />
<bean:message key="registration.addSubscription"/><br />
</app:linkUser></code></p>
</blockquote>
@@ -754,7 +759,7 @@
<p>Since they solve the same general problem, LinkUserTag and LinkSubscriptionTag are quite a bit a like, except that LinkUserTag grabs the user bean from the session context, instead of a subscription bean from the iteration. Like the LinkSubscriptionTag, the name for the user bean (e.g. "user") is defaulted, and can be omitted from the tag; all that's needed is the page property -- the rest is automatic!</p>
<blockquote>
- <p><code><app:linkUser page="/editSubscription.do?action=Create"><br />
+ <p><code><app:linkUser page="/EditSubscription.do?action=Create"><br />
<bean:message key="registration.addSubscription"/><br />
</app:linkUser></code></p>
</blockquote>
@@ -762,7 +767,7 @@
<p>When rendered, this displays a HTML hypertext link like:</p>
<blockquote>
- <p><code><a href="/struts-example/editSubscription.do?action=Create&amp;username=user"><br />
+ <p><code><a href="/struts-example/EditSubscription.do?action=Create&amp;username=user"><br />
Add<br />
</a></code></p>
@@ -778,14 +783,14 @@
<blockquote>
<p><code><!-- Subscription form bean --><br />
<form-bean<br />
- name="subscriptionForm"<br />
+ name="SubscriptionForm"<br />
type="org.apache.struts.webapp.example.SubscriptionForm"<br />
/></code></p>
<p><code><!-- Edit mail subscription --><br />
<action path="/editSubscription"<br />
type="org.apache.struts.webapp.example.EditSubscriptionAction"<br />
- name="subscriptionForm"<br />
+ name="SubscriptionForm"<br />
scope="request"<br />
validate="false"<br />
><br />
@@ -796,7 +801,7 @@
<p><i>When we've introduced these type of mappings before, and mentioned that the struts-config.xml was parsed when the ActionServlet was initialized. But we should make it clear that when the Struts digester parsed this file, it actually created standard Java objects, linked as properties to the controller. This means you don't have to edit Java source files just to add a bunch of "new" statements. (How cool is that?)</i></p>
</blockquote>
- <p>Following what was specified by struts-config.xml, the controller makes sure that a subscriptionForm bean exists, along with the SubscriptionAction object, and then calls the action object's perform method. The perform method first checks to see that the user is logged-in. If not, control is forwarded to the login action. EditSubscriptionAction.perform then either creates a new subscription object (if the task is Create), or searches the user's subscription hashtable for a matching hostname (if the task is Edit).</p>
+ <p>Following what was specified by struts-config.xml, the controller makes sure that a SubscriptionForm bean exists, along with the SubscriptionAction object, and then calls the action object's perform method. The perform method first checks to see that the user is logged-in. If not, control is forwarded to the login action. EditSubscriptionAction.perform then either creates a new subscription object (if the task is Create), or searches the user's subscription hashtable for a matching hostname (if the task is Edit).</p>
<p>Finally, EditSubscriptionAction conforms the ActionForm bean with the database bean. There may be several subscriptions in the database, but in EditSubscriptionAction we expose the one selected (or just created) for this request to use. Once the Action form (called "subform" in the code) is created and populated from the database, the bean's action is set to either Create or Edit, and control is forwarded to our "success" form, subscription.jsp .</p>
@@ -861,7 +866,7 @@
<blockquote>
<p><code><logic:equal<br />
- name="subscriptionForm"<br />
+ name="SubscriptionForm"<br />
property="action"<br />
scope="request"<br />
value="Create"><br />
1.5 +6 -6 jakarta-struts/web/example/welcome.jsp
Index: welcome.jsp
===================================================================
RCS file: /home/cvs/jakarta-struts/web/example/welcome.jsp,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- welcome.jsp 10 Mar 2004 03:14:31 -0000 1.4
+++ welcome.jsp 12 Mar 2004 05:19:45 -0000 1.5
@@ -10,22 +10,22 @@
<h3><bean:message key="index.heading"/></h3>
<ul>
-<li><html:link action="/editRegistration?action=Create"><bean:message key="index.registration"/></html:link></li>
-<li><html:link action="/logon"><bean:message key="index.logon"/></html:link></li>
+<li><html:link action="/EditRegistration?action=Create"><bean:message key="index.registration"/></html:link></li>
+<li><html:link action="/Logon"><bean:message key="index.logon"/></html:link></li>
</ul>
<h3>Language Options</h3>
<ul>
-<li><html:link action="/locale?language=en">English</html:link></li>
-<li><html:link action="/locale?language=ja" useLocalEncoding="true">Japanese</html:link></li>
-<li><html:link action="/locale?language=ru" useLocalEncoding="true">Russian</html:link></li>
+<li><html:link action="/Locale?language=en">English</html:link></li>
+<li><html:link action="/Locale?language=ja" useLocalEncoding="true">Japanese</html:link></li>
+<li><html:link action="/Locale?language=ru" useLocalEncoding="true">Russian</html:link></li>
</ul>
<hr />
<p><html:img bundle="alternate" pageKey="struts.logo.path" altKey="struts.logo.alt"/></p>
-<p><html:link action="/tour"><bean:message key="index.tour"/></html:link></p>
+<p><html:link action="/Tour"><bean:message key="index.tour"/></html:link></p>
</body>
</html>
1.7 +5 -5 jakarta-struts/web/example/WEB-INF/struts-config-registration.xml
Index: struts-config-registration.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/web/example/WEB-INF/struts-config-registration.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- struts-config-registration.xml 9 Mar 2004 04:40:53 -0000 1.6
+++ struts-config-registration.xml 12 Mar 2004 05:19:46 -0000 1.7
@@ -50,7 +50,7 @@
<action-mappings>
<!-- Matches all edit actions (in this case, only user regstration) -->
- <action path="/edit*"
+ <action path="/Edit*"
type="org.apache.struts.webapp.example.Edit{1}Action"
name="{1}Form"
scope="request"
@@ -59,7 +59,7 @@
</action>
<!-- Matches all save actions (in this case, only user registration) -->
- <action path="/save*"
+ <action path="/Save*"
type="org.apache.struts.webapp.example.Save{1}Action"
name="{1}Form"
scope="request"
1.42 +27 -28 jakarta-struts/web/example/WEB-INF/struts-config.xml
Index: struts-config.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/web/example/WEB-INF/struts-config.xml,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- struts-config.xml 12 Mar 2004 02:44:34 -0000 1.41
+++ struts-config.xml 12 Mar 2004 05:19:46 -0000 1.42
@@ -35,25 +35,24 @@
<form-beans>
<!-- Logon form bean -->
- <form-bean name="logonForm"
+ <form-bean name="LogonForm"
type="org.apache.struts.validator.DynaValidatorForm">
<form-property name="username" type="java.lang.String"/>
<form-property name="password" type="java.lang.String"/>
</form-bean>
<!-- Subscription form bean -->
- <form-bean name="subscriptionForm"
+ <form-bean name="SubscriptionForm"
type="org.apache.struts.webapp.example.SubscriptionForm"/>
-
- </form-beans>
+ </form-beans>
<!-- ========== Global Forward Definitions ============================== -->
<global-forwards>
- <forward name="welcome" path="/welcome.do"/>
- <forward name="logoff" path="/logoff.do"/>
- <forward name="logon" path="/logon.do"/>
- <forward name="success" path="/mainMenu.do"/>
+ <forward name="welcome" path="/Welcome.do"/>
+ <forward name="logoff" path="/Logoff.do"/>
+ <forward name="logon" path="/Logon.do"/>
+ <forward name="success" path="/MainMenu.do"/>
</global-forwards>
@@ -61,7 +60,7 @@
<action-mappings>
<!-- Display welcome page -->
- <action path="/welcome"
+ <action path="/Welcome"
type="org.apache.struts.webapp.example.WelcomeAction">
<forward name="failure" path="/Error.jsp" />
<forward name="success" path="/welcome.jsp" />
@@ -69,26 +68,26 @@
<!-- Change locale action -->
<action
- path="/locale"
+ path="/Locale"
type="org.apache.struts.webapp.example.LocaleAction"
parameter="welcome" />
<!-- Display registration page -->
- <action path="/registration"
- forward="/Registration.jsp"/>
+ <action path="/Registration"
+ forward="/registration.jsp"/>
<!-- Display logon page -->
- <action path="/mainMenu"
+ <action path="/MainMenu"
forward="/mainMenu.jsp"/>
<!-- Display logon page -->
- <action path="/logon"
+ <action path="/Logon"
forward="/logon.jsp"/>
<!-- Process a user logon -->
- <action path="/submitLogon"
+ <action path="/SubmitLogon"
type="org.apache.struts.webapp.example.LogonAction"
- name="logonForm"
+ name="LogonForm"
scope="request"
input="logon">
<exception
@@ -98,29 +97,29 @@
</action>
<!-- Process a user logoff -->
- <action path="/logoff"
+ <action path="/Logoff"
type="org.apache.struts.webapp.example.LogoffAction">
- <forward name="success" path="/welcome.do"/>
+ <forward name="success" path="/Welcome.do"/>
</action>
<!-- Edit mail subscription -->
- <action path="/editSubscription"
+ <action path="/EditSubscription"
type="org.apache.struts.webapp.example.EditSubscriptionAction"
- name="subscriptionForm"
+ name="SubscriptionForm"
scope="request"
validate="false">
- <forward name="failure" path="/mainMenu.do"/>
+ <forward name="failure" path="/MainMenu.do"/>
<forward name="success" path="/subscription.jsp"/>
</action>
<!-- Save mail subscription -->
- <action path="/saveSubscription"
+ <action path="/SaveSubscription"
type="org.apache.struts.webapp.example.SaveSubscriptionAction"
- name="subscriptionForm"
+ name="SubscriptionForm"
scope="request"
input="subscription">
<forward name="subscription" path="/subscription.jsp"/>
- <forward name="success" path="/editRegistration.do?action=Edit"/>
+ <forward name="success" path="/EditRegistration.do?action=Edit"/>
</action>
<!-- Display the change password page when a password expires -->
@@ -129,7 +128,7 @@
</action>
<!-- Display the "walking tour" documentation -->
- <action path="/tour"
+ <action path="/Tour"
forward="/tour.html">
</action>
1.13 +2 -2 jakarta-struts/web/example/WEB-INF/validation.xml
Index: validation.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/web/example/WEB-INF/validation.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- validation.xml 12 Mar 2004 02:44:34 -0000 1.12
+++ validation.xml 12 Mar 2004 05:19:46 -0000 1.13
@@ -16,7 +16,7 @@
<!-- ========== Default Language Form Definitions ===================== -->
<formset>
- <form name="logonForm">
+ <form name="LogonForm">
<field property="username"
depends="required">
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org