You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by jm...@apache.org on 2002/12/24 02:50:09 UTC
cvs commit: jakarta-struts/doc/userGuide building_model.xml building_view.xml configuration.xml dev_tiles.xml dev_validator.xml index.xml installation-ipas.xml installation-jr30.xml installation-ubs72.xml installation-was352.xml installation.xml introduction.xml preface.xml release-notes-1.0-b1.xml release-notes-1.0-b2.xml release-notes-1.0-b3.xml release-notes-1.0.1.xml release-notes-1.0.xml release-notes-1.1-b1.xml release-notes-1.1-b2.xml release-notes.xml struts-logic.xml struts-nested.xml struts-tiles.xml
jmitchell 2002/12/23 17:50:09
Modified: doc/userGuide building_model.xml building_view.xml
configuration.xml dev_tiles.xml dev_validator.xml
index.xml installation-ipas.xml
installation-jr30.xml installation-ubs72.xml
installation-was352.xml installation.xml
introduction.xml preface.xml
release-notes-1.0-b1.xml release-notes-1.0-b2.xml
release-notes-1.0-b3.xml release-notes-1.0.1.xml
release-notes-1.0.xml release-notes-1.1-b1.xml
release-notes-1.1-b2.xml release-notes.xml
struts-logic.xml struts-nested.xml struts-tiles.xml
Log:
Fix a few typos (and tabs to spaces, sorry about that, I've turned it off after this)
Revision Changes Path
1.13 +1 -1 jakarta-struts/doc/userGuide/building_model.xml
Index: building_model.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/building_model.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- building_model.xml 10 Oct 2002 03:15:16 -0000 1.12
+++ building_model.xml 24 Dec 2002 01:50:07 -0000 1.13
@@ -275,7 +275,7 @@
<p>
Note that you can define as many datasource objects as your application requires and
- refer to each using a logical name. This can be useful in proding better security or
+ refer to each using a logical name. This can be useful in providing better security or
scalability, or even to test datasource implementations against each other.
</p>
1.22 +50 -50 jakarta-struts/doc/userGuide/building_view.xml
Index: building_view.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/building_view.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- building_view.xml 22 Dec 2002 23:10:28 -0000 1.21
+++ building_view.xml 24 Dec 2002 01:50:07 -0000 1.22
@@ -689,59 +689,59 @@
Tiles is a powerful templating library that allows you to construct views by combining
various "tiles". Here's a quick setup guide:
</p>
- <ol>
- <li>Create a /layout/layout.jsp file that contains your app's common look and feel:
- <pre>
- <html>
- <body>
- <tiles:insert attribute="body"/>
- </body>
- </html>
- </pre>
- </li>
- <li>
- Create your /index.jsp homepage file:
- <pre>
- <h1>This is my homepage!</h1>
- </pre>
- </li>
- <li>Create a /WEB-INF/tiles-defs.xml file that looks like this:<br/>
- <pre>
- <tiles-definitions>
- <definition name="layout" path="/layout/layout.jsp">
- <put name="body" value=""/>
- </definition>
- <definition name="homepage" extends="layout">
- <put name="body" value="/index.jsp"/>
- </definition>
- <tiles-definitions>
- </pre>
- </li>
- <li>
- Setup the TilesPlugin in the struts-config.xml file:
- <pre>
- <plug-in className="org.apache.struts.tiles.TilesPlugin">
- <set-property property="definitions-config" value="/WEB-INF/tiles-defs.xml"/>
- </plug-in>
- </pre>
- </li>
- <li>
- Setup an action mapping in struts-config.xml to point to your homepage tile:
- <pre>
- <action
- path="/index"
- type="org.apache.struts.actions.ForwardAction"
- parameter="homepage"/>
- </pre>
- </li>
+ <ol>
+ <li>Create a /layout/layout.jsp file that contains your app's common look and feel:
+ <pre>
+ <html>
+ <body>
+ <tiles:insert attribute="body"/>
+ </body>
+ </html>
+ </pre>
+ </li>
+ <li>
+ Create your /index.jsp homepage file:
+ <pre>
+ <h1>This is my homepage!</h1>
+ </pre>
+ </li>
+ <li>Create a /WEB-INF/tiles-defs.xml file that looks like this:<br/>
+ <pre>
+ <tiles-definitions>
+ <definition name="layout" path="/layout/layout.jsp">
+ <put name="body" value=""/>
+ </definition>
+ <definition name="homepage" extends="layout">
+ <put name="body" value="/index.jsp"/>
+ </definition>
+ <tiles-definitions>
+ </pre>
+ </li>
+ <li>
+ Setup the TilesPlugin in the struts-config.xml file:
+ <pre>
+ <plug-in className="org.apache.struts.tiles.TilesPlugin">
+ <set-property property="definitions-config" value="/WEB-INF/tiles-defs.xml"/>
+ </plug-in>
+ </pre>
+ </li>
+ <li>
+ Setup an action mapping in struts-config.xml to point to your homepage tile:
+ <pre>
+ <action
+ path="/index"
+ type="org.apache.struts.actions.ForwardAction"
+ parameter="homepage"/>
+ </pre>
+ </li>
</ol>
<p>
- The TilesPlugin configures a special RequestProcessor that determines if the requested view is a
- tile and processes it accordingly. Note that we made the homepage tile extend our root layout
- tile and changed the body attribute. Tiles inserts the file named in the body attribute into the main
- layout.
+ The TilesPlugin configures a special RequestProcessor that determines if the requested view is a
+ tile and processes it accordingly. Note that we made the homepage tile extend our root layout
+ tile and changed the body attribute. Tiles inserts the file named in the body attribute into the main
+ layout.
</p>
- <p>See the the tiles-documentation webapp for in-depth examples.</p>
+ <p>See the tiles-documentation webapp for in-depth examples.</p>
</section>
<section name="3.4.4 Image Rendering Components" href="image_rendering">
1.4 +23 -23 jakarta-struts/doc/userGuide/configuration.xml
Index: configuration.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/configuration.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- configuration.xml 22 Dec 2002 06:10:05 -0000 1.3
+++ configuration.xml 24 Dec 2002 01:50:07 -0000 1.4
@@ -20,32 +20,32 @@
<section name="7.1 Overview" href="config-overview">
- <p>
- [:TODO:]
- </p>
-
+ <p>
+ [:TODO:]
+ </p>
+
</section>
-
+
<section name="7.2 The Struts configuration file" href="struts-config">
-
- <p>
+
+ <p>
The <a href="building_controller.html#config">Building Controller
Components</a> chapter covered writing the form-bean and action-mapping
portions of the Struts configuration file.
- These elements usually play an important role in the development of a
- Struts application.
- The other elements in Struts configuration file tend to be static:
- you set them once and leave them alone.
- </p>
-
- <p>
- These "static" configuration elements are :
- </p>
-
- <ul>
- <li>[:TODO:]</li>
+ These elements usually play an important role in the development of a
+ Struts application.
+ The other elements in Struts configuration file tend to be static:
+ you set them once and leave them alone.
+ </p>
+
+ <p>
+ These "static" configuration elements are :
+ </p>
+
+ <ul>
+ <li>[:TODO:]</li>
</ul>
-
+
</section>
<section name="7.2.1 Controller Configuration" href="controller_config">
@@ -73,7 +73,7 @@
<li>
<b>contentType</b> - Default content type (and optional character
encoding) to be set on each response. May be overridden by the
- Action, JSP, or other rewource to which the request is forwarded.
+ Action, JSP, or other resource to which the request is forwarded.
[text/html] (optional)
</li>
<li>
@@ -166,7 +166,7 @@
<section name="7.2.2 Message Resources Configuration" href="resources_config">
<p>
- Struts has builtin support for internationalization (I18N).
+ Struts has built in support for internationalization (I18N).
You can define one or more <code><message-resources></code> elements for your webapp;
modules can define their own resource bundles.
Different bundles can be used simultaneously in your application, the 'key' attribute is used to specify the desired bundle.
@@ -390,7 +390,7 @@
<p>
(My struts-default.xml would be equivalent to what most folks call struts-config.xml. I just
- like the symmety of having all my Struts module files being named struts-<module>.xml)
+ like the symmetry of having all my Struts module files being named struts-<module>.xml)
</p>
</section>
1.12 +2 -2 jakarta-struts/doc/userGuide/dev_tiles.xml
Index: dev_tiles.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/dev_tiles.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- dev_tiles.xml 5 Nov 2002 14:18:04 -0000 1.11
+++ dev_tiles.xml 24 Dec 2002 01:50:07 -0000 1.12
@@ -117,7 +117,7 @@
</li>
<li>
- It is possible to define library ofreusable <em><strong>Tiles</strong>
+ It is possible to define library of reusable <em><strong>Tiles</strong>
</em>.
</li>
@@ -151,7 +151,7 @@
</li>
<li>
- For example, key could be user provilege, browser type, ...
+ For example, key could be user privilege, browser type, ...
</li>
<li>
1.16 +2 -2 jakarta-struts/doc/userGuide/dev_validator.xml
Index: dev_validator.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/dev_validator.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- dev_validator.xml 7 Dec 2002 22:41:34 -0000 1.15
+++ dev_validator.xml 24 Dec 2002 01:50:07 -0000 1.16
@@ -67,7 +67,7 @@
<section href="validator-changes" name="Changes and deprecations">
<p> <strong>Validating against the DTD in the commons-validator.jar. </strong></p>
-<p> Struts no longer maintains a seperate dtd for validator-rules.xml and validator.xml.
+<p> Struts no longer maintains a separate dtd for validator-rules.xml and validator.xml.
Additionally, commons-validator now maintains a unified validator.dtd.
Change all validator.xml DTD references to:
<ol><pre>
@@ -219,7 +219,7 @@
<section href="resources" name="Validator Resources">
<p>
<a href="http://www.strutskickstart.com/">
-<b>DynaForms and the Validator</b></a> by by James Turner and Kevin Bedell.
+<b>DynaForms and the Validator</b></a> by James Turner and Kevin Bedell.
Sample chapter from
<a href="http://www.strutskickstart.com/">Struts Kickstart</a>;
available as a free download (PDF).
1.23 +7 -7 jakarta-struts/doc/userGuide/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/index.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- index.xml 21 Dec 2002 02:37:10 -0000 1.22
+++ index.xml 24 Dec 2002 01:50:07 -0000 1.23
@@ -118,10 +118,10 @@
<li><a href="building_controller.html#plugin_classes">4.6 Plugin Classes</a></li>
<li><a href="building_controller.html#actionmapping">4.7 The ActionMapping Implementation</a></li>
<li><a href="building_controller.html#config">4.8 Writing ActionMappings</a>
- <ul>
+ <ul>
<li><a href="building_controller.html#action_mapping_example">4.8.1 ActionMapping Example</a></li>
- </ul>
- </li>
+ </ul>
+ </li>
<li><a href="building_controller.html#module_config-use_actions">4.9 Using ActionMappings for Pages</a></li>
<li><a href="building_controller.html#logging">4.10 Using The Commons Logging Interface</a></li>
</ul></li>
@@ -162,11 +162,11 @@
</ul>
<li>7. Configuring Applications</li>
- <ul>
- <li><a href="configuration.html#config-overview">7.1 Overview</a></li>
+ <ul>
+ <li><a href="configuration.html#config-overview">7.1 Overview</a></li>
<li><a href="configuration.html#config">7.2 The Struts Configuration File</a>
<ul>
- <li><a href="configuration.html#plugin_config">7.2.1 Controller Configurationn</a></li>
+ <li><a href="configuration.html#plugin_config">7.2.1 Controller Configuration</a></li>
<li><a href="configuration.html#resources_config">7.2.2 Message Resources Configuration</a></li>
<li><a href="configuration.html#PlugIn_config">7.2.3 PlugIn Configuration</a></li>
<li><a href="configuration.html#data-source_config">7.2.4 Data Source Configuration</a></li>
@@ -175,7 +175,7 @@
</ul>
</li>
<li>
- <a href="configuration.html#dd_config">7.3 The Web Application Deployment Descriptor</a>
+ <a href="configuration.html#dd_config">7.3 The Web Application Deployment Descriptor</a>
<ul>
<li><a href="configuration.html#dd_config_servlet">7.3.1 Configure the Action Servlet Instance</a></li>
<li><a href="configuration.html#dd_config_mapping">7.3.2 Configure the Action Servlet Mapping</a></li>
1.3 +1 -1 jakarta-struts/doc/userGuide/installation-ipas.xml
Index: installation-ipas.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/installation-ipas.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- installation-ipas.xml 31 Aug 2002 13:15:02 -0000 1.2
+++ installation-ipas.xml 24 Dec 2002 01:50:07 -0000 1.3
@@ -133,7 +133,7 @@
<p>The first time you deploy you will be prompted by a Deploy wizard and asked to
supply both locations of the struts-example.ear file and of the cc.xml file.
Once both elements have been satisfied continue until the finish button and
-click it. The EAR file should deploy sucessfully.</p>
+click it. The EAR file should deploy successfully.</p>
<p>Test the sample application by using the following URL in the browser:</p>
<p>
<code>http://hostname:9000/struts-example/index.jsp</code>
1.3 +1 -1 jakarta-struts/doc/userGuide/installation-jr30.xml
Index: installation-jr30.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/installation-jr30.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- installation-jr30.xml 31 Aug 2002 13:15:02 -0000 1.2
+++ installation-jr30.xml 24 Dec 2002 01:50:07 -0000 1.3
@@ -33,7 +33,7 @@
<pre>
/struts-example/index.jsp:
-javax.servlet.ServletException: Compilation error occured:
+javax.servlet.ServletException: Compilation error occurred:
allaire.jrun.scripting.DefaultCFE:
1.3 +1 -1 jakarta-struts/doc/userGuide/installation-ubs72.xml
Index: installation-ubs72.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/installation-ubs72.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- installation-ubs72.xml 31 Aug 2002 13:15:02 -0000 1.2
+++ installation-ubs72.xml 24 Dec 2002 01:50:07 -0000 1.3
@@ -42,7 +42,7 @@
</li>
<li> Note: "<PLUGIN>" represents the plugin you are using for your specific
- webserver. For apache on Windows, it might be "cgi-bin/SaCGI.exe", for IIS
+ webserver. For Apache on Windows, it might be "cgi-bin/SaCGI.exe", for IIS
on Windows, it might be "scripts/SaCGI.exe" or "scripts/ISAPI.dll". Consult
the UBS documentation for more information. </li>
</ul>
1.3 +1 -1 jakarta-struts/doc/userGuide/installation-was352.xml
Index: installation-was352.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/installation-was352.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- installation-was352.xml 31 Aug 2002 13:15:02 -0000 1.2
+++ installation-was352.xml 24 Dec 2002 01:50:07 -0000 1.3
@@ -105,7 +105,7 @@
<code>$STRUTS_HOME/lib/struts-config_1_0.dtd</code> <br/>
to <br/>
<code>$WAS_HOME/AppServer/hosts/default_host/struts-example/servlets/org/apache/struts/resources/struts-config_1_0.dtd</code><br/>
- or be connected to the Internet to fetch the dtd from the jakarta web site.</li>
+ or be connected to the Internet to fetch the dtd from the Jakarta web site.</li>
<li>Start your webapp in the Admin Console</li>
1.21 +2 -2 jakarta-struts/doc/userGuide/installation.xml
Index: installation.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/installation.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- installation.xml 22 Dec 2002 01:25:33 -0000 1.20
+++ installation.xml 24 Dec 2002 01:50:07 -0000 1.21
@@ -308,7 +308,7 @@
<li>Jetty - <a href="installation-jetty.html">Additional steps required.</a></li>
<li>JRun - <a href="installation-jr30.html">Additional steps required.</a></li>
<li>Novell ExteNd Application Server 4.0+ -
- <a href="installation-novell.html">Additional steps requird.</a></li>
+ <a href="installation-novell.html">Additional steps required.</a></li>
<li>Orion Application Server - <a href="installation-oas.html">Additional steps
required.</a></li>
<li>Resin 1.2+ "standalone" - No additional steps required.</li>
@@ -405,7 +405,7 @@
from the Jakarta Commons project, must be in your classpath when
compiling Struts. The <code>build.xml</code> provided does this
automatically. If you use your development machine to test Struts
- application locally, be sure that the <code>stuts.jar</code> is
+ application locally, be sure that the <code>struts.jar</code> is
<strong>NOT</strong> on your classpath when your container is running.
</p>
1.14 +7 -7 jakarta-struts/doc/userGuide/introduction.xml
Index: introduction.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/introduction.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- introduction.xml 29 Oct 2002 05:30:24 -0000 1.13
+++ introduction.xml 24 Dec 2002 01:50:07 -0000 1.14
@@ -58,7 +58,7 @@
design pattern abstracted from the venerable
<a href="http://st-www.cs.uiuc.edu/users/smarch/st-docs/mvc.html">Smalltalk MVC framework</a>.
Java Web developers now tend to use the terms Model 2 and MVC interchangeably. In this guide, we use
- the MVC paradigm to describe the Struts architechture, which might be best termed a Model 2/MVC
+ the MVC paradigm to describe the Struts architecture, which might be best termed a Model 2/MVC
design.
</p>
@@ -162,7 +162,7 @@
</p>
<p>
- Struts includes a set of custom custom tag libraries that facilitate
+ Struts includes a set of custom tag libraries that facilitate
creating user interfaces that are fully internationalized, and that
interact gracefully with <code>ActionForm</code> beans that are part
of the <i>Model</i> portion of the system.
@@ -311,9 +311,9 @@
Web applications is retaining and validating what a user has entered between
requests. With Struts, you can define your own set of input bean classes, by
subclassing
- <a href="http://jakarta.apache.org/struts/api/org/apache/struts/action/ActionForm.html">Actionform</a>
+ <a href="http://jakarta.apache.org/struts/api/org/apache/struts/action/ActionForm.html">ActionForm</a>
[<code>org.apache.struts.action.ActionForm</code>]. The ActionForm class makes it
- easy to store <b>and validate</b> the data for your appplication's input forms.
+ easy to store <b>and validate</b> the data for your application's input forms.
The ActionForm bean is automatically saved in one of the standard, shared context
collections, so that it can be used by other objects, like an Action object or
another JSP.
@@ -343,7 +343,7 @@
<ul>
<li>The controller servlet either retrieves or creates the ActionForm bean instance.</li>
<li>The controller servlet passes the bean to the Action object.</li>
- <li>If the request is being used to to submit an input page, the Action object
+ <li>If the request is being used to submit an input page, the Action object
can examine the data. If necessary, the data can be sent back to the input
form along with a list of messages to display on the page. Otherwise the data can
be passed along to the business tier.</li>
@@ -359,10 +359,10 @@
</p>
<p>
Other Struts tags can automatically output messages queued by an Action
- or ActionForm and simply need to be intergrated into the page's markup.
+ or ActionForm and simply need to be integrated into the page's markup.
The messages are designed for
<a href="http://developer.java.sun.com/developer/technicalArticles/Intl/IntlIntro/">localization</a>
- and will render the best available mesage for a user's locale.
+ and will render the best available message for a user's locale.
</p>
<p>
1.16 +55 -55 jakarta-struts/doc/userGuide/preface.xml
Index: preface.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/preface.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- preface.xml 30 Nov 2002 14:30:27 -0000 1.15
+++ preface.xml 24 Dec 2002 01:50:07 -0000 1.16
@@ -206,16 +206,16 @@
<section name="0.5.3 DynaBeans" href="dynabeans">
<p>
- DynaBeans combine the extensibility of JavaBeans with the flexbility of a Map.
+ DynaBeans combine the extensibility of JavaBeans with the flexibility of a Map.
Defining even the simplest JavaBean requires defining a new class and coding a field and two methods for each property.
The properties of a DynaBean can be configured via an XML descriptor.
The virtual properties of a DynaBean can't be called by standard Java methods,
- but work well with components that rely on relfection and introspection.
+ but work well with components that rely on reflection and introspection.
</p>
<p>
In a Struts application, you can use DynaBeans to describe your HTML forms.
- This stategy can avoid creating a formal JavaBean subclass to store a few simple properties.
+ This strategy can avoid creating a formal JavaBean subclass to store a few simple properties.
</p>
<p>
@@ -336,27 +336,27 @@
<b>Web Applications</b></a> in the Java Web Services Tutorial.</li>
</ul>
- </section>
-
- <section name="0.7.1 Servlets and threads" href="threads">
-
- <p>
- To boost performance, the container can multi-thread servlets.
- Only one instance of a particular servlet is created,
- and each request for that servlet passes through the same object.
- This strategy helps the container make the best use of available resources.
- The tradeoff is that the servlet's <code>doGet()</code> and <code>doPost()</code> methods must be programmed in a <em>thread-safe</em> manner.
- </p>
-
- <p>
- For more about servlets and thread-safety, see:
- </p>
-
- <ul>
+ </section>
+
+ <section name="0.7.1 Servlets and threads" href="threads">
+
+ <p>
+ To boost performance, the container can multi-thread servlets.
+ Only one instance of a particular servlet is created,
+ and each request for that servlet passes through the same object.
+ This strategy helps the container make the best use of available resources.
+ The tradeoff is that the servlet's <code>doGet()</code> and <code>doPost()</code> methods must be programmed in a <em>thread-safe</em> manner.
+ </p>
+
+ <p>
+ For more about servlets and thread-safety, see:
+ </p>
+
+ <ul>
<li>
<a href="http://java.sun.com/webservices/docs/1.0/tutorial/doc/Servlets5.html#64386">Controlling Concurrent Access to Shared Resources</a> in JWST.
</li>
- </ul>
+ </ul>
</section>
@@ -383,15 +383,15 @@
</li>
</ul>
- <p>
- For more about the servlet context, see:
- </p>
-
- <ul>
+ <p>
+ For more about the servlet context, see:
+ </p>
+
+ <ul>
<li>
<a href="http://java.sun.com/webservices/docs/1.0/tutorial/doc/Servlets10.html#64724">Accessing the Web Context</a> in JWST.
</li>
- </ul>
+ </ul>
</section>
@@ -440,15 +440,15 @@
generally have to worry about the thread safety of your access to
request properties and attributes.</p>
- <p>
- For more about the servlet request, see:
- </p>
-
- <ul>
+ <p>
+ For more about the servlet request, see:
+ </p>
+
+ <ul>
<li>
<a href="http://java.sun.com/webservices/docs/1.0/tutorial/doc/Servlets7.html#64433">Getting Information from Requests</a> in JWST.
</li>
- </ul>
+ </ul>
</section>
@@ -496,18 +496,18 @@
<p>
Other presentation systems, like Velocity Tools for Struts,
- may delegate rendering the response to a specialized serlvet,
+ may delegate rendering the response to a specialized servlet,
but the same pattern holds true.
You create a template,
and the dynamic response is generated automatically from the template.
</p>
- <p>
- For more about the servlet response, see:
- </p>
-
- <ul>
- <li>
+ <p>
+ For more about the servlet response, see:
+ </p>
+
+ <ul>
+ <li>
<a href="http://java.sun.com/webservices/docs/1.0/tutorial/doc/Servlets7.html#64531">Constructing Responses</a> in JWST.
</li>
</ul>
@@ -538,11 +538,11 @@
For more about filters, see:
</p>
- <ul>
+ <ul>
<li>
<a href="http://java.sun.com/webservices/docs/1.0/tutorial/doc/Servlets8.html#64572">Filtering Requests and Responses</a>
- </li>
- </ul>
+ </li>
+ </ul>
</section>
@@ -592,9 +592,9 @@
For more about sessions, see:
</p>
<ul>
- <li>
- <a href="http://java.sun.com/webservices/docs/1.0/tutorial/doc/Servlets11.html#64744">Maintaining Client State</a> in JWST
- </li>
+ <li>
+ <a href="http://java.sun.com/webservices/docs/1.0/tutorial/doc/Servlets11.html#64744">Maintaining Client State</a> in JWST
+ </li>
<li>
<a href="http://java.sun.com/products/servlet/2.1/api/javax.servlet.http.HttpSession.html"><code>javax.servlet.http.HttpSession</code></a>
</li>
@@ -610,7 +610,7 @@
Struts uses this feature to pass a request through specialized components,
each handling one aspect of the response.
In the normal course, a request may pass through a controller object, a model object,
- and finaly to a view object as part of a single request/response cycle.
+ and finally to a view object as part of a single request/response cycle.
</p>
</section>
@@ -631,8 +631,8 @@
</p>
<ul>
<li>
- <a href="http://java.sun.com/webservices/docs/1.0/tutorial/doc/WebApp.html#76431">Web Applications</a> in JWST
- </li>
+ <a href="http://java.sun.com/webservices/docs/1.0/tutorial/doc/WebApp.html#76431">Web Applications</a> in JWST
+ </li>
</ul>
</section>
@@ -655,15 +655,15 @@
</section>
- <section name="0.7.10 Security" href="security">
+ <section name="0.7.10 Security" href="security">
<p>
One detail that can be configured in the Web application deployment descriptor is container-managed security.
Declarative security can be used to protect requests for URIs that match given patterns.
- Progmatic security can be used to fine-tune security make authorization decisions based on the time of day,
+ Pragmatic security can be used to fine-tune security make authorization decisions based on the time of day,
the parameters of a call, or the internal state of a Web component.
- It can also be used to restrict authentification based on information in a database.
- </p>
+ It can also be used to restrict authentication based on information in a database.
+ </p>
<p>For more information about container-managed security, see:</p>
<ul>
@@ -801,13 +801,13 @@
<section name="0.11 JAAS" href="jaas">
- <p>While Struts can work with any approach to user authentification and authorization, Struts 1.1 will offer
+ <p>While Struts can work with any approach to user authentication and authorization, Struts 1.1 will offer
direct support for the standard Java Authentication and Authorization Service (JAAS). In Struts 1.1 (and the
current nightly build), you can specify security roles on an action-by-action basis.</p>
<p>For more about JAAS, see the <a href="http://java.sun.com/products/jaas/index-14.html">Javasoft product page</a>
and the <a href="http://java.sun.com/webservices/docs/1.0/tutorial/doc/WebAppSecurity.html">
- Web Applicaton Security</a> chapter of the
+ Web Application Security</a> chapter of the
<a href="http://java.sun.com/webservices/docs/1.0/tutorial/index.html">Web Services Tutorial</a>.</p>
<p align="center">
1.2 +1 -1 jakarta-struts/doc/userGuide/release-notes-1.0-b1.xml
Index: release-notes-1.0-b1.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/release-notes-1.0-b1.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- release-notes-1.0-b1.xml 20 Feb 2002 00:41:14 -0000 1.1
+++ release-notes-1.0-b1.xml 24 Dec 2002 01:50:07 -0000 1.2
@@ -150,7 +150,7 @@
<li>A new <code><image></code> tag has been added, to create
HTML input tags of type "image".</li>
<li>The <code>form</code> tag has been enhanced to read its configuration from
- a corresponding action mapping entry in the"struts-config.xml" file,
+ a corresponding action mapping entry in the "struts-config.xml" file,
if the <code>name</code>, <code>scope</code>, and <code>type</code>
attributes are not specified. It can look up the name of the
form bean, its Java class, the scope in which the bean should be
1.2 +3 -3 jakarta-struts/doc/userGuide/release-notes-1.0-b2.xml
Index: release-notes-1.0-b2.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/release-notes-1.0-b2.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- release-notes-1.0-b2.xml 20 Feb 2002 00:41:14 -0000 1.1
+++ release-notes-1.0-b2.xml 24 Dec 2002 01:50:08 -0000 1.2
@@ -125,7 +125,7 @@
encapsulated as a servlet or JSP page, via use of two new standard
actions: <code>org.apache.struts.actions.ForwardAction</code> and
<code>org.apache.struts.actions.IncludeAction</code>. These actions
- let you take advantage of the standard processing perfomed by the
+ let you take advantage of the standard processing performed by the
controller servlet (including form bean population and calling the
<code>validate()</code> method), but not have to write Java code to
perform (or wrap) the required business logic.</li>
@@ -211,7 +211,7 @@
<li>Attribute getter methods have been added to all of the custom
tag implementation classes to facilitate reuse.</li>
<li>The <code><template:get></code> tag now has an optional
- "flush" attribute that causes the response to be commited prior
+ "flush" attribute that causes the response to be committed prior
to performing the include, if set to "true". This allows working
around problems on broken servlet containers.</li>
</ul>
@@ -246,7 +246,7 @@
message, making some problems difficult to track down.</li>
</ul>
- <p>The following changes and bug fixes have occured in the
+ <p>The following changes and bug fixes have occurred in the
<em>struts-html</em> custom tag library (package
<code>org.apache.struts.taglib.html</code>):</p>
<ul>
1.2 +1 -1 jakarta-struts/doc/userGuide/release-notes-1.0-b3.xml
Index: release-notes-1.0-b3.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/release-notes-1.0-b3.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- release-notes-1.0-b3.xml 20 Feb 2002 00:41:14 -0000 1.1
+++ release-notes-1.0-b3.xml 24 Dec 2002 01:50:08 -0000 1.2
@@ -222,7 +222,7 @@
contain more than one name/value pair.</li>
</ul>
- <p>The following changes and bug fixes have occured in the
+ <p>The following changes and bug fixes have occurred in the
<em>struts-html</em> custom tag library (package
<code>org.apache.struts.taglib.html</code>):</p>
<ul>
1.2 +2 -2 jakarta-struts/doc/userGuide/release-notes-1.0.1.xml
Index: release-notes-1.0.1.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/release-notes-1.0.1.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- release-notes-1.0.1.xml 20 Feb 2002 00:41:14 -0000 1.1
+++ release-notes-1.0.1.xml 24 Dec 2002 01:50:08 -0000 1.2
@@ -156,14 +156,14 @@
<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
+ <p>The following changes and bug fixes have occurred in the
<em>struts-bean</em> custom tag library (package
<code>org.apache.struts.taglib.bean</code>):</p>
<ul>
<li>Correct the generated scripting variable type when the <bean:cookie>, <bean:header>, or <bean:parameter> tag is used with the "multiple" attribute.</li>
</ul>
- <p>The following changes and bug fixes have occured in the
+ <p>The following changes and bug fixes have occurred in the
<em>struts-html</em> custom tag library (package
<code>org.apache.struts.taglib.html</code>):</p>
<ul>
1.2 +2 -2 jakarta-struts/doc/userGuide/release-notes-1.0.xml
Index: release-notes-1.0.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/release-notes-1.0.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- release-notes-1.0.xml 20 Feb 2002 00:41:14 -0000 1.1
+++ release-notes-1.0.xml 24 Dec 2002 01:50:08 -0000 1.2
@@ -221,7 +221,7 @@
path in <code>RequestUtils.absoluteURL()</code>.</li>
</ul>
- <p>The following changes and bug fixes have occured in the
+ <p>The following changes and bug fixes have occurred in the
<em>struts-bean</em> custom tag library (package
<code>org.apache.struts.taglib.bean</code>):</p>
<ul>
@@ -232,7 +232,7 @@
were using URL rewriting.</li>
</ul>
- <p>The following changes and bug fixes have occured in the
+ <p>The following changes and bug fixes have occurred in the
<em>struts-html</em> custom tag library (package
<code>org.apache.struts.taglib.html</code>):</p>
<ul>
1.4 +5 -5 jakarta-struts/doc/userGuide/release-notes-1.1-b1.xml
Index: release-notes-1.1-b1.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/release-notes-1.1-b1.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- release-notes-1.1-b1.xml 26 Jun 2002 23:36:11 -0000 1.3
+++ release-notes-1.1-b1.xml 24 Dec 2002 01:50:08 -0000 1.4
@@ -43,7 +43,7 @@
<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
+ copied into the <code>/WEB-INF/lib</code> directory of
your web application.</li>
<li><code>struts.jar</code> - JAR file that contains the compiled
Java classes of Struts. You must
@@ -266,7 +266,7 @@
<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
+ <p>The following changes and bug fixes have occurred in the
<em>struts-bean</em> custom tag library (package
<code>org.apache.struts.taglib.bean</code>):</p>
<ul>
@@ -279,7 +279,7 @@
"private".</li>
</ul>
- <p>The following changes and bug fixes have occured in the
+ <p>The following changes and bug fixes have occurred in the
<em>struts-html</em> custom tag library (package
<code>org.apache.struts.taglib.html</code>):</p>
<ul>
@@ -315,7 +315,7 @@
<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>Add Russian 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>
@@ -326,7 +326,7 @@
<li>None.</li>
</ul>
- <p>The following changes and bug fixes to the Struts Excercise Taglib Example
+ <p>The following changes and bug fixes to the Struts Exercise Taglib Example
Application have occurred:</p>
<ul>
<li>Added test case for <html:select> using <html:options> based on a collection
1.5 +8 -8 jakarta-struts/doc/userGuide/release-notes-1.1-b2.xml
Index: release-notes-1.1-b2.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/release-notes-1.1-b2.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- release-notes-1.1-b2.xml 18 Oct 2002 15:27:42 -0000 1.4
+++ release-notes-1.1-b2.xml 24 Dec 2002 01:50:08 -0000 1.5
@@ -44,7 +44,7 @@
<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
+ copied into the <code>/WEB-INF/lib</code> directory of
your web application.</li>
<li><code>struts.jar</code> - JAR file that contains the compiled
Java classes of Struts. You must
@@ -149,7 +149,7 @@
(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>SOURCE DEVELOPERS NOTE! Ant Prerequiste Updated</strong></p>
+ <p><strong>SOURCE DEVELOPERS NOTE! Ant Prerequisite Updated</strong></p>
<p>To build Struts from source Ant 1.4 or later is now required. This
does not affect developers that use Struts from the binary distribution.</p>
@@ -168,7 +168,7 @@
<p>New example applications for the Validator and Tiles are now part
of the Struts distribution.</p>
- <p><strong>New Contrib directory for optional compoonents</strong></p>
+ <p><strong>New Contrib directory for optional components</strong></p>
<p>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>
@@ -220,7 +220,7 @@
<em>struts-bean</em> custom tag library
[<code>org.apache.struts.taglib.bean</code>]:</p>
<ul>
- <li><code><bean:write></code>: Add format, locale and bundle attributes to to support formatting values according to current
+ <li><code><bean:write></code>: Add format, locale and bundle attributes to support formatting values according to current
user locale, format string from attribute or format string from string resources.</li>
<li><code><bean:cookie>, <bean:header>, or <bean:parameter>:</code> Correct the generated scripting variable type when tag is used with the "multiple" attribute.</li>
<li><code><bean:message>:</code> Added <code>name</code>, <code>property</code>, and <code>scope</code> attributes to the tag, so that the message source key can be obtained dynamically from a bean or bean property.</li>
@@ -273,7 +273,7 @@
<li>Kickstart FAQ: The questions most likely to be asked when selecting Struts.</li>
<li>1.0 JavaDoc: Added archival copy to web site for future reference.</li>
<li>The UserGuide "Building" pages: General revisions to reflect new features and current practices.</li>
- <li>Installation: Upated instructions for SilverStream and Resin. Add installation notes for Jetty. Added RexIP to list of nominal containers.</li>
+ <li>Installation: Updated instructions for SilverStream and Resin. Add installation notes for Jetty. Added RexIP to list of nominal containers.</li>
<li>JavaDocs: New <code>@since Struts 1.1</code> tag to indicate new packages, classes, and members added after the Struts 1.0.x version</li>
</ul>
@@ -347,7 +347,7 @@
</ul>
<p><strong>Bean Taglib Package Changes</strong></p>
- <p>The following changes and bug fixes have occured in the
+ <p>The following changes and bug fixes have occurred in the
<em>struts-bean</em> custom tag library
[<code>org.apache.struts.taglib.bean</code>]:</p>
<ul>
@@ -361,7 +361,7 @@
</ul>
<p><strong>HTML Taglib Package Changes</strong></p>
- <p>The following changes and bug fixes have occured in the
+ <p>The following changes and bug fixes have occurred in the
<em>struts-html</em> custom tag library (package
<code>org.apache.struts.taglib.html</code>):</p>
<ul>
@@ -408,7 +408,7 @@
</ul>
<p><strong>Exercise Taglib Example Application Changes</strong></p>
- <p>The following changes and bug fixes to the Struts Excercise Taglib Example
+ <p>The following changes and bug fixes to the Struts Exercise Taglib Example
Application have occurred:</p>
<ul>
<li>Added test case for <html:select> using <html:options> based on a collection
1.15 +8 -8 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.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- release-notes.xml 22 Dec 2002 01:25:33 -0000 1.14
+++ release-notes.xml 24 Dec 2002 01:50:08 -0000 1.15
@@ -62,7 +62,7 @@
<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
+ copied into the <code>/WEB-INF/lib</code> directory of
your web application.</li>
<li><code>struts.jar</code> - JAR file that contains the compiled
Java classes of Struts. You must
@@ -165,7 +165,7 @@
(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>SOURCE DEVELOPERS NOTE! Ant Prerequiste Updated</strong></p>
+ <p><strong>SOURCE DEVELOPERS NOTE! Ant Prerequisite Updated</strong></p>
<p>To build Struts from source Ant 1.4 or later is now required. This
does not affect developers that use Struts from the binary distribution.</p>
@@ -184,7 +184,7 @@
<p>New example applications for the Validator and Tiles are now part
of the Struts distribution.</p>
- <p><strong>New Contrib directory for optional compoonents</strong></p>
+ <p><strong>New Contrib directory for optional components</strong></p>
<p>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>
@@ -236,7 +236,7 @@
<em>struts-bean</em> custom tag library
[<code>org.apache.struts.taglib.bean</code>]:</p>
<ul>
- <li><code><bean:write></code>: Add format, locale and bundle attributes to to support formatting values according to current
+ <li><code><bean:write></code>: Add format, locale and bundle attributes to support formatting values according to current
user locale, format string from attribute or format string from string resources.</li>
<li><code><bean:cookie>, <bean:header>, or <bean:parameter>:</code> Correct the generated scripting variable type when tag is used with the "multiple" attribute.</li>
<li><code><bean:message>:</code> Added <code>name</code>, <code>property</code>, and <code>scope</code> attributes to the tag, so that the message source key can be obtained dynamically from a bean or bean property.</li>
@@ -289,7 +289,7 @@
<li>Kickstart FAQ: The questions most likely to be asked when selecting Struts.</li>
<li>1.0 JavaDoc: Added archival copy to web site for future reference.</li>
<li>The UserGuide "Building" pages: General revisions to reflect new features and current practices.</li>
- <li>Installation: Upated instructions for SilverStream and Resin. Add installation notes for Jetty. Added RexIP to list of nominal containers.</li>
+ <li>Installation: Updated instructions for SilverStream and Resin. Add installation notes for Jetty. Added RexIP to list of nominal containers.</li>
<li>JavaDocs: New <code>@since Struts 1.1</code> tag to indicate new packages, classes, and members added after the Struts 1.0.x version</li>
</ul>
@@ -363,7 +363,7 @@
</ul>
<p><strong>Bean Taglib Package Changes</strong></p>
- <p>The following changes and bug fixes have occured in the
+ <p>The following changes and bug fixes have occurred in the
<em>struts-bean</em> custom tag library
[<code>org.apache.struts.taglib.bean</code>]:</p>
<ul>
@@ -377,7 +377,7 @@
</ul>
<p><strong>HTML Taglib Package Changes</strong></p>
- <p>The following changes and bug fixes have occured in the
+ <p>The following changes and bug fixes have occurred in the
<em>struts-html</em> custom tag library (package
<code>org.apache.struts.taglib.html</code>):</p>
<ul>
@@ -424,7 +424,7 @@
</ul>
<p><strong>Exercise Taglib Example Application Changes</strong></p>
- <p>The following changes and bug fixes to the Struts Excercise Taglib Example
+ <p>The following changes and bug fixes to the Struts Exercise Taglib Example
Application have occurred:</p>
<ul>
<li>Added test case for <html:select> using <html:options> based on a collection
1.10 +2 -2 jakarta-struts/doc/userGuide/struts-logic.xml
Index: struts-logic.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/struts-logic.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- struts-logic.xml 20 Nov 2002 04:29:26 -0000 1.9
+++ struts-logic.xml 24 Dec 2002 01:50:08 -0000 1.10
@@ -1491,7 +1491,7 @@
<li><em>href</em> - Use the value of this attribute unchanged.
</li>
<li><em>page</em> - Use the value of this attribute as an
- applicaiton-relative URI, and generate a server-relative
+ application-relative URI, and generate a server-relative
URI by including the context path.</li>
</ul>
@@ -1628,7 +1628,7 @@
added to the generated hyperlink. The corresponding value is
defined by the <code>paramName</code> and (optional)
<code>paramProperty</code> attributes, optionally scoped by
- the <code>paramScope</code> attributel</p>
+ the <code>paramScope</code> attribute</p>
</info>
</attribute>
1.14 +3 -3 jakarta-struts/doc/userGuide/struts-nested.xml
Index: struts-nested.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/struts-nested.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- struts-nested.xml 20 Nov 2002 04:29:26 -0000 1.13
+++ struts-nested.xml 24 Dec 2002 01:50:08 -0000 1.14
@@ -143,7 +143,7 @@
<required>false</required>
<rtexprvalue>true</rtexprvalue>
<info>
- true/false vaule, describing to the tag if the result if to be URLEncoded.
+ true/false value, describing to the tag if the result if to be URLEncoded.
Helps JavaScript along if the result is required for URL hacking.
</info>
</attribute>
@@ -171,7 +171,7 @@
need to provide their logic.
</p>
<p>
- <strong>Note</strong>: The acess to a bean via the <code>name</code>
+ <strong>Note</strong>: The access to a bean via the <code>name</code>
attribute takes priority over looking for the reference from other
parent tags. So if a name is specified, a bean will have to be there
waiting for it. It was made this way so that you could use separate
@@ -1947,7 +1947,7 @@
<strong>Note:</strong> The nested context of this tag relies on the use
of the "property" property, and the internal use of the "name" property.
The nested tags rely on these properties and will attempt to set them
- iteself. The <code><html:options></code> tag this tag extendeds
+ itself. The <code><html:options></code> tag this tag extended
allows other options for the tag which don't use these properties.
To take advantage of these options, markup using the
<code><html:options></code> tag instead of the nested tag.
1.6 +267 -267 jakarta-struts/doc/userGuide/struts-tiles.xml
Index: struts-tiles.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/struts-tiles.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- struts-tiles.xml 20 Nov 2002 04:29:26 -0000 1.5
+++ struts-tiles.xml 24 Dec 2002 01:50:08 -0000 1.6
@@ -20,13 +20,13 @@
<uri>http://jakarta.apache.org/struts/tags-tiles</uri>
<info>
This tag library provides tiles tags.
- <br></br>
- <br></br>
- Tiles were previously called Components. For historical reasons, names, pages, components and templates
- are used indifferently to design a tile. Also, a lot of tags and attribute names are
- left for backward compatibility.
- <br></br>To know more about tags defined in this library, check the associated documentation:
- tiles-doc.
+ <br></br>
+ <br></br>
+ Tiles were previously called Components. For historical reasons, names, pages, components and templates
+ are used indifferently to design a tile. Also, a lot of tags and attribute names are
+ left for backward compatibility.
+ <br></br>To know more about tags defined in this library, check the associated documentation:
+ tiles-doc.
</info>
<!-- ===================== Include Tags ====================== -->
@@ -36,34 +36,34 @@
<summary>
Insert a tiles/component/template.
</summary>
- <info>
- Insert a tiles/component/template with the possibility to pass parameters
- (called attribute).
- A tile can be seen as a procedure that can take parameters or attributes.
- <code><template:insert></code> allows to define these attributes and pass them to the inserted jsp page,
- called template.
- Attributes are defined using nested tag <code><template:put></code> or
- <code><template:putList></code>.
- <br></br>
+ <info>
+ Insert a tiles/component/template with the possibility to pass parameters
+ (called attribute).
+ A tile can be seen as a procedure that can take parameters or attributes.
+ <code><template:insert></code> allows to define these attributes and pass them to the inserted jsp page,
+ called template.
+ Attributes are defined using nested tag <code><template:put></code> or
+ <code><template:putList></code>.
+ <br></br>
You must specify one of this tag attribute :
- <ul>
- <li><code>template</code>, for inserting a tiles/component/template page,</li>
- <li><code>component</code>, for inserting a tiles/component/template page, (same as template)</li>
- <li><code>page</code> for inserting a JSP page, (same as template)</li>
- <li><code>definition</code>, for inserting a definition from definitons factory</li>
- <li><code>attribute</code>, surrounding tiles's attribute name whose value is used.
- <br>If attribute is associated to 'direct' flag (see put), and flag is true, write
- attribute value (no insertion).
- </br></li>
- <li><code>name</code>, to let 'insert' determine the type of entities to insert. In this later
- case, search is done in this order : definitions, tiles/components/templates, pages.
- </li>
- </ul>
- <br></br>
- In fact, Page, component and template, are equivalent as a tile, component or template are jsp page.
- <br></br>
- <STRONG>Example : </STRONG>
- <pre><code>
+ <ul>
+ <li><code>template</code>, for inserting a tiles/component/template page,</li>
+ <li><code>component</code>, for inserting a tiles/component/template page, (same as template)</li>
+ <li><code>page</code> for inserting a JSP page, (same as template)</li>
+ <li><code>definition</code>, for inserting a definition from definitions factory</li>
+ <li><code>attribute</code>, surrounding tiles's attribute name whose value is used.
+ <br>If attribute is associated to 'direct' flag (see put), and flag is true, write
+ attribute value (no insertion).
+ </br></li>
+ <li><code>name</code>, to let 'insert' determine the type of entities to insert. In this later
+ case, search is done in this order : definitions, tiles/components/templates, pages.
+ </li>
+ </ul>
+ <br></br>
+ In fact, Page, component and template, are equivalent as a tile, component or template are jsp page.
+ <br></br>
+ <STRONG>Example : </STRONG>
+ <pre><code>
<template:insert page="/basic/myLayout.jsp" flush="true">
<template:put name="title" value="My first page" />
<template:put name="header" value="/common/header.jsp" />
@@ -71,7 +71,7 @@
<template:put name="menu" value="/basic/menu.jsp" />
<template:put name="body" value="/basic/helloBody.jsp" />
</template:insert></code></pre>
- </info>
+ </info>
<tagclass>org.apache.struts.taglib.tiles.InsertTag</tagclass>
<bodycontent>JSP</bodycontent>
@@ -81,7 +81,7 @@
<rtexprvalue>true</rtexprvalue>
<info>
A string representing the URI of a tile or template (a JSP page).
- <br></br>'page', 'component' and 'template' are synonyms : they have exactly the same behavior.
+ <br></br>'page', 'component' and 'template' are synonyms : they have exactly the same behavior.
</info>
</attribute>
@@ -89,51 +89,51 @@
<name>component</name>
<required>false</required>
<rtexprvalue>true</rtexprvalue>
- <info>
- Path (relative or absolute to webapps) of the component to insert.
- <br></br>'page', 'component' and 'template' are synonyms : they have exactly the same behavior.
- </info>
+ <info>
+ Path (relative or absolute to webapps) of the component to insert.
+ <br></br>'page', 'component' and 'template' are synonyms : they have exactly the same behavior.
+ </info>
</attribute>
<attribute>
<name>page</name>
<required>false</required>
<rtexprvalue>true</rtexprvalue>
- <info>
- Path (relative or absolute to webapps) of the page to insert.
- <br></br>'page', 'component' and 'template' are synonyms : they have exactly the same behavior.
- </info>
+ <info>
+ Path (relative or absolute to webapps) of the page to insert.
+ <br></br>'page', 'component' and 'template' are synonyms : they have exactly the same behavior.
+ </info>
</attribute>
<attribute>
- <name>definition</name>
- <required>false</required>
- <rtexprvalue>true</rtexprvalue>
- <info>
- Name of the definition to insert. Definition are defined in a centralized file.
- For now, only definition from factory can be inserted with this attribute.
- To insert a definiton defined with tag <template:definition>, use beanName="".
- </info>
+ <name>definition</name>
+ <required>false</required>
+ <rtexprvalue>true</rtexprvalue>
+ <info>
+ Name of the definition to insert. Definition are defined in a centralized file.
+ For now, only definition from factory can be inserted with this attribute.
+ To insert a definition defined with tag <template:definition>, use beanName="".
+ </info>
</attribute>
<attribute>
<name>attribute</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
- <info>
- Name of an attribute in current tile/component context. Value of this attribute is passed to
- 'name' (see attribute 'name').
- </info>
+ <info>
+ Name of an attribute in current tile/component context. Value of this attribute is passed to
+ 'name' (see attribute 'name').
+ </info>
</attribute>
<attribute>
<name>name</name>
<required>false</required>
<rtexprvalue>true</rtexprvalue>
- <info>
- Name of an entity to insert. Search is done in this order : definition, attribute,
- [tile/component/template/page].
- </info>
+ <info>
+ Name of an entity to insert. Search is done in this order : definition, attribute,
+ [tile/component/template/page].
+ </info>
</attribute>
<attribute>
@@ -142,11 +142,11 @@
<rtexprvalue>true</rtexprvalue>
<info>
Name of the bean used as value. Bean is retrieved from specified context, if any. Otherwise,
- method pageContext.findAttribute is used.
- If beanProperty is also specified, retrieve value from the corresponding bean property.
- <br></br>If found bean (or property value) is instance of one of Attribute class (Direct,
- Instance, ...), insertion is done according to the class type. Otherwise, the toString method is
- called on the bean, and returned String is used as name to insert (see 'name' attribute).
+ method pageContext.findAttribute is used.
+ If beanProperty is also specified, retrieve value from the corresponding bean property.
+ <br></br>If found bean (or property value) is instance of one of Attribute class (Direct,
+ Instance, ...), insertion is done according to the class type. Otherwise, the toString method is
+ called on the bean, and returned String is used as name to insert (see 'name' attribute).
</info>
</attribute>
@@ -156,7 +156,7 @@
<rtexprvalue>true</rtexprvalue>
<info>
Bean property name. If specified, value is retrieve from this property. Support nested/indexed
- properties.
+ properties.
</info>
</attribute>
@@ -166,8 +166,8 @@
<rtexprvalue>false</rtexprvalue>
<info>
Scope into which bean is searched. If not specified, method pageContext.findAttribute is used.
- Scope can be any JSP scope, 'component', or 'template'.
- In these two later cases, bean is search in tile/component/template context.
+ Scope can be any JSP scope, 'component', or 'template'.
+ In these two later cases, bean is search in tile/component/template context.
</info>
</attribute>
@@ -175,9 +175,9 @@
<name>flush</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
- <info>
- True or false. If true, current page out stream is flushed before insertion.
- </info>
+ <info>
+ True or false. If true, current page out stream is flushed before insertion.
+ </info>
</attribute>
<attribute>
@@ -186,8 +186,8 @@
<rtexprvalue>true</rtexprvalue>
<info>
If this attribute is set to true, and the attribute specified by the name
- does not exist, simply return without writing anything. The default value is false, which will
- cause a runtime exception to be thrown.
+ does not exist, simply return without writing anything. The default value is false, which will
+ cause a runtime exception to be thrown.
</info>
</attribute>
@@ -197,7 +197,7 @@
<rtexprvalue>true</rtexprvalue>
<info>
If the user is in the specified role, the tag is taken into account;
- otherwise, the tag is ignored (skipped).
+ otherwise, the tag is ignored (skipped).
</info>
</attribute>
@@ -207,10 +207,10 @@
<rtexprvalue>true</rtexprvalue>
<info>
Url of a controller called immediately before page is inserted.<br></br>
- Url usually denote a Struts action. Controller (action) is used to prepare data
- to be render by inserted Tile.
- <br></br>
- See also controlerClass. Only one of controllerUrl or controllerClass should be used.
+ Url usually denote a Struts action. Controller (action) is used to prepare data
+ to be render by inserted Tile.
+ <br></br>
+ See also controlerClass. Only one of controllerUrl or controllerClass should be used.
</info>
</attribute>
@@ -220,18 +220,18 @@
<rtexprvalue>true</rtexprvalue>
<info>
Class type of a controller called immediately before page is inserted.<br></br>
- Controller is used to prepare data to be render by inserted Tile.
- <br></br>
- See also controlerUrl
- <br></br>
- Class must implements or extends one of the following :
- <ul>
- <li>org.apache.struts.tiles.Controller</li>
- <li>org.apache.struts.tiles.ControllerSupport</li>
- <li>org.apache.struts.action.Action (wrapper org.apache.struts.action.ActionController is used)</li>
- </ul>
- <br></br>
- See also controllerUrl. Only one of controllerUrl or controllerClass should be used.
+ Controller is used to prepare data to be render by inserted Tile.
+ <br></br>
+ See also controlerUrl
+ <br></br>
+ Class must implements or extends one of the following :
+ <ul>
+ <li>org.apache.struts.tiles.Controller</li>
+ <li>org.apache.struts.tiles.ControllerSupport</li>
+ <li>org.apache.struts.action.Action (wrapper org.apache.struts.action.ActionController is used)</li>
+ </ul>
+ <br></br>
+ See also controllerUrl. Only one of controllerUrl or controllerClass should be used.
</info>
</attribute>
@@ -242,70 +242,70 @@
<summary>
Create a tile /component / template definition bean.
</summary>
- <info>
- Create a tile/component/template definition as a bean.
- Newly created bean will be saved under specified "id", in the requested "scope".
- Definition tag has same syntax as <code>insert</code> tag.
- The new definition can extends a definition described in factory (XML file), and overload
- any previously defined parameters.
- </info>
+ <info>
+ Create a tile/component/template definition as a bean.
+ Newly created bean will be saved under specified "id", in the requested "scope".
+ Definition tag has same syntax as <code>insert</code> tag.
+ The new definition can extends a definition described in factory (XML file), and overload
+ any previously defined parameters.
+ </info>
<tagclass>org.apache.struts.taglib.tiles.DefinitionTag</tagclass>
- <bodycontent>JSP</bodycontent>
+ <bodycontent>JSP</bodycontent>
- <attribute>
- <name>id</name>
- <required>true</required>
- <rtexprvalue>false</rtexprvalue>
- <info>
+ <attribute>
+ <name>id</name>
+ <required>true</required>
+ <rtexprvalue>false</rtexprvalue>
+ <info>
Specifies the name under which the newly created definition bean will be saved.
</info>
</attribute>
<attribute>
<name>scope</name>
- <required>false</required>
- <rtexprvalue>false</rtexprvalue>
- <info>
+ <required>false</required>
+ <rtexprvalue>false</rtexprvalue>
+ <info>
Specifies the variable scope into which the newly defined bean will be created.
- If not specified, the bean will be created in page scope.
+ If not specified, the bean will be created in page scope.
</info>
</attribute>
<attribute>
- <name>template</name>
- <required>false</required>
- <rtexprvalue>true</rtexprvalue>
- <info>
+ <name>template</name>
+ <required>false</required>
+ <rtexprvalue>true</rtexprvalue>
+ <info>
A string representing the URI of a tile/component/template (a JSP page).
</info>
</attribute>
<attribute>
- <name>page</name>
- <required>false</required>
- <rtexprvalue>true</rtexprvalue>
- <info>
+ <name>page</name>
+ <required>false</required>
+ <rtexprvalue>true</rtexprvalue>
+ <info>
URL of the template / component to insert. Same as "template".
</info>
</attribute>
<attribute>
- <name>role</name>
- <required>false</required>
- <rtexprvalue>true</rtexprvalue>
- <info>
+ <name>role</name>
+ <required>false</required>
+ <rtexprvalue>true</rtexprvalue>
+ <info>
Role to check before inserting this definition. If role is not defined for current user,
- definition is not inserted. Checking is done at insert time, not during definition process.
+ definition is not inserted. Checking is done at insert time, not during definition process.
</info>
</attribute>
<attribute>
- <name>extends</name>
- <required>false</required>
- <rtexprvalue>true</rtexprvalue>
- <info>
+ <name>extends</name>
+ <required>false</required>
+ <rtexprvalue>true</rtexprvalue>
+ <info>
Name of a parent definition that is used to initialize this new definition.
- Parent definition is searched in definitions factory.
+ Parent definition is searched in definitions factory.
</info>
</attribute>
@@ -316,20 +316,20 @@
<summary>
Put an attribute into tile/component/template context.
</summary>
- <info>
- Define an attribute to pass to tile/component/template.
- This tag can only be used inside 'insert' or 'definition' tag.
- Value (or content) is specified using attribute 'value' (or 'content'), or using the tag body.
- It is also possible to specify the type of the value :
+ <info>
+ Define an attribute to pass to tile/component/template.
+ This tag can only be used inside 'insert' or 'definition' tag.
+ Value (or content) is specified using attribute 'value' (or 'content'), or using the tag body.
+ It is also possible to specify the type of the value :
<ul>
- <li>string : Content is writed directly.</li>
- <li>page | template : Content is included from specified URL. Name is used as an URL.</li>
- <li>definition : Content come from specified definition (from factory). Name is used as definition name.</li>
- </ul>
- If type is specified, it is taken into account by 'get' or 'insert' inside the inserted tile.
+ <li>string : Content is written directly.</li>
+ <li>page | template : Content is included from specified URL. Name is used as an URL.</li>
+ <li>definition : Content come from specified definition (from factory). Name is used as definition name.</li>
+ </ul>
+ If type is specified, it is taken into account by 'get' or 'insert' inside the inserted tile.
<br></br>If 'type' attribute is not specified, content is 'untyped', unless it comes from a typed bean.
- <br></br>Note that using 'direct="true"' is equivalent to 'type="string"'.
- </info>
+ <br></br>Note that using 'direct="true"' is equivalent to 'type="string"'.
+ </info>
<tagclass>org.apache.struts.taglib.tiles.PutTag</tagclass>
<bodycontent>JSP</bodycontent>
@@ -337,20 +337,20 @@
<name>name</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
- <info>
- Name of the attribute.
- </info>
+ <info>
+ Name of the attribute.
+ </info>
</attribute>
<attribute>
<name>value</name>
<required>false</required>
<rtexprvalue>true</rtexprvalue>
- <info>
- Attribute value. Could be a String or an Object.
- Value can come from a direct assignement (value="aValue") or from a bean.
- One of 'value' 'content' or 'beanName' must be present.
- </info>
+ <info>
+ Attribute value. Could be a String or an Object.
+ Value can come from a direct assignment (value="aValue") or from a bean.
+ One of 'value' 'content' or 'beanName' must be present.
+ </info>
</attribute>
<attribute>
@@ -359,7 +359,7 @@
<rtexprvalue>true</rtexprvalue>
<info>
Content that's put into tile scope.
- Synonym to value. Attribute added for compatibility with JSP Template.
+ Synonym to value. Attribute added for compatibility with JSP Template.
</info>
</attribute>
@@ -371,9 +371,9 @@
Determines how content is handled: true means content is
printed <i>direct</i>ly; false, the default, means content
is included.
- This is another way to specify content type. If 'direct=true' content is 'string', if
- 'direct=false', content is 'page'.
- Attribute added for compatibility with JSP Template.
+ This is another way to specify content type. If 'direct=true' content is 'string', if
+ 'direct=false', content is 'page'.
+ Attribute added for compatibility with JSP Template.
</info>
</attribute>
@@ -384,12 +384,12 @@
<info>
Specify content type: string, page, template or definition.
<ul>
- <li>String : Content is printed directly.</li>
- <li>page | template : Content is included from specified URL. Name is used as an URL.</li>
- <li>definition : Value is the name of a definition defined in factory (xml file). Definition will be searched
- in the inserted tile, in a <code><template:insert attribute="attributeName"></code> tag, where 'attributeName'
- is the name used for this tag.</li>
- </ul>
+ <li>String : Content is printed directly.</li>
+ <li>page | template : Content is included from specified URL. Name is used as an URL.</li>
+ <li>definition : Value is the name of a definition defined in factory (xml file). Definition will be searched
+ in the inserted tile, in a <code><template:insert attribute="attributeName"></code> tag, where 'attributeName'
+ is the name used for this tag.</li>
+ </ul>
If 'type' attribute is not specified, content is 'untyped', unless it comes from a typed bean.
</info>
</attribute>
@@ -400,8 +400,8 @@
<rtexprvalue>true</rtexprvalue>
<info>
Name of the bean used as value. Bean is retrieved from specified context, if any. Otherwise,
- method pageContext.findAttribute is used.
- If beanProperty is specified, retrieve value from the corresponding bean property.
+ method pageContext.findAttribute is used.
+ If beanProperty is specified, retrieve value from the corresponding bean property.
</info>
</attribute>
@@ -411,7 +411,7 @@
<rtexprvalue>true</rtexprvalue>
<info>
Bean property name. If specified, value is retrieve from this property. Support nested/indexed
- properties.
+ properties.
</info>
</attribute>
@@ -421,8 +421,8 @@
<rtexprvalue>false</rtexprvalue>
<info>
Scope into which bean is searched. If not specified, method pageContext.findAttribute is used.
- Scope can be any JSP scope, 'tile', 'component', or 'template'.
- In these three later cases, bean is search in tile/component/template context.
+ Scope can be any JSP scope, 'tile', 'component', or 'template'.
+ In these three later cases, bean is search in tile/component/template context.
</info>
</attribute>
@@ -432,7 +432,7 @@
<rtexprvalue>true</rtexprvalue>
<info>
If the user is in the specified role, the tag is taken into account;
- otherwise, the tag is ignored (skipped).
+ otherwise, the tag is ignored (skipped).
</info>
</attribute>
@@ -441,13 +441,13 @@
<tag>
<name>putList</name>
<summary>
- Declare a list that will be pass as attribute to tile.
+ Declare a list that will be pass as attribute to tile.
</summary>
- <info>
- Declare a list that will be pass as attribute to tile.
- List elements are added using the tag 'add'.
- This tag can only be used inside 'insert' or 'definition' tag.
- </info>
+ <info>
+ Declare a list that will be pass as attribute to tile.
+ List elements are added using the tag 'add'.
+ This tag can only be used inside 'insert' or 'definition' tag.
+ </info>
<tagclass>org.apache.struts.taglib.tiles.PutListTag</tagclass>
<bodycontent>JSP</bodycontent>
@@ -455,9 +455,9 @@
<name>name</name>
<required>true</required>
<rtexprvalue>false</rtexprvalue>
- <info>
- Name of the list.
- </info>
+ <info>
+ Name of the list.
+ </info>
</attribute>
</tag>
@@ -465,14 +465,14 @@
<name>add</name>
<summary>
Add an element to the surrounding list.
- Equivalent to 'put', but for list element.
+ Equivalent to 'put', but for list element.
</summary>
- <info>
+ <info>
Add an element to the surrounding list.
- This tag can only be used inside putList tag.
- Value can come from a direct assignement (value="aValue") or from a bean.
- One of 'value' or 'beanName' must be present.
- </info>
+ This tag can only be used inside putList tag.
+ Value can come from a direct assignment (value="aValue") or from a bean.
+ One of 'value' or 'beanName' must be present.
+ </info>
<tagclass>org.apache.struts.taglib.tiles.AddTag</tagclass>
<bodycontent>JSP</bodycontent>
@@ -480,9 +480,9 @@
<name>value</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
- <info>
- Element value. Can be a String or Object.
- </info>
+ <info>
+ Element value. Can be a String or Object.
+ </info>
</attribute>
<attribute>
@@ -491,7 +491,7 @@
<rtexprvalue>true</rtexprvalue>
<info>
Element value. Can be a String or Object.
- Synonym to value. Attribute added for compatibility with JSP Template.
+ Synonym to value. Attribute added for compatibility with JSP Template.
</info>
</attribute>
@@ -503,9 +503,9 @@
Determines how content is handled: true means content is
printed <i>direct</i>ly; false, the default, means content
is included.
- This is another way to specify content type. If 'direct=true' content is 'string', if
- 'direct=false', content is 'page'.
- Attribute added for compatibility with JSP Template.
+ This is another way to specify content type. If 'direct=true' content is 'string', if
+ 'direct=false', content is 'page'.
+ Attribute added for compatibility with JSP Template.
</info>
</attribute>
@@ -516,12 +516,12 @@
<info>
Specify content type: string, page, template or instance.
<ul>
- <li>String : Content is printed directly.</li>
- <li>page | template : Content is included from specified URL. Name is used as an URL.</li>
- <li>definition : Value denote a definition defined in factory (xml file). Definition will be searched
- in the inserted tile, in a <code><insert attribute="attributeName"></code> tag, where 'attributeName'
- is the name used for this tag.</li>
- </ul>
+ <li>String : Content is printed directly.</li>
+ <li>page | template : Content is included from specified URL. Name is used as an URL.</li>
+ <li>definition : Value denote a definition defined in factory (xml file). Definition will be searched
+ in the inserted tile, in a <code><insert attribute="attributeName"></code> tag, where 'attributeName'
+ is the name used for this tag.</li>
+ </ul>
If 'type' attribute is not specified, content is 'untyped', unless it comes from a typed bean.
</info>
</attribute>
@@ -532,8 +532,8 @@
<rtexprvalue>true</rtexprvalue>
<info>
Name of the bean used as value. Bean is retrieved from specified context, if any. Otherwise,
- method pageContext.findAttribute is used.
- If beanProperty is specified, retrieve value from the corresponding bean property.
+ method pageContext.findAttribute is used.
+ If beanProperty is specified, retrieve value from the corresponding bean property.
</info>
</attribute>
@@ -543,7 +543,7 @@
<rtexprvalue>true</rtexprvalue>
<info>
Bean property name. If specified, value is retrieve from this property. Support nested/indexed
- properties.
+ properties.
</info>
</attribute>
@@ -553,8 +553,8 @@
<rtexprvalue>false</rtexprvalue>
<info>
Scope into which bean is searched. If not specified, method pageContext.findAttribute is used.
- Scope can be any JSP scope, 'component', or 'template'.
- In these two later cases, bean is search in tile/component/template context.
+ Scope can be any JSP scope, 'component', or 'template'.
+ In these two later cases, bean is search in tile/component/template context.
</info>
</attribute>
@@ -564,9 +564,9 @@
<rtexprvalue>true</rtexprvalue>
<info>
If the user is in the specified role, the tag is taken into account;
- otherwise, the tag is ignored (skipped).
- <br></br>
- The role isn't taken into account if <add> tag is used in a definition.
+ otherwise, the tag is ignored (skipped).
+ <br></br>
+ The role isn't taken into account if <add> tag is used in a definition.
</info>
</attribute>
@@ -583,7 +583,7 @@
<bodycontent>empty</bodycontent>
<info>
Retrieve content from tile context and include it.
- <br></br>Take into account the 'type' attribute.
+ <br></br>Take into account the 'type' attribute.
</info>
<attribute>
@@ -601,8 +601,8 @@
<rtexprvalue>true</rtexprvalue>
<info>
If this attribute is set to true, and the attribute specified by the name
- does not exist, simply return without writing anything. The default value is false, which will
- cause a runtime exception to be thrown.
+ does not exist, simply return without writing anything. The default value is false, which will
+ cause a runtime exception to be thrown.
</info>
</attribute>
@@ -610,9 +610,9 @@
<name>flush</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
- <info>
- True or false. If true, current page out stream is flushed before insertion.
- </info>
+ <info>
+ True or false. If true, current page out stream is flushed before insertion.
+ </info>
</attribute>
<attribute>
@@ -621,7 +621,7 @@
<rtexprvalue>true</rtexprvalue>
<info>
If the user is in the specified role, the tag is taken into account;
- otherwise, the tag is ignored (skipped).
+ otherwise, the tag is ignored (skipped).
</info>
</attribute>
@@ -630,22 +630,22 @@
<tag>
<name>getAsString</name>
<summary>
- Render the value of the specified tile/component/template attribute to the current JspWriter
+ Render the value of the specified tile/component/template attribute to the current JspWriter
</summary>
- <info>
- Retrieve the value of the specified tile/component/template attribute property, and render it to the current JspWriter as a String.
+ <info>
+ Retrieve the value of the specified tile/component/template attribute property, and render it to the current JspWriter as a String.
The usual toString() conversions is applied on found value.
- <br></br>Throw a JSPException if named value is not found.
- </info>
+ <br></br>Throw a JSPException if named value is not found.
+ </info>
<tagclass>org.apache.struts.taglib.tiles.GetAttributeTag</tagclass>
<bodycontent>empty</bodycontent>
<attribute>
<name>name</name>
<required>true</required>
<rtexprvalue>true</rtexprvalue>
- <info>
- Attribute name.
- </info>
+ <info>
+ Attribute name.
+ </info>
</attribute>
<attribute>
@@ -654,8 +654,8 @@
<rtexprvalue>true</rtexprvalue>
<info>
If this attribute is set to true, and the attribute specified by the name
- does not exist, simply return without writing anything. The default value is false, which will
- cause a runtime exception to be thrown.
+ does not exist, simply return without writing anything. The default value is false, which will
+ cause a runtime exception to be thrown.
</info>
</attribute>
@@ -665,7 +665,7 @@
<rtexprvalue>true</rtexprvalue>
<info>
If the user is in the specified role, the tag is taken into account;
- otherwise, the tag is ignored (skipped).
+ otherwise, the tag is ignored (skipped).
</info>
</attribute>
@@ -676,13 +676,13 @@
<summary>
Use attribute value inside page.
</summary>
- <info>
- Declare a Java variable, and an attribute in the specified scope, using tile attribute value.
- <br>
- Java variable and attribute will have the name specified by 'id', or the original name if not
- specified.
- </br>
- </info>
+ <info>
+ Declare a Java variable, and an attribute in the specified scope, using tile attribute value.
+ <br>
+ Java variable and attribute will have the name specified by 'id', or the original name if not
+ specified.
+ </br>
+ </info>
<tagclass>org.apache.struts.taglib.tiles.UseAttributeTag</tagclass>
<teiclass>org.apache.struts.taglib.tiles.UseAttributeTei</teiclass>
<bodycontent>empty</bodycontent>
@@ -690,33 +690,33 @@
<name>id</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
- <info>
- Declared attribute and variable name.
- </info>
+ <info>
+ Declared attribute and variable name.
+ </info>
</attribute>
<attribute>
<name>classname</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
- <info>
- Class of the declared variable.
- </info>
+ <info>
+ Class of the declared variable.
+ </info>
</attribute>
<attribute>
<name>scope</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
- <info>
- Scope of the declared attribute. Default to 'page'.
- </info>
+ <info>
+ Scope of the declared attribute. Default to 'page'.
+ </info>
</attribute>
<attribute>
<name>name</name>
<required>true</required>
<rtexprvalue>true</rtexprvalue>
- <info>
- Tile's attribute name.
- </info>
+ <info>
+ Tile's attribute name.
+ </info>
</attribute>
<attribute>
@@ -725,8 +725,8 @@
<rtexprvalue>true</rtexprvalue>
<info>
If this attribute is set to true, and the attribute specified by the name
- does not exist, simply return without error. The default value is false, which will
- cause a runtime exception to be thrown.
+ does not exist, simply return without error. The default value is false, which will
+ cause a runtime exception to be thrown.
</info>
</attribute>
@@ -737,29 +737,29 @@
<summary>
Import Tile's attribute in specified context.
</summary>
- <info>
- Import attribute from tile to requested scope.
- Attribute name and scope are optional. If not specified, all tile
- attributes are imported in page scope.
- Once imported, an attribute can be used as any other beans from jsp contexts.
- </info>
+ <info>
+ Import attribute from tile to requested scope.
+ Attribute name and scope are optional. If not specified, all tile
+ attributes are imported in page scope.
+ Once imported, an attribute can be used as any other beans from jsp contexts.
+ </info>
<tagclass>org.apache.struts.taglib.tiles.ImportAttributeTag</tagclass>
<bodycontent>empty</bodycontent>
<attribute>
<name>name</name>
<required>false</required>
<rtexprvalue>true</rtexprvalue>
- <info>
- Tile's attribute name. If not specified, all attributes are imported.
- </info>
+ <info>
+ Tile's attribute name. If not specified, all attributes are imported.
+ </info>
</attribute>
<attribute>
<name>scope</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
- <info>
- Scope into which attribute is imported. Default to page.
- </info>
+ <info>
+ Scope into which attribute is imported. Default to page.
+ </info>
</attribute>
<attribute>
@@ -768,8 +768,8 @@
<rtexprvalue>true</rtexprvalue>
<info>
If this attribute is set to true, and the attribute specified by the name
- does not exist, simply return without error. The default value is false, which will
- cause a runtime exception to be thrown.
+ does not exist, simply return without error. The default value is false, which will
+ cause a runtime exception to be thrown.
</info>
</attribute>
@@ -780,36 +780,36 @@
<summary>
Initialize Tile/Component definitions factory.
</summary>
- <info>
+ <info>
Initialize Tile/Components definitions factory.
- <br>
- In order to use Tile/Component definitions factory, you need to initialize the factory.
- This is generally done in a initializing servlet. In particular, it is done in
- "ComponentActionServlet" if you use it.
- If you don't initialize factory in a servlet, you can initialize it using this tag. You need
- to provide the description file name, and optionnaly the factory classname.
- Initialization is done only once, at the first call of this tag. Subsequent calls
- are ignored (tag checks existance of the factory.
- </br>
- </info>
+ <br>
+ In order to use Tile/Component definitions factory, you need to initialize the factory.
+ This is generally done in a initializing servlet. In particular, it is done in
+ "ComponentActionServlet" if you use it.
+ If you don't initialize factory in a servlet, you can initialize it using this tag. You need
+ to provide the description file name, and optionally the factory classname.
+ Initialization is done only once, at the first call of this tag. Subsequent calls
+ are ignored (tag checks existence of the factory.
+ </br>
+ </info>
<tagclass>org.apache.struts.taglib.tiles.InitDefinitionsTag</tagclass>
<bodycontent>empty</bodycontent>
<attribute>
<name>file</name>
<required>true</required>
<rtexprvalue>false</rtexprvalue>
- <info>
- Definition file name.
- </info>
+ <info>
+ Definition file name.
+ </info>
</attribute>
<attribute>
<name>classname</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
- <info>
- If specified, classname of the factory to create and initialized.
- </info>
+ <info>
+ If specified, classname of the factory to create and initialized.
+ </info>
</attribute>
</tag>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>