husted 2003/12/09 17:02:25
Modified: doc/userGuide release-notes.xml
Log:
+ apply HTML Tidy -xml -i -m -wrap 0
Revision Changes Path
1.36 +184 -219 jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/release-notes.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- release-notes.xml 10 Dec 2003 00:57:50 -0000 1.35
+++ release-notes.xml 10 Dec 2003 01:02:25 -0000 1.36
@@ -1,6 +1,5 @@
<?xml version="1.0"?>
<document url="release-notes.html">
-
<properties>
<author>Craig R. McClanahan</author>
<author>Robert Leland</author>
@@ -8,230 +7,196 @@
<author>Martin Cooper</author>
<title>Struts Release Notes (Nightly Build)</title>
</properties>
-
<body>
-
- <section name="Introduction" href="Introduction">
-
- <p>This section contains the release notes for
- <strong>nightly build</strong> of the Struts Framework,
- for changes that have taken place since
- <a href="release-notes-1.1.html">Version 1.1 </a>
- was released.
- </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.txt</code> - Brief installation instructions.
- For more detail, see the <code>Struts User Guide</code>, either through
- the Struts Documentation application or online at
- <a
href="http://jakarta.apache.org/struts/";>http://jakarta.apache.org/struts/</a>.
- </li>
- <li><code>LICENSE.txt</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.txt</code> - A brief introduction to Struts.</li>
- <li><code>contrib/</code> - Additional libraries developed by the Struts team
- which are not yet part of the core distribution.</li>
- <li><code>lib/</code> - Directory containing files you will need in
- your own applications. The individual files of interest are:
+ <section name="Introduction" href="Introduction">
+ <p>This section contains the release notes for
+ <strong>nightly build</strong>of the Struts Framework, for changes that have
taken place since
+ <a href="release-notes-1.1.html">Version 1.1</a>was released.</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.txt</code>- Brief installation instructions. For more detail,
see the
+ <code>Struts User Guide</code>, either through the Struts Documentation
application or online at
+ <a
href="http://jakarta.apache.org/struts/";>http://jakarta.apache.org/struts/</a>.</li>
+ <li>
+ <code>LICENSE.txt</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.txt</code>- A brief introduction to Struts.</li>
+ <li>
+ <code>contrib/</code>- Additional libraries developed by the Struts team
which are not yet part of the core distribution.</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> directory of
- your web application.</li>
- <li><code>jakarta-oro-#.#.jar</code> - JAR file containing the Jakarta
- ORO package, utilitied by the Struts Valdiator. You must place
- this file in the <code>/WEB-INF/lib</code> directory of
- your web application to use the Struts Validator package.</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-*.tld</code> - The tag library descriptor files
- for the Struts tag libraries (bean, html, logic, and nested).
- When these taglibs are used, 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>struts-config_1_2.dtd</code> - The Document Type Definition
- (DTD) for the Struts 1.2 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_1.dtd</code> - The Document Type Definition
- (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 Definition
- (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 Definition (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 Definition (DTD)
- for web.xml files conforming to the Servlet 2.3 specification.
- This copy is for reference purposes only.</li>
+ <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>directory of your web application.</li>
+ <li>
+ <code>jakarta-oro-#.#.jar</code>- JAR file containing the Jakarta ORO
package, utilitied by the Struts Valdiator. You must place this file in the
+ <code>/WEB-INF/lib</code>directory of your web application to use the
Struts Validator package.</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-*.tld</code>- The tag library descriptor files for the
Struts tag libraries (bean, html, logic, and nested). When these taglibs are used, 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>struts-config_1_2.dtd</code>- The Document Type Definition (DTD)
for the Struts 1.2 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_1.dtd</code>- The Document Type Definition (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 Definition (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 Definition (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 Definition (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>
-
- <p>The following Jakarta Commons libraries are included with this release
- of Struts:</p>
- <ul>
- <li>Commons BeanUtils 1.6.1</li>
- <li>Commons Collections 2.1</li>
- <li>Commons Digester 1.5</li>
- <li>Commons FileUpload 1.0</li>
- <li>Commons Lang 2.0</li>
- <li>Commons Logging 1.0.3</li>
- <li>Commons Validator 1.1.1-dev</li>
- </ul>
-
- </section>
-
- <section name="What Changed?" href="Changes">
-
- <p><strong>Configuration Changes</strong> [<code>/conf/shared</code>]</p>
- <ul>
- <li>
- <code><a
href="http://jakarta.apache.org/struts/dtds/struts-config_1_2.dtd";>struts-config_1_2.dtd</a></code>
- is preferred to the deprecated Struts Configuration 1.1 DTD.
- The new DTD adds two new elements <display-name>
- and <description> to the struts-config element.
- These elements are for use by struts config file tools and document
generation.
- In the Struts 1.2.x series, existing Struts configuration files can
be
- loaded using either DTD version.
- </li>
- </ul>
-
- <p><strong>Action Package Changes</strong>
[<code>org.apache.struts.action</code>]</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- <p><strong>Actions Package Changes</strong>
[<code>org.apache.struts.actions</code>]</p>
- <ul>
- <li>The DispatchAction now provides default cancel handler that can
be overridden.
- It also also possible to specify the default handler name.</li>
- <li>The LookupDispatchAction now provides default cancel handler
that can be overridden.
- It also also possible to specify the default handler name.</li>
- </ul>
-
- <p><strong>Config Package</strong>
[<code>org.apache.struts.config</code>]</p>
- <ul>
- <li>ApplicationConfig: removed in favor of ModuleConfig.</li>
- </ul>
-
- <p><strong>Plugins Package</strong>
[<code>org.apache.struts.plugins</code>]</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- <p><strong>Bean Taglib Package Changes</strong>
[<code>org.apache.struts.taglib.bean</code>]</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- <p><strong>HTML Taglib Package Changes</strong>
[<code>org.apache.struts.taglib.html</code>]:</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- <p><strong>Logic Taglib Package Changes</strong>
[<code>org.apache.struts.taglib.logic</code>]:</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- <p><strong>Nested Taglib Package Changes</strong>
[<code>org.apache.struts.nested.logic</code>]:</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- <p><strong>Tiles Taglib Package Changes</strong>
[<code>org.apache.struts.tiles.logic</code>]:</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- <p><strong>Tiles Package Changes</strong>
[<code>org.apache.struts.tiles</code>]:</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- <p><strong>Upload Package Changes</strong>
[<code>org.apache.struts.upload</code>]:</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- <p><strong>Utility Package Changes</strong>
[<code>org.apache.struts.util</code>]:</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- <p><strong>Validator Package Changes</strong>
[<code>org.apache.struts.validator</code>]</p>
- <ul>
- <li>initModuleConfigFactory()</li>
- <li>methods created for backward-compatiblity only</li>
- <li>isStopOnFirstError</li>
- <li>setStopOnFirstError</li>
- <li>validator-rules.xml, range() is deprecated - use intRange()
instead.</li>
- </ul>
-
- <ul>
- <li>The ValidatorPlugin: It is now possible to force the client side
- Javascript validation to check all constraints, instead of stopping
- at the first error. By setting a new property, stopOnFirstError,
- on the validator plug in tag to false. This is in the
struts-config.xml as follow:
-<pre>
+ <li>
+ <code>webapps/</code>- Web Application Archive (WAR) files for the web
applications that are included with Struts.</li>
+ </ul>
+ <p>The following Jakarta Commons libraries are included with this release of
Struts:</p>
+ <ul>
+ <li>Commons BeanUtils 1.6.1</li>
+ <li>Commons Collections 2.1</li>
+ <li>Commons Digester 1.5</li>
+ <li>Commons FileUpload 1.0</li>
+ <li>Commons Lang 2.0</li>
+ <li>Commons Logging 1.0.3</li>
+ <li>Commons Validator 1.1.1-dev</li>
+ </ul>
+ </section>
+ <section name="What Changed?" href="Changes">
+ <p>
+ <strong>Configuration Changes</strong>[
+ <code>/conf/shared</code>]</p>
+ <ul>
+ <li>
+ <code>
+ <a
href="http://jakarta.apache.org/struts/dtds/struts-config_1_2.dtd";>struts-config_1_2.dtd</a>
+ </code>is preferred to the deprecated Struts Configuration 1.1 DTD. The new
DTD adds two new elements <display-name> and <description> to the
struts-config element. These elements are for use by struts config file tools and
document generation. In the Struts 1.2.x series, existing Struts configuration files
can be loaded using either DTD version.</li>
+ </ul>
+ <p>
+ <strong>Action Package Changes</strong>[
+ <code>org.apache.struts.action</code>]</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ <p>
+ <strong>Actions Package Changes</strong>[
+ <code>org.apache.struts.actions</code>]</p>
+ <ul>
+ <li>The DispatchAction now provides default cancel handler that can be
overridden. It also also possible to specify the default handler name.</li>
+ <li>The LookupDispatchAction now provides default cancel handler that can
be overridden. It also also possible to specify the default handler name.</li>
+ </ul>
+ <p>
+ <strong>Config Package</strong>[
+ <code>org.apache.struts.config</code>]</p>
+ <ul>
+ <li>ApplicationConfig: removed in favor of ModuleConfig.</li>
+ </ul>
+ <p>
+ <strong>Plugins Package</strong>[
+ <code>org.apache.struts.plugins</code>]</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ <p>
+ <strong>Bean Taglib Package Changes</strong>[
+ <code>org.apache.struts.taglib.bean</code>]</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ <p>
+ <strong>HTML Taglib Package Changes</strong>[
+ <code>org.apache.struts.taglib.html</code>]:</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ <p>
+ <strong>Logic Taglib Package Changes</strong>[
+ <code>org.apache.struts.taglib.logic</code>]:</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ <p>
+ <strong>Nested Taglib Package Changes</strong>[
+ <code>org.apache.struts.nested.logic</code>]:</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ <p>
+ <strong>Tiles Taglib Package Changes</strong>[
+ <code>org.apache.struts.tiles.logic</code>]:</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ <p>
+ <strong>Tiles Package Changes</strong>[
+ <code>org.apache.struts.tiles</code>]:</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ <p>
+ <strong>Upload Package Changes</strong>[
+ <code>org.apache.struts.upload</code>]:</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ <p>
+ <strong>Utility Package Changes</strong>[
+ <code>org.apache.struts.util</code>]:</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ <p>
+ <strong>Validator Package Changes</strong>[
+ <code>org.apache.struts.validator</code>]</p>
+ <ul>
+ <li>initModuleConfigFactory()</li>
+ <li>methods created for backward-compatiblity only</li>
+ <li>isStopOnFirstError</li>
+ <li>setStopOnFirstError</li>
+ <li>validator-rules.xml, range() is deprecated - use intRange()
instead.</li>
+ </ul>
+ <ul>
+ <li>The ValidatorPlugin: It is now possible to force the client side
Javascript validation to check all constraints, instead of stopping at the first
error. By setting a new property, stopOnFirstError, on the validator plug in tag to
false. This is in the struts-config.xml as follow:
+ <pre>
<plug-in className="org.apache.struts.validator.ValidatorPlugIn">
<set-property property="pathnames"
value="/WEB-INF/validation.xml,/WEB-INF/validator-rules.xml"/>
<set-property property="stopOnFirstError" value="true"/>
</plug-in>
-</pre>
- </li>
- <li>validator-rules.xml[intRange]: IntRange now checks select-one and
radio fields.
- Example:
- This allows populating combo boxes with valid choices plus one
additional choice
- with a caption something like "Choose one" and a value 0f "-1".
- Then when the user attempts to submit the form, you can look for
the value of
- "-1" and yell at them if they failed to pick something.
- </li>
- </ul>
-
- <p><strong>Documentation Application Changes</strong>
[<code>struts-documentation.war</code>]:</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- <p><strong>MailReader Example Application Changes</strong>
[<code>struts-example.war</code>]:</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- <p><strong>Exercise Taglib Example Application Changes</strong>
[<code>struts-taglib-exercise.war</code>]:</p>
- <ul>
- <li>No signficant changes.</li>
- </ul>
-
- </section>
-
-<section>
- <p class="right">
- Next: <a href="installation.html">Installation</a>
- </p>
-</section>
-
- </body>
-
+</pre></li>
+ <li>validator-rules.xml[intRange]: IntRange now checks select-one and radio
fields. Example: This allows populating combo boxes with valid choices plus one
additional choice with a caption something like "Choose one" and a value 0f "-1". Then
when the user attempts to submit the form, you can look for the value of "-1" and yell
at them if they failed to pick something.</li>
+ </ul>
+ <p>
+ <strong>Documentation Application Changes</strong>[
+ <code>struts-documentation.war</code>]:</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ <p>
+ <strong>MailReader Example Application Changes</strong>[
+ <code>struts-example.war</code>]:</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ <p>
+ <strong>Exercise Taglib Example Application Changes</strong>[
+ <code>struts-taglib-exercise.war</code>]:</p>
+ <ul>
+ <li>No signficant changes.</li>
+ </ul>
+ </section>
+ <section>
+ <p class="right">Next:
+ <a href="installation.html">Installation</a></p>
+ </section>
+ </body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
