Author: fschumacher
Date: Tue Aug 11 19:04:02 2015
New Revision: 1695354
URL: http://svn.apache.org/r1695354
Log:
Spellchecking
Modified:
tomcat/trunk/webapps/docs/cluster-howto.xml
tomcat/trunk/webapps/docs/config/cluster-deployer.xml
tomcat/trunk/webapps/docs/config/executor.xml
tomcat/trunk/webapps/docs/config/filter.xml
tomcat/trunk/webapps/docs/config/host.xml
tomcat/trunk/webapps/docs/config/listeners.xml
tomcat/trunk/webapps/docs/config/manager.xml
tomcat/trunk/webapps/docs/config/systemprops.xml
tomcat/trunk/webapps/docs/index.xml
tomcat/trunk/webapps/docs/jasper-howto.xml
tomcat/trunk/webapps/docs/jndi-datasource-examples-howto.xml
tomcat/trunk/webapps/docs/jndi-resources-howto.xml
tomcat/trunk/webapps/docs/logging.xml
tomcat/trunk/webapps/docs/manager-howto.xml
tomcat/trunk/webapps/docs/monitoring.xml
tomcat/trunk/webapps/docs/realm-howto.xml
tomcat/trunk/webapps/docs/security-howto.xml
tomcat/trunk/webapps/docs/ssi-howto.xml
tomcat/trunk/webapps/docs/ssl-howto.xml
Modified: tomcat/trunk/webapps/docs/cluster-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/cluster-howto.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/cluster-howto.xml (original)
+++ tomcat/trunk/webapps/docs/cluster-howto.xml Tue Aug 11 19:04:02 2015
@@ -368,9 +368,9 @@ should be completed:</p>
Using interceptors, logic can be broken into more manageable pieces of
code. The interceptors configured above are:<br/>
TcpFailureDetector - verifies crashed members through TCP, if
multicast packets get dropped, this interceptor protects against false
positives,
ie the node marked as crashed even though it still is alive and
running.<br/>
- MessageDispatch15Interceptor - dispatches messages to a thread (thread
pool) to send message asynchrously.<br/>
+ MessageDispatch15Interceptor - dispatches messages to a thread (thread
pool) to send message asynchronously.<br/>
ThroughputInterceptor - prints out simple stats on message
traffic.<br/>
- Please note that the order of interceptors is important. the way they
are defined in server.xml is the way they are represented in the
+ Please note that the order of interceptors is important. The way they
are defined in server.xml is the way they are represented in the
channel stack. Think of it as a linked list, with the head being the
first most interceptor and the tail the last.
<br/>For more info, Please visit the <a
href="config/cluster-interceptor.html">reference documentation</a>
</p>
@@ -474,7 +474,7 @@ should be completed:</p>
<li><code>TomcatA</code> The session <code>S2</code> expires due to
inactivity.</li>
</ol>
-<p>Ok, now that we have a good sequence, we will take you through exactly what
happens in the session repliction code</p>
+<p>Ok, now that we have a good sequence, we will take you through exactly what
happens in the session replication code</p>
<ol>
<li><b><code>TomcatA</code> starts up</b>
@@ -506,7 +506,7 @@ should be completed:</p>
The request coming in to TomcatA is treated exactly the same way as
without session replication.
The action happens when the request is completed, the
<code>ReplicationValve</code> will intercept
the request before the response is returned to the user.
- At this point it finds that the session has been modified, and it uses
TCP to replicata the
+ At this point it finds that the session has been modified, and it uses
TCP to replicate the
session to TomcatB. Once the serialized data has been handed off to
the operating systems TCP logic,
the request returns to the user, back through the valve pipeline.
For each request the entire session is replicated, this allows code
that modifies attributes
Modified: tomcat/trunk/webapps/docs/config/cluster-deployer.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/cluster-deployer.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/cluster-deployer.xml (original)
+++ tomcat/trunk/webapps/docs/config/cluster-deployer.xml Tue Aug 11 19:04:02
2015
@@ -77,7 +77,7 @@
</attribute>
<attribute name="processDeployFrequency" required="false">
Frequency of the Farm watchDir check. Cluster wide deployment will be
- done once for the specified amount of backgrondProcess calls (ie, the
+ done once for the specified amount of backgroundProcess calls (ie, the
lower the amount, the most often the checks will occur). The minimum
value is 1, and the default value is 2.
<strong>Note: </strong> if <strong>watchEnabled</strong> is false, this
Modified: tomcat/trunk/webapps/docs/config/executor.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/executor.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/executor.xml (original)
+++ tomcat/trunk/webapps/docs/config/executor.xml Tue Aug 11 19:04:02 2015
@@ -37,7 +37,7 @@
<p>The <strong>Executor</strong> represents a thread pool that can be shared
between components in Tomcat. Historically there has been a thread pool
per
- connector created but this allows you to share a thread pool, between
(primarly) connector
+ connector created but this allows you to share a thread pool, between
(primarily) connector
but also other components when those get configured to support
executors</p>
Modified: tomcat/trunk/webapps/docs/config/filter.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/filter.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/filter.xml (original)
+++ tomcat/trunk/webapps/docs/config/filter.xml Tue Aug 11 19:04:02 2015
@@ -704,7 +704,7 @@ FINE: Request "/docs/config/manager.html
<p>There are a number of HTTP headers that can be added to the response to
improve the security of the connection. This filter provides a mechanism
for
adding those headers. Note that security related headers with more complex
- requirements, like CORS, are implemted as separate Filters.</p>
+ requirements, like CORS, are implemented as separate Filters.</p>
</subsection>
Modified: tomcat/trunk/webapps/docs/config/host.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/host.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/host.xml (original)
+++ tomcat/trunk/webapps/docs/config/host.xml Tue Aug 11 19:04:02 2015
@@ -534,7 +534,7 @@
<subsection name="Single Sign On">
<p>In many environments, but particularly in portal environments, it
- is desireable to have a user challenged to authenticate themselves only
+ is desirable to have a user challenged to authenticate themselves only
once over a set of web applications deployed on a particular virtual
host. This can be accomplished by nesting an element like this inside
the Host element for this virtual host:</p>
Modified: tomcat/trunk/webapps/docs/config/listeners.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/listeners.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/listeners.xml (original)
+++ tomcat/trunk/webapps/docs/config/listeners.xml Tue Aug 11 19:04:02 2015
@@ -398,7 +398,7 @@
</attribute>
<attribute name="homeBase" required="false">
- <p>The base directory containing user home directories.This is
effective
+ <p>The base directory containing user home directories. This is
effective
only when <code>org.apache.catalina.startup.HomesUserDatabase</code> is
used.</p>
</attribute>
Modified: tomcat/trunk/webapps/docs/config/manager.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/manager.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/manager.xml (original)
+++ tomcat/trunk/webapps/docs/config/manager.xml Tue Aug 11 19:04:02 2015
@@ -429,7 +429,7 @@
<attribute name="sessionValidCol" required="false">
<p>Name of the database column, contained in the specified session table,
- that contains a flag indicating whether this swapped out session is stil
+ that contains a flag indicating whether this swapped out session is still
valid or not. The column type must accept a single character. If not
specified the default value of <code>valid</code> will be used.</p>
</attribute>
@@ -452,7 +452,7 @@
);</source>
<p>Note: The SQL command above does not use the default names for either the
- table or the clumns so the JDBC Store would need to be configured to reflect
+ table or the columns so the JDBC Store would need to be configured to reflect
this.</p>
<p>In order for the JDBC Based Store to successfully connect to your
Modified: tomcat/trunk/webapps/docs/config/systemprops.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/systemprops.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/systemprops.xml (original)
+++ tomcat/trunk/webapps/docs/config/systemprops.xml Tue Aug 11 19:04:02 2015
@@ -671,7 +671,7 @@
<p>The class name of the factory to use to create resources of type
<code>javax.sql.DataSource</code>. If not specified the default of
<code>org.apache.tomcat.dbcp.dbcp2.BasicDataSourceFactory</code> is used
- which is a package renamed (to avoid conflictions) copy of
+ which is a package renamed (to avoid conflicts) copy of
<a href="http://commons.apache.org/dbcp";>Apache Commons DBCP</a>.</p>
</property>
Modified: tomcat/trunk/webapps/docs/index.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/index.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/index.xml (original)
+++ tomcat/trunk/webapps/docs/index.xml Tue Aug 11 19:04:02 2015
@@ -83,7 +83,7 @@ Apache Tomcat, and using many of the Apa
that is provided to each web application.</li>
<li><a href="jndi-datasource-examples-howto.html">
<strong>JDBC DataSource</strong></a>
- - Configuring a JNDI DataSoure with a DB connection pool.
+ - Configuring a JNDI DataSource with a DB connection pool.
Examples for many popular databases.</li>
<li><a href="class-loader-howto.html"><strong>Classloading</strong></a>
- Information about class loading in Apache Tomcat, including where to
place
Modified: tomcat/trunk/webapps/docs/jasper-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/jasper-howto.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/jasper-howto.xml (original)
+++ tomcat/trunk/webapps/docs/jasper-howto.xml Tue Aug 11 19:04:02 2015
@@ -353,8 +353,8 @@ without debug info <code>debug="off
<p>
When you don't want to stop the jsp generation at first jsp syntax error, use
<code>failOnError="false"</code>and with
-<code>showSuccess="true"</code> all successfull <i>jsp to java</i>
-generation are printed out. Sometimes it is very helpfull, when you cleanup the
+<code>showSuccess="true"</code> all successful <i>jsp to java</i>
+generation are printed out. Sometimes it is very helpful, when you cleanup the
generate java source files at <code>${webapp.path}/WEB-INF/src</code>
and the compile jsp servlet classes at
<code>${webapp.path}/WEB-INF/classes/org/apache/jsp</code>.
Modified: tomcat/trunk/webapps/docs/jndi-datasource-examples-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/jndi-datasource-examples-howto.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/jndi-datasource-examples-howto.xml (original)
+++ tomcat/trunk/webapps/docs/jndi-datasource-examples-howto.xml Tue Aug 11
19:04:02 2015
@@ -539,7 +539,7 @@ found. For example, you may be using a c
Oracle client. The classeXXXs.zip file and Oracle client software versions
must match.
</li>
<li>A <code>$PATH</code>, <code>LD_LIBRARY_PATH</code> problem.</li>
-<li>It has been reported that ignoring the driver you have downloded from otn
and using
+<li>It has been reported that ignoring the driver you have downloaded from otn
and using
the classes12.zip file from the directory <code>$ORAHOME\jdbc\lib</code> will
also work.
</li>
</ul>
Modified: tomcat/trunk/webapps/docs/jndi-resources-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/jndi-resources-howto.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/jndi-resources-howto.xml (original)
+++ tomcat/trunk/webapps/docs/jndi-resources-howto.xml Tue Aug 11 19:04:02 2015
@@ -692,7 +692,7 @@ Transport.send(message);]]></source>
Resource reference to a factory for java.sql.Connection
instances that may be used for talking to a particular
database that is configured in the <Context>
- configurartion for the web application.
+ configuration for the web application.
</description>
<res-ref-name>
jdbc/EmployeeDB
@@ -799,7 +799,7 @@ conn.close();]]></source>
returned to the pool. Default: false</li>
</ul>
<p>The optional evictor thread is responsible for shrinking the pool
- by removing any conections which are idle for a long time. The evictor
+ by removing any connections which are idle for a long time. The evictor
does not respect <code>minIdle</code>. Note that you do not need to
activate the evictor thread if you only want the pool to shrink according
to the configured <code>maxIdle</code> property.</p>
@@ -810,7 +810,7 @@ conn.close();]]></source>
milliseconds between consecutive runs of the evictor.
Default: -1 (disabled)</li>
<li><strong>numTestsPerEvictionRun</strong> - The number of connections
- that will be checked for idleness by the evitor during each
+ that will be checked for idleness by the evictor during each
run of the evictor. Default: 3</li>
<li><strong>minEvictableIdleTimeMillis</strong> - The idle time in
milliseconds after which a connection can be removed from the pool
@@ -888,7 +888,7 @@ conn.close();]]></source>
<h4>1. Write A Resource Factory Class</h4>
<p>You must write a class that implements the JNDI service provider
- <code>javax.naming.spi.ObjectFactory</code> inteface. Every time your
+ <code>javax.naming.spi.ObjectFactory</code> interface. Every time your
web application calls <code>lookup()</code> on a context entry that is
bound to this factory (assuming that the factory is configured with
<code>singleton="false"</code>), the
Modified: tomcat/trunk/webapps/docs/logging.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/logging.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/logging.xml (original)
+++ tomcat/trunk/webapps/docs/logging.xml Tue Aug 11 19:04:02 2015
@@ -46,7 +46,7 @@
<p>
To configure Tomcat to use an alternative logging framework for its
- internal logging, one has to replace the JULI impementation that is
+ internal logging, one has to replace the JULI implementation that is
hard-coded to use <code>java.util.logging</code> with a JULI
implementation that retains the full Commons Logging discovery mechanism.
Such an implementation is provided as an <a href="extras.html">extras</a>
@@ -488,7 +488,7 @@ log4j.logger.org.apache.catalina.core.Co
documentation</a> for details.</p>
<p>This <code>tomcat-juli.jar</code> differs from the default one. It
contains the full Apache Commons Logging implementation and thus is
- able to discover the presense of log4j and configure itself.</p>
+ able to discover the presence of log4j and configure itself.</p>
</li>
<li><p>If you want to configure Tomcat to use log4j globally:</p>
Modified: tomcat/trunk/webapps/docs/manager-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/manager-howto.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/manager-howto.xml (original)
+++ tomcat/trunk/webapps/docs/manager-howto.xml Tue Aug 11 19:04:02 2015
@@ -697,7 +697,7 @@ Default maximum session inactive interva
3 - <4 minutes: 1 sessions
>0 minutes: 2 sessions were expired]]></source>
-<p>Actually <code>/sessions</code> and <code>/expire</code> are synonims for
+<p>Actually <code>/sessions</code> and <code>/expire</code> are synonyms for
the same command. The difference is in the presence of <code>idle</code>
parameter.</p>
@@ -1054,7 +1054,7 @@ on each of deployed web applications wil
</li>
</ul>
<p>
- You'll need to experiment with this to really understand its capabilites.
+ You'll need to experiment with this to really understand its capabilities
If you provide no <code>qry</code> parameter, then all of the MBeans will
be displayed. We really recommend looking at the tomcat source code and
understand the JMX spec to get a better understanding of all the queries
Modified: tomcat/trunk/webapps/docs/monitoring.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/monitoring.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/monitoring.xml (original)
+++ tomcat/trunk/webapps/docs/monitoring.xml Tue Aug 11 19:04:02 2015
@@ -373,7 +373,7 @@ List of Attributes
<tr>
<td>delimiter</td>
- <td>Split result with delimiter (java.util.StringTokenizier)
+ <td>Split result with delimiter (java.util.StringTokenizer)
and use resultproperty as prefix to store tokens.
</td>
<td></td>
@@ -559,7 +559,7 @@ List of Attributes
<tr>
<td>delimiter</td>
- <td>Split result with delimiter (java.util.StringTokenizier)
+ <td>Split result with delimiter (java.util.StringTokenizer)
and use resultproperty as prefix to store tokens.
</td>
<td></td>
@@ -670,7 +670,7 @@ List of Attributes
</tr>
<tr>
- <td>attributebinduing</td>
+ <td>attributebinding</td>
<td>bind ALL MBean attributes in addition to <em>name</em>
</td>
<td><code class="noHighlight">false</code></td>
@@ -678,7 +678,7 @@ List of Attributes
<tr>
<td>delimiter</td>
- <td>Split result with delimiter (java.util.StringTokenizier)
+ <td>Split result with delimiter (java.util.StringTokenizer)
and use resultproperty as prefix to store tokens.
</td>
<td></td>
Modified: tomcat/trunk/webapps/docs/realm-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/realm-howto.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/realm-howto.xml (original)
+++ tomcat/trunk/webapps/docs/realm-howto.xml Tue Aug 11 19:04:02 2015
@@ -1053,7 +1053,7 @@ When developing your LoginModule, note t
only recognizes the <code>NameCallback</code> and
<code>PasswordCallback</code> at present.
</li>
<li>Although not specified in JAAS, you should create
-seperate classes to distinguish between users and roles, extending
<code>javax.security.Principal</code>,
+separate classes to distinguish between users and roles, extending
<code>javax.security.Principal</code>,
so that Tomcat can tell which Principals returned from your login
module are users and which are roles (see
<code>org.apache.catalina.realm.JAASRealm</code>).
Regardless, the first Principal returned is <em>always</em> treated as the
user Principal.
Modified: tomcat/trunk/webapps/docs/security-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/security-howto.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/security-howto.xml (original)
+++ tomcat/trunk/webapps/docs/security-howto.xml Tue Aug 11 19:04:02 2015
@@ -289,7 +289,7 @@
<p>The <strong>tomcatAuthentication</strong> and
<strong>tomcatAuthorization</strong> attributes are used with the
- AJP connectors to determine if Tomcat should handle all authenication and
+ AJP connectors to determine if Tomcat should handle all authentication
and
authorisation or if authentication should be delegated to the reverse
proxy (the authenticated user name is passed to Tomcat as part of the AJP
protocol) with the option for Tomcat to still perform authorization.</p>
Modified: tomcat/trunk/webapps/docs/ssi-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/ssi-howto.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/ssi-howto.xml (original)
+++ tomcat/trunk/webapps/docs/ssi-howto.xml Tue Aug 11 19:04:02 2015
@@ -174,7 +174,7 @@ Returns the list of all the defined vari
</li>
<li>
<strong>set</strong> - <code><!--#set var="foo" value="Bar" --></code>
-is used to assign a value to a user-defind variable.
+is used to assign a value to a user-defined variable.
</li>
<li>
<strong>if elif endif else</strong> - Used to create conditional sections. For
example:
Modified: tomcat/trunk/webapps/docs/ssl-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/ssl-howto.xml?rev=1695354&r1=1695353&r2=1695354&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/ssl-howto.xml (original)
+++ tomcat/trunk/webapps/docs/ssl-howto.xml Tue Aug 11 19:04:02 2015
@@ -286,7 +286,7 @@ JSSE implementation.
</p>
<p>
-As configuration attributes for SSL support significally differ between
+As configuration attributes for SSL support significantly differ between
APR vs. JSSE implementations, it is <strong>recommended</strong> to
avoid auto-selection of implementation. It is done by specifying a classname
in the <b>protocol</b> attribute of the <a
href="config/http.html">Connector</a>.</p>
@@ -502,7 +502,7 @@ SSL communications, and what to do about
<p>If you are using the APR/native connector,
it will determine the strength of ephemeral DH keys from the key size of
your RSA certificate. For example a 2048 bit RSA key will result in
- using a 2048 bit primefor the DH keys. Unfortunately Java 6 only supports
+ using a 2048 bit prime for the DH keys. Unfortunately Java 6 only supports
768 bit and Java 7 only supports 1024 bit. So if your certificate has a
stronger key, old Java clients might produce such handshake failures.
As a mitigation you can either try to force them to use another cipher by
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
