Author: niallp
Date: Sat Dec 2 21:03:42 2006
New Revision: 481721
URL: http://svn.apache.org/viewvc?view=rev&rev=481721
Log:
de-tab the release notes
Modified:
struts/struts1/trunk/src/site/xdoc/userGuide/release-notes.xml
Modified: struts/struts1/trunk/src/site/xdoc/userGuide/release-notes.xml
URL:
http://svn.apache.org/viewvc/struts/struts1/trunk/src/site/xdoc/userGuide/release-notes.xml?view=diff&rev=481721&r1=481720&r2=481721
==============================================================================
--- struts/struts1/trunk/src/site/xdoc/userGuide/release-notes.xml (original)
+++ struts/struts1/trunk/src/site/xdoc/userGuide/release-notes.xml Sat Dec 2
21:03:42 2006
@@ -95,47 +95,47 @@
</action>
</pre>
- <p>Just as the
<code>TilesRequestProcessor</code> could recognize a tile definition
- and resolve it
to the intended JSP, so does Struts now have built-in
- recognition for
URIs that begin with an <code>actionId</code> and will automatically
- translate
forwards. Both these forwards below will be resolved internally
- to
<code>/person/view.do</code> (with parameters included):
- </p>
-
+ <p>Just as the <code>TilesRequestProcessor</code> could recognize a
tile definition
+ and resolve it to the intended JSP, so does Struts now have built-in
+ recognition for URIs that begin with an <code>actionId</code> and will
automatically
+ translate forwards. Both these forwards below will be resolved
internally
+ to <code>/person/view.do</code> (with parameters included):
+ </p>
+
<pre>
<forward name="success" path="viewPersonAction" />
<forward name="success"
path="viewPersonAction?fruit=banana&color=yellow" />
</pre>
-
- <p>You can
effectively eliminate all URI management throughout the Struts configuration
- files
<b>and</b> within JSP. The tag libraries are also updated to recognize the
-
<code>actionId</code>:</p>
-
+
+ <p>You can effectively eliminate all URI management throughout the
Struts configuration
+ files <b>and</b> within JSP. The tag libraries are also updated to
recognize the
+ <code>actionId</code>:</p>
+
<pre>
<html:form action="savePersonAction">...</html:form>
<html:link action="viewPersonAction">...</html:link>
</pre>
-
- <p>Note: It is
good practice to name the <code>actionId</code> as <em>entityAction</em>
- to distinguish
the identifier from, perhaps, a Tiles definition named <em>entityPage</em>.</p>
-
-
<h4>Internationalization (I18N) Tag Properties</h4>
-
- <p>Struts tag
libraries now include the HTML I18N properties. This allows sites that
- specialize in
internationalization to specify both bi-directional text and language
- at the tag
level:</p>
-
+
+ <p>Note: It is good practice to name the <code>actionId</code> as
<em>entityAction</em>
+ to distinguish the identifier from, perhaps, a Tiles definition named
<em>entityPage</em>.</p>
+
+ <h4>Internationalization (I18N) Tag Properties</h4>
+
+ <p>Struts tag libraries now include the HTML I18N properties. This
allows sites that
+ specialize in internationalization to specify both bi-directional text
and language
+ at the tag level:</p>
+
<pre>
<html:link action="viewPersonAction" dir="ltor" lang="es"/>vea a
persona</html:link>
</pre>
- <h4>Dynamic
Link Parameters</h4>
-
- <p>The Struts
<code><html:link></code>, <code><html:frame></code>,
-
<code><html:rewrite></code> tag libaries now allow their bodies to nest
the new
-
<code><html:param></code> tag. This is useful when it is awkward (or
inappropriate)
- to pass in
existing parameters as a <code>Map</code>, which is still supported and will
- be appened to
any present <code><html:param></code> tags:</p>
+ <h4>Dynamic Link Parameters</h4>
+
+ <p>The Struts <code><html:link></code>,
<code><html:frame></code>,
+ <code><html:rewrite></code> tag libaries now allow their bodies
to nest the new
+ <code><html:param></code> tag. This is useful when it is awkward
(or inappropriate)
+ to pass in existing parameters as a <code>Map</code>, which is still
supported and will
+ be appened to any present <code><html:param></code> tags:</p>
<pre>
<html:link action="viewPersonAction">
