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 2006/03/31 20:04:16 UTC
svn commit: r390469 - in /struts/sandbox/trunk/action2/apps/mailreader/src:
java/mailreader2/Logon.java java/mailreader2/MailreaderSupport.java
webapp/pages/tour.html
Author: husted
Date: Fri Mar 31 10:04:15 2006
New Revision: 390469
URL: http://svn.apache.org/viewcvs?rev=390469&view=rev
Log:
Action2 Apps
* Mailreader Tour
** Up to "xwork.xml"
Modified:
struts/sandbox/trunk/action2/apps/mailreader/src/java/mailreader2/Logon.java
struts/sandbox/trunk/action2/apps/mailreader/src/java/mailreader2/MailreaderSupport.java
struts/sandbox/trunk/action2/apps/mailreader/src/webapp/pages/tour.html
Modified: struts/sandbox/trunk/action2/apps/mailreader/src/java/mailreader2/Logon.java
URL: http://svn.apache.org/viewcvs/struts/sandbox/trunk/action2/apps/mailreader/src/java/mailreader2/Logon.java?rev=390469&r1=390468&r2=390469&view=diff
==============================================================================
--- struts/sandbox/trunk/action2/apps/mailreader/src/java/mailreader2/Logon.java (original)
+++ struts/sandbox/trunk/action2/apps/mailreader/src/java/mailreader2/Logon.java Fri Mar 31 10:04:15 2006
@@ -19,13 +19,14 @@
package mailreader2;
import org.apache.struts.apps.mailreader.dao.User;
+import org.apache.struts.apps.mailreader.dao.ExpiredPasswordException;
/**
* <p> Validate a user logon. </p>
*/
public final class Logon extends MailreaderSupport {
- public String execute() throws Exception {
+ public String execute() throws ExpiredPasswordException {
User user = findUser(getUsername(), getPassword());
Modified: struts/sandbox/trunk/action2/apps/mailreader/src/java/mailreader2/MailreaderSupport.java
URL: http://svn.apache.org/viewcvs/struts/sandbox/trunk/action2/apps/mailreader/src/java/mailreader2/MailreaderSupport.java?rev=390469&r1=390468&r2=390469&view=diff
==============================================================================
--- struts/sandbox/trunk/action2/apps/mailreader/src/java/mailreader2/MailreaderSupport.java (original)
+++ struts/sandbox/trunk/action2/apps/mailreader/src/java/mailreader2/MailreaderSupport.java Fri Mar 31 10:04:15 2006
@@ -75,17 +75,17 @@
/**
* <p>Store a new application context.</p>
*
- * @param application
+ * @param value A Map representing application state
*/
- public void setApplication(Map application) {
- this.application = application;
+ public void setApplication(Map value) {
+ application = value;
}
/**
* <p>Provide application context.</p>
*/
public Map getApplication() {
- return this.application;
+ return application;
}
// ---- SessionAware ----
@@ -98,10 +98,10 @@
/**
* <p>Store a new session context.</p>
*
- * @param session
+ * @param value A Map representing session state
*/
- public void setSession(Map session) {
- this.session = session;
+ public void setSession(Map value) {
+ session = value;
}
/**
@@ -131,7 +131,7 @@
* @return Returns the task.
*/
public String getTask() {
- return this.task;
+ return task;
}
/**
@@ -140,7 +140,7 @@
* @param task The task to set.
*/
public void setTask(String task) {
- this.task = task;
+ task = task;
}
// ---- Host property ----
@@ -189,16 +189,16 @@
* @return Returns the password.
*/
public String getPassword() {
- return this.password;
+ return password;
}
/**
* <p>Store new User Password</p>
*
- * @param password The password to set.
+ * @param value The password to set.
*/
- public void setPassword(String password) {
- this.password = password;
+ public void setPassword(String value) {
+ password = value;
}
// ---- Password2 property (confirmation) ----
@@ -219,16 +219,16 @@
* @return Returns the confirmationpassword.
*/
public String getPassword2() {
- return this.password2;
+ return password2;
}
/**
* <p>Store a new User password confirmation.</p>
*
- * @param password2 The confirmation password to set.
+ * @param value The confirmation password to set.
*/
- public void setPassword2(String password2) {
- this.password2 = password2;
+ public void setPassword2(String value) {
+ password2 = value;
}
// ---- Username property ----
@@ -248,16 +248,16 @@
* @return Returns the User username.
*/
public String getUsername() {
- return this.username;
+ return username;
}
/**
* <p>Store new User username</p>
*
- * @param username The username to set.
+ * @param value The username to set.
*/
- public void setUsername(String username) {
- this.username = username;
+ public void setUsername(String value) {
+ username = value;
}
// ---- Database property ----
Modified: struts/sandbox/trunk/action2/apps/mailreader/src/webapp/pages/tour.html
URL: http://svn.apache.org/viewcvs/struts/sandbox/trunk/action2/apps/mailreader/src/webapp/pages/tour.html?rev=390469&r1=390468&r2=390469&view=diff
==============================================================================
--- struts/sandbox/trunk/action2/apps/mailreader/src/webapp/pages/tour.html (original)
+++ struts/sandbox/trunk/action2/apps/mailreader/src/webapp/pages/tour.html Fri Mar 31 10:04:15 2006
@@ -179,49 +179,49 @@
When a web application loads,
the container reads and parses the "Web Application Deployment
Descriptor", or "web.xml" file.
- Action 2 plugs into a web application via a servlet filter.
+ The framework plugs into a web application via a servlet filter.
Like any filter, the Action servlet is deployed via the web.xml.
</p>
<hr/>
<h5>web.xml - The Web Application Deployment Descriptor</h5>
<pre><code><?xml version="1.0" encoding="ISO-8859-1"?>
- <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
- "http://java.sun.com/dtd/web-app_2_3.dtd">
- <web-app>
-
- <display-name>Action2 Mailreader</display-name>
-
- <strong> <filter>
- <filter-name>Action2</filter-name>
- <filter-class>
- com.opensymphony.webwork.dispatcher.FilterDispatcher
- </filter-class>
- </filter></strong>
+<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
+ "http://java.sun.com/dtd/web-app_2_3.dtd">
+<web-app>
+
+ <display-name>Action2 Mailreader</display-name>
+
+ <strong><filter>
+ <filter-name>Action2</filter-name>
+ <filter-class>
+ com.opensymphony.webwork.dispatcher.FilterDispatcher
+ </filter-class>
+ </filter></strong>
- <filter-mapping>
+ <filter-mapping>
<filter-name><strong>Action2</strong></filter-name>
<url-pattern>/*</url-pattern>
- </filter-mapping>
+ </filter-mapping>
- <listener>
- <listener-class>
+ <listener>
+ <listener-class>
org.springframework.web.context.ContextLoaderListener
- </listener-class>
- </listener>
+ </listener-class>
+ </listener>
- <!-- Application Listener for MailReader database -->
- <listener>
- <listener-class>
+ <!-- Application Listener for MailReader database -->
+ <listener>
+ <listener-class>
mailreader2.ApplicationListener
- </listener-class>
- </listener>
+ </listener-class>
+ </listener>
- <welcome-file-list>
+ <welcome-file-list>
<welcome-file>index.html</welcome-file>
- </welcome-file-list>
+ </welcome-file-list>
- </web-app></code></pre>
+</web-app></code></pre>
<hr/>
<p>
@@ -264,7 +264,7 @@
Unless you are using Java 1.5, actions cannot be specified as a Welcome
page.
So, in the case of a Welcome page,
- how do we follow the Action 2 best practice of navigating through actions
+ how do we follow the best practice of navigating through actions
rather than pages?
</p>
@@ -304,9 +304,9 @@
</p>
<hr/>
<h5>A simple "forward thru" action element</h5>
-<pre><code> <action name="<strong>>Welcome</strong>">
- <result><strong>/pages/Welcome.jsp</strong></result>
- </action></code></pre>
+<pre><code><action name="<strong>>Welcome</strong>">
+ <result><strong>/pages/Welcome.jsp</strong></result>
+</action></code></pre>
<hr/>
<p>
@@ -324,10 +324,10 @@
<hr/>
<h5>The Welcome action element</h5>
-<pre><code> <action name="Welcome" <b>class="mailreader2.Welcome"</b>>
- <b><interceptor-ref name="defaultStack"/></b>
- <result>/pages/Welcome.jsp</result>
- </action></code></pre>
+<pre><code><action name="Welcome" <b>class="mailreader2.Welcome"</b>>
+ <strong><interceptor-ref name="defaultStack"/></strong>
+ <result>/pages/Welcome.jsp</result>
+</action></code></pre>
<hr/>
<p>
@@ -342,8 +342,8 @@
<h5>Key concept:</h5>
<blockquote>
<p>
- The essential point is that the Action class doesn't need to know
- what result type is needed for "success" or "error".
+ The Action class doesn't need to know what result type is needed
+ for "success" or "error".
The Action can just return the logical name for a result,
without knowing how the result is implemented.
</p>
@@ -521,7 +521,7 @@
<hr/>
<p>
- When we specify "resources" here, we are telling Action 2 to scan the classpath
+ When we specify "resources" here, we are telling the framework to scan the classpath
for a Resource Bundle named "resources.properties".
The bundle might be embedded in a JAR, or found in the WEB-INF/classes
folder, or anywhere else on the runtime classpath.
@@ -612,7 +612,7 @@
<p>
The <strong>text</strong> tag inserts a message from and
application's default resource bundle.
- If the Action 2 locale setting is changed for a user,
+ If the framework's locale setting is changed for a user,
the text tag will render messages from the new locale's resource
bundle instead.
</p>
@@ -654,7 +654,7 @@
</p>
<p>
- In the span of a single request for the Welcome page, Action 2 has done
+ In the span of a single request for the Welcome page, the framework has done
quite a bit already:
</p>
@@ -832,7 +832,7 @@
<hr/>
<p>
- Under the covers, Struts Action 2 uses
+ Under the covers, the framework uses
<a href="http://freemarker.sourceforge.net/">Freemarker</a>
for its standard templating language.
FreeMarker is similar to
@@ -890,7 +890,7 @@
</p>
<p>
- For the answers, we need to look at another flavor of Action 2 configuration file:
+ For the answers, we need to look at another flavor of configuration file:
the "validation" file.
</p>
@@ -911,14 +911,14 @@
<h5>Validation file for Logon Action</h5>
<pre><code><!DOCTYPE validators PUBLIC "-//OpenSymphony Group//XWork Validator 1.0.2//EN" "http://www.opensymphony.com/xwork/xwork-validator-1.0.2.dtd">
<validators>
- <field name="username">
- <field-validator type="requiredstring">
- <message key="error.username.required"/>
+ <field name="<strong>username</strong>">
+ <field-validator type="<strong>requiredstring</strong>">
+ <message key="<strong>error.username.required</strong>"/>
</field-validator>
</field>
- <field name="password">
- <field-validator type="requiredstring">
- <message key="error.password.required"/>
+ <field name="<strong>password</strong>">
+ <field-validator type="<strong>requiredstring</strong>">
+ <message key="<strong>error.password.required</strong>"/>
</field-validator>
</field>
</validators>
@@ -964,20 +964,20 @@
public final class <strong>Logon</strong> extends MailreaderSupport {
- public String <strong>execute()</strong> throws Exception {
-
- User user = findUser(getUsername(), getPassword());
+ public String <strong>execute()</strong> throws ExpiredPasswordException {
- if (user != null) {
- setUser(user);
- }
+ User user = <strong>findUser(getUsername(), getPassword());</strong>
- if (hasErrors()) {
- return INPUT;
- }
+ if (user != null) {
+ <strong>setUser(user);</strong>
+ }
- return SUCCESS;
+ if (<strong>hasErrors()</strong>) {
+ return INPUT;
}
+
+ return SUCCESS;
+}
}</code></pre>
<hr/>
@@ -991,18 +991,18 @@
<p>
Let's look at the relevant properties and methods from the MailreaderSupport and ActionSupport classes:
- "getUsername", "getPassword", "findUser" and "hasErrors".
+ "getUsername", "getPassword", "findUser", "setUser", and "hasErrors".
</p>
<p>
- Struts Action 2 lets you define
+ The framework lets you define
<a href="http://struts.apache.org/struts-action/userGuide/preface.html#javabeans">JavaBean properties</a>
directly on the Action.
Any JavaBean property can be used, including rich objects.
When a request comes in,
any public properties on the Action class are matched with the request parameters.
When the names match, the request parameter value is set to the JavaBean property.
- Struts Action 2 will make its best effort to convert the data,
+ The framework will make its best effort to convert the data,
and, if necessary, reporting any conversion errors.
</p>
@@ -1038,261 +1038,187 @@
<hr/>
<h5>MailreaderSupport.findUser</h5>
<pre><code>public User <strong>findUser</strong>(String username, String password)
- throws ExpiredPasswordException {
+ throws ExpiredPasswordException {
- User user = getDatabase().findUser(username);
- if ((user != null) && !user.getPassword().equals(password)) {
- user = null;
- }
- if (user == null) {
- this.addFieldError("password", getText("error.password.mismatch"));
- }
- return user;}</code></pre>
+ User user = <strong>getDatabase().findUser(username)</strong>;
+ if ((user != null) && !user.getPassword().equals(password)) {
+ user = null;
+ }
+ if (user == null) {
+ this.<strong>addFieldError</strong>("password", getText("error.password.mismatch"));
+ }
+ return user;
+}</code></pre>
<hr/>
<p>
-
+ The findUser method dips into the MailReader Data Access Object layer,
+ which is represented by the <strong>Database</strong> property.
+ The code for the DAO layer is maintained as a seperate project.
+ The MailReader application imports the DAO JAR,
+ but it is not responsible for maintaining any of the DAO source.
+ Keeping the data access layer at "arms-length" is a very good habit.
+ It encourages a style of development where the data access layer
+ can be tested and developed independantly of a specific end-user application.
+ In fact, there are three versions of the MailReader application,
+ all which share the same MailReader DAO JAR!
</p>
<hr/>
-<h5>BaseAction.doGet and doSet</h5>
-<pre><code> protected String <strong>doGet</strong>(ActionForm form, String
- property) {
- String initial;
- try {
- initial = (String) PropertyUtils.getSimpleProperty(form, property);
- } catch (Throwable t) {
- initial = null;
- }
- String value = null;
- if ((initial !=null) && (initial.length()>0)) {
- value = initial.trim();
- if (value.length()==0) value = null;
- }
- return value;
- }
-
- protected boolean <strong>doSet</strong>(ActionForm form, String property,
- String value) {
- try {
- DynaActionForm dyna = (DynaActionForm) form;
- dyna.set(property,value);
- } catch (Throwable t) {
- return false;
- }
- return true;
- }</code></pre>
+<h5>Best Practice:</h5>
+<blockquote>
+ <p><font class="hint">"Strongly separate data access and business logic from the rest of the application."</font>
+ </p>
+</blockquote>
<hr/>
<p>
- LogonAction uses two other BaseAction helpers: "doGetUser" and
- "doFindSuccess".
+ When findUser returns, the Logon Action looks to see if a valid (non-null) User object is returned.
+ A valid User is passed to the <strong>User</strong> property.
+ The User property is not implemented in quite the same way as Username and Password.
</p>
<hr/>
-<h5>BaseAction.doGetUser</h5>
-<pre><code> User <strong>doGetUser</strong>(UserDatabase database, String
- username,
- String password, ActionMessages errors)
- throws ExpiredPasswordException {
-
- User user = null;
- if (database == null){
- errors.add(
- ActionMessages.GLOBAL_MESSAGE,
- new ActionMessage("error.database.missing"));
- }
- else {
- user = <strong>database.</strong>findUser(username);
- if ((user != null) && !user.getPassword().equals(password)) {
- user = null;
- }
- if (user == null) {
- errors.add(
- ActionMessages.GLOBAL_MESSAGE,
- new ActionMessage("error.password.mismatch"));
- }
- }
-
- return user;
- }
-</code></pre>
+<h5>MailreaderSupport.setUser</h5>
+<pre><code>public User getUser() {
+ return (User) <strong>getSession().get(Constants.USER_KEY)</strong>;
+}
+public void setUser(User user) {
+ getSession().put(Constants.USER_KEY, user);
+}</code></pre>
<hr/>
<p>
- The <strong>doGetUser</strong> helper does the real work of the
- LogonAction.
- The "doGetUser" method checks the tendered credentials against the
- database,
- If there are any issues, like there is not a user by that name, or the
- password doesn't match, doGetUser passes back the appropriate messages.
+ Instead of using a field to store the property value,
+ setUser passes it to a <strong>Session</strong> property.
</p>
+<h5>MailreaderSupport.getSession() and setSession()r</h5>
+<pre><code>private Map session;
+
+public Map <strong>getSession()</strong> {
+ return session;
+}
+
+public void <strong>setSession(Map value)</strong> {
+ session = value;
+}</code></pre>
+
<p>
- The doGet user is another "facade" method.
- A facade simplifies a complicated call to a business method.
- Here, doGetUser wrapes the business method with the Error Handling needed
- by the Mail Reader application.
+ To look at the MailreaderSupport class, the Session property looks like a plain-old Map.
+ In fact, the Session property is an adapter that is backed by the servlet session object at runtime.
+ The MailreaderSupport class doesn't need to know that though.
+ It can treat Session like any other Map.
+ We can also test the MailreaderSupport class by passing it some other implementation of Map,
+ running the test,
+ and then looking to see what changes MailreaderSupport made to our "mock" Session object.
</p>
-<hr/>
-<h5>BaseAction.doFindSuccess</h5>
-<pre><code> protected ActionForward <strong>doFindSuccess</strong>
- (ActionMapping mapping) {
- if (log.isTraceEnabled()) {
- log.trace(Constants.LOG_SUCCESS);
- }
- return mapping.findForward(Constants.SUCCESS);
-</code></pre>
-<hr/>
+<p>
+ But, when MailreaderSupport is running inside a web application,
+ how does it acquire a reference to the servlet session?
+</p>
<p>
- The <strong>doFindSuccess</strong> method is a simple utility but often
- used.
- It just checks the mapping for a result named "Success".
- By using a utility,
- we can include a logging statement when trace is enabled,
- and be very sure that everyone knows how to spell "Success". :)
+ Good question. If you were to look at just the MailreaderSupport class,
+ you would not see a single line of code that sets the session property.
+ But, yet, when we run the class, the session property is not null.
+ Hmmm.
</p>
-<h5>web.xml -- Action Servlet Configuration</h5>
-<pre><code>
- <servlet>
- <servlet-name>action</servlet-name>
- <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
- <init-param>
- <param-name>config</param-name>
- <param-value><strong>/WEB-INF/struts-config.xml</strong></param-value>
- </init-param>
- <load-on-startup>1</load-on-startup>
- </servlet>
-</code></pre>
+<p>
+ The magic that provides the Session property a runtime value is called "dependency injection".
+ The MailreaderSupport class implements a interface called <strong>SessionAware</strong>.
+ SessionAware is bundled with the framework, and it defines a setter for the Session property.
+</p>
-<hr/>
-<h5>The SubmitLogon action element</h5>
-<pre><code> <!-- Process a user logon -->
- <action
- <strong>path="/SubmitLogon"</strong>
- type="org.apache.struts.apps.mailreader.actions.LogonAction"
- <strong>name</strong>="LogonForm"
- <strong>scope</strong>="request"
- <strong>validate</strong>="request"
- <strong>input</strong>="Logon">
- <<strong>exception</strong>
- key="expired.password"
- type="org.apache.struts.apps.mailreader.dao.ExpiredPasswordException"
- path="/ChangePassword.jsp"/>
- <forward
- name="Success"
- path="/MainMenu.do"/>
- </action></code></pre>
-<hr/>
+<p>
+ <code>public void <strong>setSession</strong>(Map session);</code>
+</p>
<p>
- We saw the path and type attributes in the Welcome action.
- Let's look at the new attributes: "name", "scope", "input", and
- "exception".
+ Also bundled with the framework is an object called the <strong>ServletConfigInterceptor</strong>.
+ If the ServletConfigInterceptor sees that an Action implements the SessionAware interface,
+ it automatically set the session property.
</p>
-<h4>The "name" attribute</h4>
+<pre><code> if (action instanceof <code>SessionAware</code>) {
+ ((SessionAware) action).<code>setSession</code>(context.getSession());
+}</code></pre>
<p>
- The <strong>name</strong> attribute specifies something Struts Action
- calls an "ActionForm".
- The ActionForm buffers input from a form and delivers it to an Action
- class as an object.
- The ActionForm can also be used to validate input.
- If validation fails, the tags can rewrite the input values from the
- ActionForm.
+ The framework uses these "Interceptor" classes to create a "front controller"
+ for each action an application defines.
+ Each Interceptor can peek at the request before an Action class is invoked,
+ and then again after the Action class is invoked.
+ (If you have worked with Servlet
+ <a href="http://java.sun.com/products/servlet/Filters.html">Filters</a>,
+ you will recognize this pattern.
+ But, unlike Filters, Interceptors are not tied to HTTP.
+ Interceptors can be tested and developed outside of a web application.)
</p>
<p>
- The ActionForms are defined in the "form-beans" section of struts-config.
+ You can use the same set of Interceptors for all your actions,
+ or define a special set of Interceptors for any given action,
+ or define different sets of Interceptors to use with different types of actions.
+ The framework comes with a default set of Interceptors,
+ that it will use when another set is not specified,
+ but you can designate your own default Interceptor set (or "stack")
+ in the xwork.xml configuration file.
</p>
<p>
- ActionForms can be "conventional" or "dynamic".
- MailReader uses dynamic ActionForms.
- Rather than cobble up an actual JavaBean class,
- we specify the properties the ActionForm can accept in the configuration
- file.
+ Most Interceptors provide a "utility" function, like setting the session property.
+ Others, like the ValidationInterceptor, can change the workflow of an action.
+ Interceptors are key feature of the framework,
+ and we will see a few more on the tour.
</p>
-<hr/>
-<h5>The form-bean element for LogonForm</h5>
-<pre><code> <!-- LogonAction form bean -->
- <form-bean
- name="LogonForm"
- <strong>extends="BaseForm"/></strong></code></pre>
-<hr/>
+<p>
+ If a valid User is not found, or the password doesn't match,
+ the findUser method invokes the <strong>addFieldError</strong> method to note the problem.
+ When findUser returns, the Logon Action checks for errors,
+ and then returns either INPUT or SUCCESS.
+</p>
<p>
- Hmmmm. That doesn't seem to tell us much.
- The LogonForm "extends" the BaseForm, but doesn't add any attributes.
- What about the BaseForm element that LogonForm extends?
+ The addFieldError method is provided by the ActionSupport class,
+ which is bundled with the framework.
+ The constants for INPUT and SUCCESS are also provided by ActionSupport.
+ While the ActionSupport class provides many useful utilities,
+ you are not required to use it as a base class.
+ Any Java class can be used as an Action, if you like.
</p>
-<hr/>
-<h5>BaseForm - An "abstract" form-bean</h5>
-<pre><code> <!-- BaseAction form bean (abstract) -->
- <form-bean
- name="BaseForm"
- type="org.apache.struts.validator.DynaValidatorForm">
- <strong><form-property</strong>
- name="username"
- type="java.lang.String"/>
- <form-property
- name="password"
- type="java.lang.String"/>
- <form-property
- name="task"
- type="java.lang.String"
- initial="Create"/>
- </form-bean></code></pre>
-<hr/>
+<p>
+ But, it is a good practice to provide a base class with utilites
+ that can be shared by an application's Action classes.
+ The framework does this with ActionSupport,
+ and the MailReader application does the same with the MailreaderSupport class.
+</p>
-<h5>Note:</h5>
+<hr/>
+<h5>Best Practice:</h5>
<blockquote>
- <p><font class="hint">
- <strong>Extends</strong> - In the Struts configuration file,
- we can use the "extends" attribute to adopt default settings from
- another element.
- Extends makes using XML elements more like object-orientated
- programming.
- You can setup a base element, and then only specify the behavior that
- changes.
- </font></p>
+ <p><font class="hint">"Use a base class to define common functionality."</font></p>
</blockquote>
<hr/>
<p>
- Struts creates the ActionForms automatically, regardless of whether the
- form-bean is conventional or dynamic.
- The ActionForm lets us specify which properties we want to extract from
- the incoming request.
- If a property is not specified by the ActionForm,
- the value is not automatically transferred from the request, validated,
- or passed to the Action class.
+ But, what happens if Logon returns INPUT instead of SUCCESS. How does the framework know what to do next?
</p>
-<h4>The "scope" attribute</h4>
-
<p>
- The <strong>scope</strong> attribute in the "SubmitLogon" action element
- tells the controller whether to store the ActionForm in the request,
- rather than in the user's session.
+ To answer that question, we need to turn back to the xwork.xml configuration file.
</p>
-<hr/>
-<h5>Best Practice:</h5>
-<blockquote>
- <p><font class="hint">
- Use request scope for single-page forms that contain all the
- properties needed by the Action.
- There is usually no need to maintain form input across requests.
- </font></p>
-</blockquote>
-<hr/>
+
+<h4><a name="xwork.xml" id="xwork.xml">xwork.xml</a></h4>
+
+
+... TODO ...
+
<h4>The "validate" attribute</h4>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org