martinc 02/03/19 19:07:13
Modified: doc index.xml news_2002.xml project.xml
doc/proposals release-plan-1.1b1.xml
Added: doc/userGuide release-notes-1.1-b1.xml
Log:
Documentation updates for Struts 1.1 Beta 1. Also some miscellaneous fixes
to broken links, etc.
Revision Changes Path
1.22 +41 -6 jakarta-struts/doc/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/index.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- index.xml 5 Mar 2002 02:26:54 -0000 1.21
+++ index.xml 20 Mar 2002 03:07:13 -0000 1.22
@@ -175,22 +175,57 @@
<p>
Check the
- <a href="http://jakarta.apache.org/doc-1.0.2/release-notes-1.0.2.html";>
- </a> for a summary of the changes since the Struts 1.0.1 release.
+ <a href="http://jakarta.apache.org/struts/doc-1.0.2/release-notes-1.0.2.html";>
+ Release Notes</a> for a summary of the changes since the Struts 1.0.1 release.
</p>
<p>
<b>In addition to a Struts distribution,</b> you will need to ensure that
you have downloaded and installed all of the
- <a href="http://jakarta.apache.org/doc-1.0.2/installation.html#Prerequisites";>
+ <a
href="http://jakarta.apache.org/struts/doc-1.0.2/installation.html#Prerequisites";>
prerequisite</a> software applications. Then, follow the appropriate instructions
to
- <a href="http://jakarta.apache.org/doc-1.0.2/installation.html#Installing";>
+ <a href="http://jakarta.apache.org/struts/doc-1.0.2/installation.html#Installing";>
install and use a Struts binary
distribution</a> in your web application or for
- <a href="http://jakarta.apache.org/doc-1.0.2/installation.html#Building";>
+ <a href="http://jakarta.apache.org/struts/doc-1.0.2/installation.html#Building";>
building Struts from the source distribution</a>.
</p>
+ <p>
+ The latest <i>beta release</i> of <strong>Struts 1.1</strong> is also
+ available, in the same three distributions. While not necessarily quite as
+ stable as the latest production release, the beta release provides an interim
+ release between the nightly builds and the production release so that
+ developers can start taking advantage of new functionality without the same
+ degree of risk as using the nightly builds may entail.
+ </p>
+
+ <ul>
+ <li><a href="http://jakarta.apache.org/builds/jakarta-struts/release/v1.1-b1";>
+ <b>Struts 1.1 Beta 1 Binary Distribution</b></a></li>
+ <li><a href="http://jakarta.apache.org/builds/jakarta-struts/release/v1.1-b1/lib";>
+ <b>Struts 1.1 Beta 1 Library Distribution</b></a></li>
+ <li><a href="http://jakarta.apache.org/builds/jakarta-struts/release/v1.1-b1/src";>
+ <b>Struts 1.1 Beta 1 Source Code Distribution</b></a></li>
+ </ul>
+
+ <p>
+ Check the
+ <a href="http://jakarta.apache.org/struts/userGuide/release-notes-1.1-b1.html";>
+ Release Notes</a> for a summary of the changes since the Struts 1.0.2 release.
+ </p>
+
+ <p>
+ As with the production release, you will need to ensure that you have
+ downloaded and installed all of the
+ <a
href="http://jakarta.apache.org/struts/userGuide/installation.html#Prerequisites";>
+ prerequisite</a> software applications. Then, follow the appropriate instructions
to
+ <a href="http://jakarta.apache.org/struts/userGuide/installation.html#Installing";>
+ install and use a Struts binary
+ distribution</a> in your web application or for
+ <a href="http://jakarta.apache.org/struts/userGuide/installation.html#Building";>
+ building Struts from the source distribution</a>.
+ </p>
</section>
<section name="Nightly Builds" href="Builds">
@@ -215,7 +250,7 @@
<p>
Be sure to check the
- <a href="http://jakarta.apache.org/release-notes.html";>
+ <a href="http://jakarta.apache.org/struts/userGuide/release-notes.html";>
Release Notes</a> for the nightly builds so you know what you are getting!
</p>
1.5 +25 -1 jakarta-struts/doc/news_2002.xml
Index: news_2002.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/news_2002.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- news_2002.xml 5 Mar 2002 02:26:54 -0000 1.4
+++ news_2002.xml 20 Mar 2002 03:07:13 -0000 1.5
@@ -14,6 +14,30 @@
<section name="News & Status">
+<h3><a name="20020319"></a>19 March 2002 - Struts 1.1 Beta 1 Released</h3>
+<p>
+The Struts team announces the release of Struts 1.1 Beta 1. This release
+includes substantial new functionality, while retaining full backwards
+compatibility with earlier versions of Struts. It also incorporates fixes
+for a number of bugs which were reported against earlier versions.
+</p>
+<p>
+The binary distribution for this release is available
+<a href="http://jakarta.apache.org/builds/jakarta-struts/release/v1.1-b1/";>
+<b>here</b></a>
+and the source distribution
+is available
+<a href="http://jakarta.apache.org/builds/jakarta-struts/release/v1.1-b1/src/";>
+<b>here</b></a>.
+In addition, a library distribution, which consists of a minimal
+binary distribution, without sample web applications or additional code, is
+available
+<a href="http://www.apache.org/dist/jakarta/jakarta-struts/release/v1.1-b1/lib/";>
+<b>here</b></a>.
+</p>
+<hr size="1" noshade=""/>
+
+
<h3><a name="20020304"></a>04 March 2002 - Best Practice with Expresso-Struts
Framework</h3>
<p>
In this article, Peter Pilgrim looks at the best practice of using a popular web
@@ -231,7 +255,7 @@
In addition, a library distribution, which consists of a minimal
binary distribution, without sample web applications or additional code, is
available
-<a href="http://www.apache.org/dist/jakarta/jakarta-struts/release/v1.0.2/src/";>
+<a href="http://www.apache.org/dist/jakarta/jakarta-struts/release/v1.0.2/lib/";>
<b>here</b></a>.
</p>
<hr size="1" noshade=""/>
1.21 +7 -2 jakarta-struts/doc/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/project.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- project.xml 10 Mar 2002 06:22:40 -0000 1.20
+++ project.xml 20 Mar 2002 03:07:13 -0000 1.21
@@ -31,6 +31,13 @@
href="http://jakarta.apache.org/struts/doc-1.0.2/installation.html"/>
</menu>
+ <menu name="Beta Release (1.1-b1)">
+ <item name="Release Notes"
+ href="userGuide/release-notes-1.1-b1.html"/>
+ <item name="Release Plan"
+ href="proposals/release-plan-1.1b1.html"/>
+ </menu>
+
<menu name="Nightly Build">
<item name="User Guide"
href="userGuide/index.html"/>
@@ -44,8 +51,6 @@
href="proposals/workflow.html"/>
<item name="Wish List"
href="proposals/todo-1.1.html"/>
- <item name="Struts 1.1 Beta 1 Release Plan"
- href="proposals/release-plan-1.1b1.html"/>
</menu>
</project>
1.2 +15 -10 jakarta-struts/doc/proposals/release-plan-1.1b1.xml
Index: release-plan-1.1b1.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/proposals/release-plan-1.1b1.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- release-plan-1.1b1.xml 10 Mar 2002 06:22:40 -0000 1.1
+++ release-plan-1.1b1.xml 20 Mar 2002 03:07:13 -0000 1.2
@@ -11,7 +11,7 @@
<section name="Objective" href="Objective">
- <p><font size="-2">$Id: release-plan-1.1b1.xml,v 1.1 2002/03/10 06:22:40 martinc
Exp $</font></p>
+ <p><font size="-2">$Id: release-plan-1.1b1.xml,v 1.2 2002/03/20 03:07:13 martinc
Exp $</font></p>
<p>The objective of the <strong>Struts 1.1 Beta 1</strong> release is to
create a milestone release against which a final series of bug fixes and
@@ -34,7 +34,7 @@
<p>Therefore, the following release plan is proposed for Struts 1.1 Beta 1:
</p>
<ul>
- <li><em>Code Freeze / Tag Date</em> - Tuesday, March 12, 2002</li>
+ <li><em>Code Freeze / Tag Date</em> - Monday, March 18, 2002</li>
<li><em>Release Manager</em> - Martin Cooper</li>
<li><em>Release Announcement</em> - To the following mailing lists:
<ul>
@@ -52,14 +52,6 @@
<p>Prior to the release of Struts 1.1 Beta 1, the following action items
must be completed:</p>
<ul>
- <li>All <a href="http://nagoya.apache.org/bugzilla/";>Bugzilla</a> bug reports
- against Struts 1.1 nightly builds MUST be marked as "Resolved", with any
- of the legal Bugzilla resolutions (FIXED, INVALID, WONTFIX, LATER,
- REMIND, WORKSFORME).</li>
- <li>Bug reports that are resolved as LATER or REMIND will include comments
- as to whether those specific issues will be dealt with in a subsequent
- 1.1 beta, release candidate, or final release, or whether they will be
- scheduled for consideration in a subsequent release time frame.</li>
<li>The Struts 1.1 Release Notes document shall be updated to describe
substantial changes and improvements since the Struts 1.0.2 release,
along with associated updates to the main Struts Documentation
@@ -73,6 +65,19 @@
<li>A release vote shall take place on the STRUTS-DEV mailing list to
approve this plan. The release vote MUST pass by "Majority Approval"
of Struts committers.</li>
+ </ul>
+
+ <p>Prior to the release of a subsequent Struts 1.1 release candidate, the
+ following action items must be completed:</p>
+ <ul>
+ <li>All <a href="http://nagoya.apache.org/bugzilla/";>Bugzilla</a> bug reports
+ against Struts 1.1 nightly builds MUST be marked as "Resolved", with any
+ of the legal Bugzilla resolutions (FIXED, INVALID, WONTFIX, LATER,
+ REMIND, WORKSFORME).</li>
+ <li>Bug reports that are resolved as LATER or REMIND will include comments
+ as to whether those specific issues will be dealt with in a subsequent
+ release candidate, or final release, or whether they will be scheduled
+ for consideration in a subsequent release time frame.</li>
</ul>
</section>
1.1 jakarta-struts/doc/userGuide/release-notes-1.1-b1.xml
Index: release-notes-1.1-b1.xml
===================================================================
<?xml version="1.0"?>
<document url="./release-notes-1.1-b1.xml">
<properties>
<author>Craig R. McClanahan</author>
<author>Robert Leland</author>
<author>Ted Husted</author>
<title>Struts Release Notes (Version 1.1 Beta 1)</title>
</properties>
<body>
<section name="Introduction" href="Introduction">
<p>This document contains the release notes for
<strong>Version 1.1 Beta 1</strong> of the Struts Framework,
and covers changes that have taken place since
<a href="release-notes-1.0.2.html">Version 1.0.2</a>
was released. The following sections cover
<a href="#New">New Features</a> and <a href="#Changes">Changes</a>
to Struts.</p>
</section>
<section name="What's Included?" href="Included">
<p>The binary distribution of this release includes the following
files relevant to Struts:</p>
<ul>
<li><code>INSTALL</code> - Brief installation instructions. See
the <code>Struts Documentation Application</code>, or online at
<a
href="http://jakarta.apache.org/struts/";>http://jakarta.apache.org/struts/</a>
for more information.</li>
<li><code>LICENSE</code> - The Apache Software Foundation license that
defines the terms under which you can use Struts (and other software
licensed by Apache).</li>
<li><code>README</code> - A brief introduction to Struts.</li>
<li><code>lib/</code> - Directory containing files you will need in
your own applications. The individual files of interest are:
<ul>
<li><code>commons-*.jar</code> - Release packages from the
<a href="http://jakarta.apache.org/commons/";>Jakarta Commons
Project</a> that Struts relies on. You are welcome to use these
classes in your own applications. These JAR files should be
copied into the <code>/WEB-INF/lib</code> dirctory of
your web application.</li>
<li><code>struts.jar</code> - JAR file that contains the compiled
Java classes of Struts. You must
place this file in the <code>/WEB-INF/lib</code> directory of
your web application.</li>
<li><code>struts-xxxxx.tld</code> - The tag library descriptor files
for the Struts 1.1 tag libraries (bean, html, logic, and
template). You must place these files in the <code>/WEB-INF</code>
directory of your web application, and reference them with
appropriate <code><taglib></code> directives in your
web.xml file.</li>
<li><code>jdbc2_0-stdext.jar</code> - The JDBC 2.0 Optional Package
API classes (package <code>javax.sql</code>). You will need to
include this file in the <code>/WEB-INF/lib</code> directory
of your application, if it is not already made visible to web
applications by your servlet container.</li>
<li><code>struts-config_1_1.dtd</code> - The document type descriptor
(DTD) for the Struts 1.1 configuration file (which is typically named
<code>/WEB-INF/struts-config.xml</code>. Your configuration file
will be validated against an internal copy of this DTD -- this
copy is available for reference purposes only.</li>
<li><code>struts-config_1_0.dtd</code> - The document type descriptor
(DTD) for the Struts 1.0 configuration file (which is typically named
<code>/WEB-INF/struts-config.xml</code>. Your configuration file
will be validated against an internal copy of this DTD -- this
copy is available for reference purposes only.</li>
<li><code>web-app_2_2.dtd</code> - The document type descriptor (DTD)
for web.xml files conforming to the Servlet 2.2 specification.
This copy is for reference purposes only.</li>
<li><code>web-app_2_3.dtd</code> - The document type descriptor (DTD)
for web.xml files conforming to the Servlet 2.3 specification.
This copy is for reference purposes only.</li>
</ul></li>
<li><code>webapps/</code> - Web Application Archive (WAR) files for the
web applications that are included with Struts.</li>
</ul>
</section>
<section name="What's New?" href="New">
<p><strong>DEPRECATIONS</strong>:</p>
<ul>
<li><code>struts-config.dtd</code> in favor of
<code>struts-config_1_1.dtd</code>.</li>
</ul>
<p><strong>COMMONS PACKAGES</strong>:
Several components of Struts 1.0 have been found to be useful in
general Java development (and not just useful for building Struts-based
web applications), and have been migrated into the
<a href="http://jakarta.apache.org/commons/";>Jakarta Commons Project</a>.
As a result, the current development version of Struts has been modified
to rely on the Commons packages containing these classes, rather than the
Struts internal versions. In nearly every case, this involved changing
only the <code>import</code> statements at the top of your classes. Any
applications that utilize these classes will need to be modified in the
same way. The following Commons packages contain the replacements for the
corresponding Struts 1.0 classes:</p>
<ul>
<li><strong>BeanUtils Package</strong> (org.apache.commons.beanutils) -
<code>org.apache.struts.utils.BeanUtils</code>,
<code>org.apache.struts.utils.ConvertUtils</code>, and
<code>org.apache.struts.utils.PropertyUtils</code>.</li>
<li><strong>Collections Package</strong>
(org.apache.commons.collections) -
<code>org.apache.struts.util.ArrayStack</code>,
<code>org.apache.struts.util.FastArrayList</code>,
<code>org.apache.struts.util.FastHashMap</code>,
<code>org.apache.struts.util.FastTreeMap</code>.</li>
<li><strong>Digester Package</strong> -
(org.apache.commons.digester) -
<code>org.apache.struts.digester.*</code>.</li>
</ul>
<p><strong>XML PARSER PREREQUISITE UPDATED</strong>: Struts now depends
on an XML parser that conforms to the JAXP/1.1 (rather than JAXP/1.0)
APIs. Parsers known to work include the JAXP/1.1 reference implementation,
and Xerces 1.3.1.</p>
<p><strong>CONTRIB Directory</strong>:
A new directory (<code>contrib</code>) in the CVS source repository has
been added to accumulate Struts add-on extensions that are generally
useful but have not yet been integrated into the standard code base.</p>
<p>
<ul>
<li>ValidatorForm - Client and Server-side validation library.</li>
<li>Tiles - Advanced templating library (see Struts-Tiles.war).</li>
<li>Service Manager - Add custom services without subclassing controller.</li>
</ul>
</p>
<p><strong>UNIT TESTING SUPPORT</strong>: Support for running unit tests
on Struts components and custom tags is being added, utilizing the
<a href="http://jakarta.apache.org/cactus/";>Jakarta Cactus</a> product.</p>
<p>The following new features have been added to the basic controller
framework (package <code>org.apache.struts.action</code>):</p>
<ul>
<li>The new <code>ActionMessages</code> class will support a superset of
the capabilities of <code>ActionErrors</code>, and will be useful as
a collection of general purpose messages, not just errors.</li>
</ul>
<p>The following new features have been added to the utility classes
(package <code>org.apache.struts.util</code>):</p>
<ul>
<li>LocalStrings: Correct message regarding replaceable parameter so that it
does not append an extraneous character.</li>
<li>Add LabelValueBean class. This defines a collection of name/value pairs that
can be used with the <html:options> tag, and elsewhere.</li>
<li>MessageResources: Escape any single quote characters that are included in
the specified message string.</li>
<li>Allow a transaction token to be the only parameter in
computeParameters().</li>
<li>Change RequestUtils to encode ampersands when building a query string.</li>
</ul>
<p>The following new features have been added to the
<em>struts-bean</em> custom tag library (package
<code>org.apache.struts.taglib.bean</code>):</p>
<ul>
<li>Add format, locale and bundle attributes to bean:write to support values
formatting according to current
user locale, format string from attribute or format string from string
resources.</li>
<li>Correct the generated scripting variable type when the <bean:cookie>,
<bean:header>, or <bean:parameter> tag is used with the "multiple"
attribute.</li>
<li>Added <code>name</code>, <code>property</code>, and
<code>scope</code> attributes to the <code><bean:message></code>
tag, so that the message source key can be obtained dynamically from
a bean or bean property.</li>
</ul>
<p>The following new features have been added to the
<em>struts-html</em> custom tag library (package
<code>org.apache.struts.taglib.html</code>):</p>
<ul>
<li>On the Options tag, if the property specified by the "property" attribute
returns null, it now throws an error message that indicates what the real problem is,
rather than causing an NPE.</li>
<li>Added 'style' and 'styleClass' attributes for <html:option> and
<html:options> tags.</li>
<li>Added 'name', 'property' and 'scope' attributes to
<code><bean:message></code> so that
the message resource key can be obtained dynamically from a bean.</li>
<li>Added a new <code><html:messages></code> tag to iterate through
a message collection in the new <code>ActionMessages</code> class.</li>
<li><code>ActionForm</code> will now call <code>reset()</code> if it
instantiates the ActionForm bean.</li>
<li>Added indexed property to the SubmitTag, SelectTag, LinkTag.java,
CheckboxTag, ButtonTag, ImageTag, RadioTag, and TextArea.Tag.</li>
</ul>
<p>The following new features have been added to the
<em>struts-logic</em> custom tag library (package
<code>org.apache.struts.taglib.logic</code>):</p>
<ul>
<li>Added <code><logic:empty></code> and
<code><logic:notEmpty></code> tags, which are similar to
<code><logic:present></code> and
<code><logic:notPresent></code> except for the treatment of
empty strings.</li>
</ul>
<p>The following new features have been added to the
<em>struts-template</em> custom tag library (package
<code>org.apache.struts.taglib.template</code>):</p>
<ul>
<li>None.</li>
</ul>
<p>The following new features have been added to the Struts Documentation
application (and corresponding contents on the Struts web site):</p>
<ul>
<li>Move Tag Library documentation into User's Guide.</li>
<li>Added Kickstart FAQ.</li>
<li>Added Reference copy of 1.0 JavaDoc.</li>
<li>Revised the example page in the User's Guide (Building View Components) to
reflect current practice.</li>
<li>Revised installation instructions for SilverStream and Resin.</li>
</ul>
</section>
<section name="Changes and Bug Fixes" href="Changes">
<p>The following changes and bug fixes have occurred in the configuration
files related to Struts:</p>
<ul>
<li>Remove deprecated support for the old (Struts 0.5) configuration file
format.</li>
</ul>
<p>The following changes and bug fixes have occurred in the basic
controller framework (package <code>org.apache.struts.action</code>):</p>
<ul>
<li>Add InvokeAction and CreateActionForm methods to allow direct chaining of
Actions.</li>
<li>Add ContextHelper to expose framework elements to alternate presentation
layers.</li>
<li>ActionForms and related classes now use a StringBuffer when responding a
toString request in order to conserve resources.</li>
<li>Add standard LookupDispatchAction to help select between internationalized
buttons.</li>
<li>Modify ActionForm class to use ActionServletWrapper rather than expose
ActionServlet.</li>
<li>Add ActionServletWrapper class. Used by ActionForm to prevent the Public
String properties of ActionServlet from being changed via a query string.</li>
<li>Unconditionally pass the selected mapping as a request attribute under key
Action.MAPPING_KEY, even if no form bean is specified.</li>
<li>Avoid a NullPointerException in corner cases caused by failed initialization
of ActionServlet.</li>
<li>The <code>ActionForm</code> class is now truly serializable, because
the two non-serializable instance variables (servlet and
multipartRequestHandler) have been made transient. However, if you
actually do serialize and deserialize such instances, it is your
responsibility to reset these two properties.</li>
<li>Removed deprecated Struts 0.5 methods, and support for the Struts 0.5
configuration file format.</li>
<li>The initial order a property/key is added in is now maintained by
ActionMessages class.</li>
</ul>
<p>The following changes and bug fixes have occurred in the file upload
package (package <code>org.apache.struts.upload</code>):</p>
<ul>
<li>Correct MultiboxTagdoAfterBody() to return SKIP_BODY instead of
SKIP_PAGE.</li>
<li>Fixed lost byte problem in BufferedMultipartInputStream</li>
<li>Fixed ArrayIndexOutOfBoundsException situations</li>
<li>Better reporting for premature closing of input streams while reading
multipart requests.</li>
<li>Additional fix for file corruption problem with uploads and new line
characters.</li>
</ul>
<p>The following changes and bug fixes have occurred in the utilities
(package <code>org.apache.struts.util</code>):</p>
<ul>
<li>Modify RequestUtils class to use ActionServletWrapper rather than expose
ActionServlet.</li>
<li>Added error message for the getActionErrors and getActionMessages
method.</li>
<li>Added a getActionErrors and getActionMessages methods to generate the
correct corresponding object based on the object retrieved from request scope based on
the key passed in.</li>
<li>The logic for creating an ActionErrors or ActionMessages object has been
moved to a utility method in RequestUtils. The JspException message is also generated
in RequestUtils.</li>
<li><code>ConvertUtils.convertCharacter()</code> will now detect empty strings
and return the default value.</li>
</ul>
<p>The following changes and bug fixes have occured in the
<em>struts-bean</em> custom tag library (package
<code>org.apache.struts.taglib.bean</code>):</p>
<ul>
<li>The <code><html:errors></code> when the property tag is
specified, errors are no longer printed if the specified property
has no errors. Previously errors were always printed ! Future
enhancements would include additional attributes to always turn
off the header or footer. </li>
<li>Made the remaining helper methods "protected" rather than
"private".</li>
</ul>
<p>The following changes and bug fixes have occured in the
<em>struts-html</em> custom tag library (package
<code>org.apache.struts.taglib.html</code>):</p>
<ul>
<li>Fixed FormTag to exclude query string when identifying action mapping
name.</li>
<li>Added the 'align' attribute to the <html:image> tag.</li>
<li>Added indexed attribute to ImageTag, RadioTag, and TextAreaTag.</li>
<li>Added MessagesTag.</li>
<li>Correctly URLEncode the query string parameter value on ImgTag, even if
there is only a single parameter.</li>
</ul>
<p>The following changes and bug fixes have occurred in the
<em>struts-logic</em> custom tag library (package
<code>org.apache.struts.taglib.logic</code>):</p>
<ul>
<li>None.</li>
</ul>
<p>The following changes and bug fixes to the Struts Documentation
application (and corresponding contents on the Struts web site) have
occurred:</p>
<ul>
<li>In the HTML tag documentation, expand to cover using indexed properties with
iterate.</li>
<li>Add installation notes for Jetty.</li>
<li>In the Tag Developers Guide, add more detail regarding file upload
requirements.</li>
<li>In the Introduction, added references to basic background material.</li>
<li>In Building View Components, clarify that additional i18n support may be
provided by the browser, and is outside the scope of the framework.</li>
<li>In Building Controller Components, document 'validating' init-param, add
defaults for various parameters, clarify that some web.xml settings are not
Struts-specific.</li>
<li>Reorganized to separate 1.0 material from nightly build material.</li>
<li>Expanded Resources section.</li>
<li>Various updates regarding other release notes.</li>
</ul>
<p>The following changes and bug fixes to the Struts Example Application
have occurred:</p>
<ul>
<li>Add Russiand and Japanese translations of the application resources and set
the character set for the example JSP pages to "UTF-8" so that it can display either
English or Japanese.</li>
<li>Exchange "name" for "attribute" properties for Edit mappings in Struts
configuration file.</li>
<li>Remove references to saving database data from "tour" document, since this
functionality was removed.</li>
</ul>
<p>The following changes and bug fixes to the Struts Template Example
Application have occurred:</p>
<ul>
<li>None.</li>
</ul>
<p>The following changes and bug fixes to the Struts Excercise Taglib Example
Application have occurred:</p>
<ul>
<li>Added test case for <html:select> using <html:options> based on a
collection
saved in the page context.</li>
</ul>
<p>
Next: <a href="installation.html">Installation</a>
</p>
</section>
</body>
</document>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
