jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fschumac...@apache.org
Subject svn commit: r1676839 - /jmeter/trunk/xdocs/usermanual/
Date Wed, 29 Apr 2015 20:00:23 GMT
Author: fschumacher
Date: Wed Apr 29 20:00:22 2015
New Revision: 1676839

URL: http://svn.apache.org/r1676839
Log:
More typos

Modified:
    jmeter/trunk/xdocs/usermanual/best-practices.xml
    jmeter/trunk/xdocs/usermanual/build-web-test-plan.xml
    jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml
    jmeter/trunk/xdocs/usermanual/functions.xml
    jmeter/trunk/xdocs/usermanual/get-started.xml
    jmeter/trunk/xdocs/usermanual/hints_and_tips.xml
    jmeter/trunk/xdocs/usermanual/intro.xml
    jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml
    jmeter/trunk/xdocs/usermanual/listeners.xml
    jmeter/trunk/xdocs/usermanual/regular_expressions.xml
    jmeter/trunk/xdocs/usermanual/remote-test.xml
    jmeter/trunk/xdocs/usermanual/test_plan.xml

Modified: jmeter/trunk/xdocs/usermanual/best-practices.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/best-practices.xml?rev=1676839&r1=1676838&r2=1676839&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/best-practices.xml (original)
+++ jmeter/trunk/xdocs/usermanual/best-practices.xml Wed Apr 29 20:00:22 2015
@@ -407,7 +407,7 @@ If the value is not known until the test
 Doing so will ease you migration to the next version of JMeter. <br/>
 Note that in the documentation <code>jmeter.properties</code> is frequently mentioned
but this should be understood as
 "Copy from jmeter.properties to user.properties the property you want to modify and do so
in the latter file".</p>
-<note><code>user.properties</code> file superseeds the properties defined
in <code>jmeter.properties</code></note>
+<note><code>user.properties</code> file supersedes the properties defined
in <code>jmeter.properties</code></note>
 </section>
 
 </body>

Modified: jmeter/trunk/xdocs/usermanual/build-web-test-plan.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-web-test-plan.xml?rev=1676839&r1=1676838&r2=1676839&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/build-web-test-plan.xml (original)
+++ jmeter/trunk/xdocs/usermanual/build-web-test-plan.xml Wed Apr 29 20:00:22 2015
@@ -77,7 +77,7 @@ field, enter JMeter Users.</p>
 
 <p>Next, increase the number of users (called threads) to 5.</p>
 
-<p>In the next field, the Ramp-Up Period, leave the the default value of 1
+<p>In the next field, the Ramp-Up Period, leave the default value of 1
 seconds.  This property tells JMeter how long to delay between starting each
 user. For example, if you enter a Ramp-Up Period of 5 seconds, JMeter will
 finish starting all of your users by the end of the 5 seconds.  So, if we have

Modified: jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml?rev=1676839&r1=1676838&r2=1676839&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml (original)
+++ jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml Wed Apr 29 20:00:22 2015
@@ -103,7 +103,7 @@ field, enter JMeter Users.</p>
 
 <p>Next, increase the number of users (called threads) to 10.</p>
 
-<p>In the next field, the Ramp-Up Period, leave the the default value of 0
+<p>In the next field, the Ramp-Up Period, leave the default value of 0
 seconds.  This property tells JMeter how long to delay between starting each
 user. For example, if you enter a Ramp-Up Period of 5 seconds, JMeter will
 finish starting all of your users by the end of the 5 seconds.  So, if we have

Modified: jmeter/trunk/xdocs/usermanual/functions.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/functions.xml?rev=1676839&r1=1676838&r2=1676839&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/functions.xml (original)
+++ jmeter/trunk/xdocs/usermanual/functions.xml Wed Apr 29 20:00:22 2015
@@ -151,7 +151,7 @@ run.  This could be used to replace the
 matter to change a test to target a different server with the same test.
 </p>
 <p>
-Note that variables cannot currently be nested; i.e <code>${Var${N}}</code> does
not work.
+Note that variables cannot currently be nested; i.e. <code>${Var${N}}</code>
does not work.
 The <code>__V</code> (variable) function (versions after 2.2) can be used to
do this: <code>${__V(Var${N})}</code>.
 In earlier JMeter versions one can use <code>${__BeanShell(vars.get("Var${N}")}</code>.
 </p>
@@ -198,7 +198,7 @@ Configuration elements are processed by
 Therefore functions such as <code>__threadNum</code> do not work properly in
elements such as User Defined Variables.
 Also note that variables defined in a UDV element are not available until the element has
been processed.
 </p>
-<note>When using variable/function references in SQL code (etc),
+<note>When using variable/function references in SQL code (etc.),
 remember to include any necessary quotes for text strings,
 i.e. use
 <source>
@@ -258,7 +258,7 @@ The <code>__logn()</code> function refer
 Alternatively, the Java Request sampler can be used to create a sample containing variable
references;
 the output will be shown in the appropriate Listener.
 For versions of JMeter later than 2.3, there is a <complink name="Debug Sampler"/>

-that can be used to display the values of variables etc in the Tree View Listener.
+that can be used to display the values of variables etc. in the Tree View Listener.
 </p>
 <note><sup>*</sup>If you define a user-defined static variable with the
same name as a built-in function, your static
 variable will override the built-in function.</note>
@@ -307,7 +307,7 @@ replacement string") parsed by this func
         in your template string</property>
         <property name="Second argument" required="Yes">This is the template string
that will replace
         the function at run-time.  To refer to a group captured in the regular expression,
use the syntax:
-        <code>$[group_number]$</code>.  Ie: <code>$1$</code>, or
<code>$2$</code>.  Your template can be any string.</property>
+        <code>$[group_number]$</code>.  I.e.: <code>$1$</code>, or
<code>$2$</code>.  Your template can be any string.</property>
         <property name="Third argument" required="No, default=1">The third argument
tells JMeter which match
         to use.  Your regular expression might find numerous matches.  You have four choices:
                 <ul><li>An integer - Tells JMeter to use that match.  '<code>1</code>'
for the first found match, '<code>2</code>' for the
@@ -488,7 +488,7 @@ Examples:<br></br>
     See the documentation for DecimalFormat for full details.<br></br>
     If the path name does not contain any special formatting characters,
     the current sequence number will be appended to the name, otherwise
-    the number will be inserted aaccording to the fomatting instructions.<br></br>
+    the number will be inserted according to the formatting instructions.<br></br>
     If the start sequence number is omitted, and the end sequence number is specified,
     the sequence number is interpreted as a loop count, and the file will be used at most
"<code>end</code>" times.
     In this case the filename is not formatted.
@@ -779,7 +779,7 @@ For example:
 </b>
 </p>
 <note>
-Note that a different Interpreter is used for each independent occurence of the function
+Note that a different Interpreter is used for each independent occurrence of the function
 in a test script, but the same Interpreter is used for subsequent invocations.
 This means that variables persist across calls to the function.
 </note>

Modified: jmeter/trunk/xdocs/usermanual/get-started.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/get-started.xml?rev=1676839&r1=1676838&r2=1676839&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/get-started.xml (original)
+++ jmeter/trunk/xdocs/usermanual/get-started.xml Wed Apr 29 20:00:22 2015
@@ -114,7 +114,7 @@ If your version of Java does not include
 Include the necessary encryption packages in JMeter's <a href="#classpath">classpath</a>.
 
 Also, update <a href="#configuring_jmeter"><code>system.properties</code></a>
to register the SSL Provider.</p>
 <p>
-JMeter HTTP defaults to protocol level TLS. This can be changed by editting the JMeter property

+JMeter HTTP defaults to protocol level TLS. This can be changed by editing the JMeter property

 <code>https.default.protocol</code> in <code>jmeter.properties</code>
or <code>user.properties</code>.
 </p>
 <p><b>The JMeter HTTP samplers are configured to accept all certificates,
@@ -386,7 +386,7 @@ Normally this is not necessary.
 </subsection>
 
 <subsection name="&sect-num;.4.6 Overriding Properties Via The Command Line" anchor="override">
-<p>Java system properties, JMeter properties, and logging properties can be overriden
directly on the command line
+<p>Java system properties, JMeter properties, and logging properties can be overridden
directly on the command line
 (instead of modifying <code>jmeter.properties</code>).
 To do so, use the following options:</p>
 <dl>
@@ -521,7 +521,7 @@ Prior to version 2.5.1, JMeter invoked <
 This caused problems for applications that invoke JMeter directly, so JMeter no longer invokes
<code>System.exit()</code>
 for a normal test completion. [Some fatal errors may still invoke <code>System.exit()</code>]
 JMeter will exit all the non-daemon threads it starts, but it is possible that some non-daemon
threads
-may still remain; these will prevent the JVM from exitting.
+may still remain; these will prevent the JVM from exiting.
 To detect this situation, JMeter starts a new daemon thread just before it exits.
 This daemon thread waits a short while; if it returns from the wait, then clearly the
 JVM has not been able to exit, and the thread prints a message to say why.

Modified: jmeter/trunk/xdocs/usermanual/hints_and_tips.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/hints_and_tips.xml?rev=1676839&r1=1676838&r2=1676839&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/hints_and_tips.xml (original)
+++ jmeter/trunk/xdocs/usermanual/hints_and_tips.xml Wed Apr 29 20:00:22 2015
@@ -35,7 +35,7 @@ Also, try search the JMeter User list; s
 </p>
 <subsection name="&sect-num;.1 Passing variables between threads" anchor="variable_and_threads">
 <p>
-JMeter variables have thread scope. This is deliberate, so that threads can act indepently.
+JMeter variables have thread scope. This is deliberate, so that threads can act independently.
 However sometimes there is a need to pass variables between different threads, in the same
or different Thread Groups.
 </p>
 <p>

Modified: jmeter/trunk/xdocs/usermanual/intro.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/intro.xml?rev=1676839&r1=1676838&r2=1676839&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/intro.xml (original)
+++ jmeter/trunk/xdocs/usermanual/intro.xml Wed Apr 29 20:00:22 2015
@@ -47,7 +47,7 @@ since been replaced by the Apache Tomcat
 and to add functional-testing capabilities.
 </p>
 
-<p>JMeter became a Top Level Apache project in November 2011, which means it has a
Project Management Commitee and a dedicated website.</p>
+<p>JMeter became a Top Level Apache project in November 2011, which means it has a
Project Management Committee and a dedicated website.</p>
 </subsection>
 
 <subsection name="1.2 The Future" anchor="future">

Modified: jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml?rev=1676839&r1=1676838&r2=1676839&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml (original)
+++ jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml Wed Apr 29 20:00:22 2015
@@ -45,14 +45,14 @@
 <subsection name="1.1 Thread Bind" anchor="thread_bind">
     <p>
     This bind is meant to open a session to a LDAP server. Any testplan should use this operation
as the starting point from a session.
-    For each Thread (each virtual user) a seperate connection with the LDAP server is build,
and so a seperate Thread bind is performed.
+    For each Thread (each virtual user) a separate connection with the LDAP server is build,
and so a separate Thread bind is performed.
     </p>
 </subsection>
 <subsection name="1.2 Single bind/unbind" anchor="single">
     <p>
         This bind is used for user authentication verification.
         A proper developed LDAP client, who needs an authenticated user, perform a bind with
a given distinguished name and password.
-        This Single bind/unbind operation is for this purpose. It builds it own seperate
connection to the LDAP server, performs a
+        This Single bind/unbind operation is for this purpose. It builds it own separate
connection to the LDAP server, performs a
         bind operation, and ends the connection again (by sending an unbind).
     </p>
 </subsection>
@@ -73,7 +73,7 @@
 </subsection>
 <subsection name="4 Search" anchor="search">
     <p>
-    The search test simply searches for all objects which comply with a given search filter,
eg.
+    The search test simply searches for all objects which comply with a given search filter,
e.g.
     all persons with a "employeeType=inactive" or "all persons with a userID equals user1"
     </p>
 </subsection>
@@ -86,7 +86,7 @@
 <subsection name="6 Modify" anchor="modify">
     <p>
         This operation modifies one or more attributes from a given object.
-        It needs the distinghised name from the object, as well as the attributes and the
new values for this attribute.<br/>
+        It needs the distinguished name from the object, as well as the attributes and the
new values for this attribute.<br/>
         Three versions are available, add, for adding an attribute value<br/>
         replace, for overwriting the old attribute value with a new value<br/>
         delete, to delete a value form an attribute, or to delete all the values of an attribute<br/>
@@ -95,16 +95,16 @@
 <subsection name="7 Delete" anchor="delete">
     <p>
         This operation deletes an object from the LDAP server.
-        It needs the distinghised name from the object.
+        It needs the distinguished name from the object.
     </p>
 </subsection>
 <subsection name="8 modDN" anchor="moddn">
     <p>
         This operation modifies the distinguished name from an object (it "moves" the object).<br/>
         It comes in two flavours, just renaming an entry, then you specify a new RDN (relative
distinguished name, this is the lowest part of the DN)<br/>
-        eg, you can rename "cn=admin,dc=test,dc=com" to cn=administrator,dc=test,dc=com"<br/>
+        e.g. you can rename "cn=admin,dc=test,dc=com" to cn=administrator,dc=test,dc=com"<br/>
         The second flavour is renaming (moving) a complete subtree by specifying a "new superior"<br/>
-        eg you can move a complete subtree "ou=retired,ou=people,dc=test,dc=com" to a new
subtree "ou=retired people,dc=test,dc=com" by specifying
+        e.g. you can move a complete subtree "ou=retired,ou=people,dc=test,dc=com" to a new
subtree "ou=retired people,dc=test,dc=com" by specifying
         a new rdn "ou=retired people" and a new superior of "dc=test,dc=com"
     </p>
 </subsection>

Modified: jmeter/trunk/xdocs/usermanual/listeners.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/listeners.xml?rev=1676839&r1=1676838&r2=1676839&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/listeners.xml (original)
+++ jmeter/trunk/xdocs/usermanual/listeners.xml Wed Apr 29 20:00:22 2015
@@ -389,7 +389,7 @@ Content-Type: text/html; charset=ISO-885
   &lt;url&gt;http://www.apache.org/&lt;/url&gt;
 &lt;/httpSample&gt;
 
--- nonHTTPP Sample
+-- non HTTP Sample
 
 &lt;sample t="0" lt="0" ts="1144372616082" s="true" lb="Example Sampler"
     rc="200" rm="OK" tn="Listen 1-1" dt="text" de="ISO-8859-1" by="10"&gt;

Modified: jmeter/trunk/xdocs/usermanual/regular_expressions.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/regular_expressions.xml?rev=1676839&r1=1676838&r2=1676839&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/regular_expressions.xml (original)
+++ jmeter/trunk/xdocs/usermanual/regular_expressions.xml Wed Apr 29 20:00:22 2015
@@ -70,7 +70,7 @@ combinations - and '<code>alp</code>' is
 Unlike Perl, there is no need to (i.e. do not) enclose the regular expression in <code>//</code>.
 </note>
 <p>
-So how does one use the modifiers <code>ismx</code> etc if there is no trailing
<code>/</code>? 
+So how does one use the modifiers <code>ismx</code> etc. if there is no trailing
<code>/</code>? 
 The solution is to use <i>extended regular expressions</i>, i.e. <code>/abc/i</code>
becomes <code>(?i)abc</code>.
 See also <a href="#placement">Placement of modifiers</a> below.
 </p>
@@ -115,7 +115,7 @@ Suppose you want to match the following
 <code>name="file.name" value="readme.txt"</code> 
 and you want to extract both <code>file.name</code> and <code>readme.txt</code>.
 <br/>
-A suitable reqular expression would be:
+A suitable regular expression would be:
 <br/>
 <code>name="([^"]+)" value="([^"]+)"</code>
 <br/>
@@ -174,7 +174,7 @@ and the '<code>$</code>' metacharacter m
 <subsection name="&sect-num;.4 Meta characters" anchor="meta_chars">
 <p>
 Regular expressions use certain characters as meta characters - these characters have a special
meaning to the RE engine.
-Such characters must be escaped by preceeding them with <code>\</code> (backslash)
in order to treat them as ordinary characters.
+Such characters must be escaped by preceding them with <code>\</code> (backslash)
in order to treat them as ordinary characters.
 Here is a list of the meta characters and their meaning (please check the ORO documentation
if in doubt).
 </p>
 <dl>

Modified: jmeter/trunk/xdocs/usermanual/remote-test.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/remote-test.xml?rev=1676839&r1=1676838&r2=1676839&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/remote-test.xml (original)
+++ jmeter/trunk/xdocs/usermanual/remote-test.xml Wed Apr 29 20:00:22 2015
@@ -39,7 +39,7 @@ all the data from them.  This offers the
 
 <ul>
 <li>Saving of test samples to the local machine </li>
-<li>Managment of multiple JMeterEngines from a single machine </li>
+<li>Management of multiple JMeterEngines from a single machine </li>
 <li>No need to copy the test plan to each server - the client sends it to all the servers</li>
 </ul>
 </p>
@@ -144,7 +144,7 @@ and follow the instructions below.
 </p>
 <p>JMeter uses Remote Method Invocation (RMI) as the remote communication mechanism.
 Therefore, you need
 to run the RMI Registry application (which is named, "<code>rmiregistry</code>")
that comes with the JDK and is located in the "<code>bin</code>"
-directory.  Before running <code>rmiregistry</code>, make sure that the following
jars are in your system claspath:
+directory.  Before running <code>rmiregistry</code>, make sure that the following
jars are in your system classpath:
 <ul>
     <li><code>JMETER_HOME/lib/ext/ApacheJMeter_core.jar</code></li>
     <li><code>JMETER_HOME/lib/jorphan.jar</code></li>
@@ -185,7 +185,7 @@ rmiregistry -J-Dsun.rmi.log.debug=true \
 For example: "<code>jmeter -s -Dsun.rmi.loader.logLevel=verbose</code>" (i.e.
omit the <code>-J</code> prefixes).
 Alternatively the properties can be defined in the <code>system.properties</code>
file.
 </p>
-<p>The solution to the problem is to remove the loopbacks <code>127.0.0.1</code>
and <code>127.0.0.2</code> from <code>etc/hosts</code>.
+<p>The solution to the problem is to remove the loopbacks <code>127.0.0.1</code>
and <code>127.0.0.2</code> from <code>/etc/hosts</code>.
 What happens is <code>jmeter-server</code> can't connect to rmiregistry if <code>127.0.0.2</code>
loopback is not available.
 Use the following settings to fix the problem.</p>
 <p> Replace</p>
@@ -252,7 +252,7 @@ There are some JMeter properties that ca
     <dh><code>Hold</code></dh><dd>hold samples in an array
until the end of a run. This may use a lot of memory on the server and is discouraged.</dd>
     <dh><code>DiskStore</code></dh><dd>store samples in a disk
file (under <code>java.io.temp</code>) until the end of a run. 
     The serialised data file is deleted on JVM exit.</dd>
-    <dh><code>StrippedDiskStore</code></dh><dd>remove responseData
from succesful samples, and use DiskStore sender to send them.</dd>
+    <dh><code>StrippedDiskStore</code></dh><dd>remove responseData
from successful samples, and use DiskStore sender to send them.</dd>
     <dh><code>Batch</code></dh><dd>send saved samples when
either the count (num_sample_threshold) or time (time_threshold) exceeds a threshold,
     at which point the samples are sent synchronously.
     The thresholds can be configured on the server using the following properties:
@@ -274,8 +274,8 @@ There are some JMeter properties that ca
       </ul>
     Other fields that vary between samples are lost. 
     </dd>
-    <dh><code>Stripped</code></dh><dd>remove responseData from
succesful samples</dd>
-    <dh><code>StrippedBatch</code></dh><dd>remove responseData
from succesful samples, and use Batch sender to send them.</dd>
+    <dh><code>Stripped</code></dh><dd>remove responseData from
successful samples</dd>
+    <dh><code>StrippedBatch</code></dh><dd>remove responseData
from successful samples, and use Batch sender to send them.</dd>
     <dh><code>Asynch</code></dh><dd>samples are temporarily
stored in a local queue. A separate worker thread sends the samples.
         This allows the test thread to continue without waiting for the result to be sent
back to the client.
         However, if samples are being created faster than they can be sent, the queue will
eventually fill up,
@@ -284,7 +284,7 @@ There are some JMeter properties that ca
         The queue size can be adjusted by setting the JMeter property
         <code>asynch.batch.queue.size</code> (default <code>100</code>)
on the server node.
     </dd>
-    <dh><code>StrippedAsynch</code></dh><dd>remove responseData
from succesful samples, and use Async sender to send them.</dd>
+    <dh><code>StrippedAsynch</code></dh><dd>remove responseData
from successful samples, and use Async sender to send them.</dd>
     <dh><code>Custom implementation</code></dh><dd>set the
mode parameter to your custom sample sender class name.
     This must implement the interface <code>SampleSender</code> and have a constructor
which takes a single
     parameter of type <code>RemoteSampleListener</code>. 

Modified: jmeter/trunk/xdocs/usermanual/test_plan.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/test_plan.xml?rev=1676839&r1=1676838&r2=1676839&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/test_plan.xml (original)
+++ jmeter/trunk/xdocs/usermanual/test_plan.xml Wed Apr 29 20:00:22 2015
@@ -192,7 +192,7 @@ two different searches.  However, we wan
 each search.  We could do this by having 4 simple HTTP request elements (load search,
 search "A", load search, search "B").  Instead, we use the <complink name="Interleave
 Controller"/> which passes on one child request each time through the test.  It keeps
the
-ordering (ie - it doesn't pass one on at random, but "remembers" its place) of its
+ordering (i.e. it doesn't pass one on at random, but "remembers" its place) of its
 child elements.  Interleaving 2 child requests may be overkill, but there could easily have
 been 8, or 20 child requests.</p>
 
@@ -411,7 +411,7 @@ that Controller.  In the following test
 <p>Another example, this time using Timers:</p>
 <figure image="scoping3.png">complex example</figure>
 <p>In this example, the requests are named to reflect the order in which they will
be executed.  Timer #1 will apply to Requests Two, Three, and Four (notice how order is irrelevant
for hierarchical elements).  Assertion #1 will apply only to Request Three.  Timer #2 will
affect all the requests.</p>
-<p>Hopefully these examples make it clear how configuration (hierarchical) elements
are applied.  If you imagine each Request being passed up the tree branches, to its parent,
then to its parent's parent, etc, and each time collecting all the configuration elements
of that parent, then you will see how it works.  </p>
+<p>Hopefully these examples make it clear how configuration (hierarchical) elements
are applied.  If you imagine each Request being passed up the tree branches, to its parent,
then to its parent's parent, etc., and each time collecting all the configuration elements
of that parent, then you will see how it works.  </p>
 <b>
 The Configuration elements Header Manager, Cookie Manager and Authorization manager are
 treated differently from the Configuration Default elements.



Mime
View raw message