You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by se...@apache.org on 2007/07/07 23:38:13 UTC
svn commit: r554271 - in /jakarta/jmeter/branches/rel-2-2/xdocs: changes.xml
extending/index.xml usermanual/component_reference.xml
usermanual/ldapanswer_xml.xml
Author: sebb
Date: Sat Jul 7 14:38:12 2007
New Revision: 554271
URL: http://svn.apache.org/viewvc?view=rev&rev=554271
Log:
Fix minor typos.
Modified:
jakarta/jmeter/branches/rel-2-2/xdocs/changes.xml
jakarta/jmeter/branches/rel-2-2/xdocs/extending/index.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/ldapanswer_xml.xml
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/changes.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/changes.xml?view=diff&rev=554271&r1=554270&r2=554271
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/changes.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/changes.xml Sat Jul 7 14:38:12 2007
@@ -869,7 +869,7 @@
or FTP, RMI, SMTP, etc..). It is the code that actually makes the
connection to whatever is being tested. A SamplerController
represents code that understands how to organize and run a group
- of test samples. It is what binds together a Sampler and it's test
+ of test samples. It is what binds together a Sampler and its test
samples and runs them. A TestSample represents code that understands
how to gather information from the user about a particular test.
For a website, it would represent a URL and any information to be sent
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/extending/index.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/extending/index.xml?view=diff&rev=554271&r1=554270&r2=554271
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/extending/index.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/extending/index.xml Sat Jul 7 14:38:12 2007
@@ -196,7 +196,7 @@
config element for free (as in, you don't have to do anything!). <b>AbstractConfigElement</b>
-stores all it's values in a Map, and provides getProperty and putProperty methods. Your
+stores all its values in a Map, and provides getProperty and putProperty methods. Your
config element can provide <b>getXXX()</b> and <b>setXXX()</b> methods, but these should delegate
@@ -532,7 +532,7 @@
JMeter will call this method and hand the Saveable object to be saved (it will be
-the object that specified your TagHandler as the class responsible for it's saving).
+the object that specified your TagHandler as the class responsible for saving it).
This method should use the given Writer object to print all the XML necessary to
@@ -546,7 +546,7 @@
a tag that corresponds to your PrimaryTagName, an instance of your TagHandler will
-be created, and it's <b>setAtts()</b> method will get called. Thereafter, methods are called
+be created, and its <b>setAtts()</b> method will get called. Thereafter, methods are called
depending on subsequent tags and character data. For every tag, JMeter calls
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml?view=diff&rev=554271&r1=554270&r2=554271
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml Sat Jul 7 14:38:12 2007
@@ -1444,7 +1444,7 @@
<p>The Module Controller provides a mechanism for substituting test plan fragments into the current test plan at run-time. To use this
module effectively, one might have a number of Controllers under the <complink name="WorkBench" />, each with a different series of
samplers under them. The module controller can then be used to easily switch between these multiple test cases simply by choosing
-the appropriate controller in it's drop down box. This provides convenience for running many alternate test plans quickly and easily.
+the appropriate controller in its drop down box. This provides convenience for running many alternate test plans quickly and easily.
</p>
</description>
<note>The Module Controller should not be used with remote testing or non-gui testing in conjunction with Workbench components since the Workbench test elements are not part of test plan .jmx files. Any such test will fail.</note>
@@ -2953,10 +2953,10 @@
<properties>
<property name="Name" required="">Descriptive name for this element that is shown in the tree.</property>
<property name="Update Once Per Iteration" required="Yes">A flag to indicate whether the User Paramters element
- should update it's variables only once per iteration. if you embed functions into the UP, then you may need greater
+ should update its variables only once per iteration. if you embed functions into the UP, then you may need greater
control over how often the values of the variables are updated. Keep this box checked to ensure the values are
updated each time through the UP's parent controller. Uncheck the box, and the UP will update the parameters for
- every sample request made within it's <a href="build-test-plan.html#scoping_rules">scope</a>.</property>
+ every sample request made within its <a href="build-test-plan.html#scoping_rules">scope</a>.</property>
</properties>
</component>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/ldapanswer_xml.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/ldapanswer_xml.xml?view=diff&rev=554271&r1=554270&r2=554271
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/ldapanswer_xml.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/ldapanswer_xml.xml Sat Jul 7 14:38:12 2007
@@ -112,7 +112,7 @@
<li>
<countlimit>
This is the maximum number of searchresults that will be returned, as it is requested by the client.
-The actual number might be smaller as the server can have it's own countlimit configured.
+The actual number might be smaller as the server can have its own countlimit configured.
This will be used only in search requests.</li>
<li>
<dn>
@@ -140,7 +140,7 @@
<li>
<timelimit>
This is the maximum timethe server will use in finding the requested objects.as it is requested by the client.
-The actual number might be smaller as the server can have it's own countlimit configured.
+The actual number might be smaller as the server can have its own countlimit configured.
This will be used only in search requests.</li>
</ol>
-->
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org