jakarta-jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wool...@apache.org
Subject cvs commit: jakarta-jmeter/xdocs/usermanual component_reference.xml
Date Fri, 08 Oct 2004 04:37:52 GMT
woolfel     2004/10/07 21:37:52

  Modified:    xdocs/usermanual component_reference.xml
  Log:
  updated component documentation to have the right index number
  
  peter
  
  Revision  Changes    Path
  1.97      +89 -89    jakarta-jmeter/xdocs/usermanual/component_reference.xml
  
  Index: component_reference.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/component_reference.xml,v
  retrieving revision 1.96
  retrieving revision 1.97
  diff -u -r1.96 -r1.97
  --- component_reference.xml	7 Oct 2004 17:44:40 -0000	1.96
  +++ component_reference.xml	8 Oct 2004 04:37:52 -0000	1.97
  @@ -15,7 +15,7 @@
    * limitations under the License.
    * 
    -->
  -<document index="yes" index-level-2="yes" colbreak="15.4"
  +<document index="yes" index-level-2="yes" colbreak="16.4"
     prev="boss.html" next="functions.html" date="$Date$">
   
   <properties>
  @@ -34,11 +34,11 @@
   
    -->
   
  -<section name="15.1 Samplers" anchor="samplers">
  +<section name="16.1 Samplers" anchor="samplers">
   <description>
   	<br></br>
   </description>
  -<component name="FTP Request" index="15.1.1" screenshot="gen-controller/ftp-request.gif">
  +<component name="FTP Request" index="16.1.1" screenshot="gen-controller/ftp-request.gif">
   <description>This controller lets you send an FTP "retrieve file" request to an FTP
server.
   If you are going to send multiple requests to the same FTP server, consider
   using a <complink name="FTP Request Defaults"/> Configuration
  @@ -60,7 +60,7 @@
   
   </component>
   
  -<component name="HTTP Request" index="15.1.2" screenshot="gen-controller/http-request.png">
  +<component name="HTTP Request" index="16.1.2" screenshot="gen-controller/http-request.png">
   
   <description>
           <p>This sampler lets you send an HTTP/HTTPS request to a web server.  It
  @@ -136,7 +136,7 @@
   
   </component>
   
  -<component name="JDBC Request" index="15.1.3" screenshot="gen-controller/jdbc-request.gif">
  +<component name="JDBC Request" index="16.1.3" screenshot="gen-controller/jdbc-request.gif">
   
   <description><p>This sampler lets you send an JDBC Request (an SQL query) to
a database.</p>
   <p>If you are going to send multiple requests to the same database, consider
  @@ -174,7 +174,7 @@
   
   </component>
   
  -<component name="Java Request" index="15.1.4" screenshot="java_request.gif">
  +<component name="Java Request" index="16.1.4" screenshot="java_request.gif">
   
   <description><p>This sampler lets you control a java class that implements
the
   JavaSamplerClient interface.  By writing your own implementation of this interface,
  @@ -197,7 +197,7 @@
   
   </component>
   
  -<component name="SOAP/XML-RPC Request" index="15.1.5" screenshot="soap_sampler.png">
  +<component name="SOAP/XML-RPC Request" index="16.1.5" screenshot="soap_sampler.png">
   
   <description><p>This sampler lets you send a SOAP request to a webservice.
 It can also be
   used to send XML-RPC over HTTP.  It creates an HTTP POST request, with the specified XML
as the
  @@ -217,7 +217,7 @@
   
   </component>
   
  -<component name="LDAP Request" index="15.1.6" screenshot="ldap_request.png">
  +<component name="LDAP Request" index="16.1.6" screenshot="ldap_request.png">
     <description>This Sampler lets you send a different Ldap request(Add, Modify, Delete
and Search) to a LDAP server.
       <p>If you are going to send multiple requests to the same LDAP server, consider
         using an <complink name="LDAP Request Defaults"/>
  @@ -297,7 +297,7 @@
                                         </links>
   
   </component>
  -<component name="LDAP Extended Request" index="15.1.6b" screenshot="ldapext_request.png">
  +<component name="LDAP Extended Request" index="16.1.6b" screenshot="ldapext_request.png">
     <description>This Sampler can send all 8 different LDAP request to a LDAP server.
It is an extended version of the LDAP sampler,
     therefore it is harder to configure, but can be made much closer resembling a real LDAP
session.
       <p>If you are going to send multiple requests to the same LDAP server, consider
  @@ -426,7 +426,7 @@
   </component>
   
   
  -<component name="WebService(SOAP) Request (Beta Code)" index="15.1.7" screenshot="webservice_sampler.png">
  +<component name="WebService(SOAP) Request (Beta Code)" index="16.1.7" screenshot="webservice_sampler.png">
   
   <description><p>This sampler has been tested with IIS Webservice running .NET
1.0. It
    hasn't been tested with SUN or IBM webservices providers, but it should work.
  @@ -473,7 +473,7 @@
   
   </component>
   
  -<component name="Access Log Sampler" index="15.1.8" screenshot="">
  +<component name="Access Log Sampler" index="16.1.8" screenshot="">
   <center><h2>(Alpha Code)</h2></center>
   <description><p>AccessLogSampler was designed to read access logs and generate
http requests.
   For those not familiar with the access log, it is the log the webserver maintains of every
  @@ -526,7 +526,7 @@
   
   </component>
   
  -<component name="BeanShell Sampler" index="15.1.9" screenshot="">
  +<component name="BeanShell Sampler" index="16.1.9" screenshot="">
   <center><h2>(Beta Code)</h2></center>
   	<description><p>This sampler allows you to write a sampler using the BeanShell
scripting language.		
   </p><p>
  @@ -592,7 +592,7 @@
   </component>
   
   
  -<component name="BSF Sampler" index="15.1.10" screenshot="">
  +<component name="BSF Sampler" index="16.1.10" screenshot="">
   <center><h2>(ALPHA Code)</h2></center>
   	<description><p>This sampler allows you to write a sampler using a BSF scripting
language.<br></br>
   		
  @@ -611,7 +611,7 @@
   TBC
   </component>
   
  -<component name="TCP Sampler" index="15.1.11" screenshot="">
  +<component name="TCP Sampler" index="16.1.11" screenshot="">
   <description>TBA
   </description>
   <properties>
  @@ -619,7 +619,7 @@
   </properties>
   </component>
   
  -<component name="Test Action" index="15.1.12" screenshot="test_action.png">
  +<component name="Test Action" index="16.1.12" screenshot="test_action.png">
   <description>TBA
   </description>
   <properties>
  @@ -629,12 +629,12 @@
   
   </section>
   
  -<section name="15.2 Logic Controllers" anchor="logic_controllers">
  +<section name="16.2 Logic Controllers" anchor="logic_controllers">
   <description>
   	<br></br>
   </description>
   
  -<component index="15.2.1" name="Interleave Controller" screenshot="logic-controller/interleave-controller.png">
  +<component index="16.2.1" name="Interleave Controller" screenshot="logic-controller/interleave-controller.png">
   <description><p>If you add Generative or Logic Controllers to an Interleave
Controller, JMeter will alternate among each of the
   other controllers for each loop iteration. </p>
   </description>
  @@ -706,7 +706,7 @@
   </example>
   </component>
   
  -<component index="15.2.2" name="Loop Controller" anchor="loop" screenshot="logic-controller/loop-controller.gif">
  +<component index="16.2.2" name="Loop Controller" anchor="loop" screenshot="logic-controller/loop-controller.gif">
   <description><p>If you add Generative or Logic Controllers to a Loop Controller,
JMeter will
   loop through them a certain number of times, in addition to the loop value you
   specified for the Thread Group.  For example, if you add one HTTP Request to a
  @@ -745,7 +745,7 @@
   
   </component>
   
  -<component index="15.2.3" name="Once Only Controller" anchor="once_only_controller"
  +<component index="16.2.3" name="Once Only Controller" anchor="once_only_controller"
   screenshot="logic-controller/once-only-controller.gif">
   <description>
   <p>The Once Only Logic Controller tells JMeter to process the controller(s) inside
it only once, and pass over any requests under it
  @@ -773,7 +773,7 @@
   </example>
   </component>
   
  -<component index="15.2.4" name="Simple Controller" anchor="simple_controller" screenshot="logic-controller/simple-controller.gif">
  +<component index="16.2.4" name="Simple Controller" anchor="simple_controller" screenshot="logic-controller/simple-controller.gif">
   <description>
   <p>The Simple Logic Controller lets  you organize your Samplers and other
   Logic Controllers.  Unlike other Logic Controllers, this controller provides no functionality
beyond that of a
  @@ -797,7 +797,7 @@
   </example>
   </component>
   
  -<component index="15.2.5" name="Random Controller" screenshot="logic-controller/random-controller.gif">
  +<component index="16.2.5" name="Random Controller" screenshot="logic-controller/random-controller.gif">
   <description>
   <p>The Random Logic Controller acts similarly to the Interleave Controller, except
that
   instead of going in order through its sub-controllers and samplers, it picks one
  @@ -812,7 +812,7 @@
   
   </component>
   
  -<component index="15.2.6" name="Recording Controller" screenshot="logic-controller/recording-controller.gif">
  +<component index="16.2.6" name="Recording Controller" screenshot="logic-controller/recording-controller.gif">
   <description>
   <p>The Recording Controller is a place holder indicating where the proxy server should
   record samples to.  During test run, it has no effect, similar to the Simple Controller.
 But during
  @@ -826,7 +826,7 @@
   
   </component>
   
  -<component index="15.2.7" name="Module Controller" screenshot="module_controller.png">
  +<component index="16.2.7" name="Module Controller" screenshot="module_controller.png">
   <description>
   <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
  @@ -843,7 +843,7 @@
   
   </component>
   
  -<component index="15.2.8" name="Throughput Controller" screenshot="throughput_controller.png">
  +<component index="16.2.8" name="Throughput Controller" screenshot="throughput_controller.png">
   <description>
   <p>The Throughput Controller allows the user to control how often it is executed.
 There are two modes - percent execution and total executions.  Percent executions causes
the controller to execute a certain percentage of the iterations through the test plan.  Total
   executions causes the controller to stop executing after a certain number of executions
have occurred.  Like the Once Only Controller, this
  @@ -859,7 +859,7 @@
   </properties>
   
   </component>
  -<component name="If Controller" index="15.2.9" screenshot="">
  +<component name="If Controller" index="16.2.9" screenshot="">
   	<description>
   		<p>The If Controller allows the user to control whether the test elements below
it (its children) are run or not.</p>
   	</description>
  @@ -869,7 +869,7 @@
   </properties>
   </component>
   
  -<component name="Random Order Controller" index="15.2.10" screenshot="">
  +<component name="Random Order Controller" index="16.2.10" screenshot="">
   	<description>
   		<p>The Random Order Controller is much like a Simple Controller in that it will
execute each child
   		 element at most once, but the order of execution of the nodes will be random.</p>
  @@ -879,7 +879,7 @@
   </properties>
   </component>
   
  -<component name="ForEach Controller" index="15.2.11" anchor="loop" screenshot="logic-controller/foreach-controller.png">
  +<component name="ForEach Controller" index="16.2.11" anchor="loop" screenshot="logic-controller/foreach-controller.png">
   <description><p>A ForEach controller loops through the values of a set of related
variables. 
   When you add samplers (or controllers) to a ForEach controller, every sample sample (or
controller)
   is executed one or more times, where during every loop the variable has a new value.
  @@ -931,7 +931,7 @@
   
   </component>
   
  -<component name="Transaction Controller" index="15.2.12" screenshot="">
  +<component name="Transaction Controller" index="16.2.12" screenshot="">
   	<description>
   		<p>The Transaction Controller times how long it takes for all its children to run.
   			It then adds a "sample" entry to the test output with the total elapsed time.
  @@ -943,7 +943,7 @@
   </properties>
   </component>
   
  -<component name="Runtime Controller" index="15.2.12" screenshot="">
  +<component name="Runtime Controller" index="16.2.12" screenshot="">
   	<description>
   		<p>The Runtime Controller controls how long its children are allowed to run.
   		</p>
  @@ -956,7 +956,7 @@
   
   </section>
   
  -<section name="15.3 Listeners" anchor="listeners">
  +<section name="16.3 Listeners" anchor="listeners">
   <description>
   	<br></br>
   Most of the listeners perform several roles in addition to "listening"
  @@ -1049,7 +1049,7 @@
   	<br></br>
   
   </description>
  -<component index="15.3.1" name="Mailer Visualizer" screenshot="mailer_vis.png">
  +<component index="16.3.1" name="Mailer Visualizer" screenshot="mailer_vis.png">
   <description><p>The mailer visualizer can be set up to send email if a test
run receives too many
   failed responses from the server.</p></description>
   
  @@ -1072,11 +1072,11 @@
   </properties>
   </component>
   
  -<component index="15.3.2" name="Graph Full Results" screenshot="">
  +<component index="16.3.2" name="Graph Full Results" screenshot="">
   <description>No Description</description>
   </component>
   
  -<component index="15.3.3" name="Graph Results" screenshot="graph_results.png">
  +<component index="16.3.3" name="Graph Results" screenshot="graph_results.png">
   <description><p>The Graph Results listener generates a simple graph that plots
all sample times.  Along
   the bottom of the graph, the current sample (black), the current average of all samples(blue),
the
   current standard deviation (red), and the current throughput rate (green) are displayed
in milliseconds.</p>
  @@ -1089,14 +1089,14 @@
   number.</p></description>
   </component>
   
  -<component index="15.3.4" name="Spline Visualizer" screenshot="spline_visualizer.png">
  +<component index="16.3.4" name="Spline Visualizer" screenshot="spline_visualizer.png">
   <description><p>The Spline Visualizer provides a view of all sample times from
the start
   of the test till the end, regardless of how many samples have been taken.  The spline
   has 10 points, each representing 10% of the samples, and connected using spline
   logic to show a single continuous line.</p></description>
   </component>
   
  -<component index="15.3.5" name="Assertion Results" screenshot="assertion_results.png">
  +<component index="16.3.5" name="Assertion Results" screenshot="assertion_results.png">
   <description><p>The Assertion Results visualizer shows the URL of each sample
taken (no time information
   is shown).  It also reports failures of any <a href="test_plan.html#assertions">Assertions</a>
that
   are part of the test plan.</p></description>
  @@ -1106,7 +1106,7 @@
   </links>
   </component>
   
  -<component index="15.3.6" name="View Results Tree" screenshot="view_results_tree.png">
  +<component index="16.3.6" name="View Results Tree" screenshot="view_results_tree.png">
   <description>The View Results Tree shows a tree of all sample responses, allowing
you to view the
   response for any sample.  In addition to showing the response, you can see the time it
took to get
   this response, and some response codes.
  @@ -1120,25 +1120,25 @@
   </description>
   </component>
   
  -<component index="15.3.7" name="Aggregate Report" screenshot="aggregate_report.png">
  +<component index="16.3.7" name="Aggregate Report" screenshot="aggregate_report.png">
   <description>The aggregate report creates a table row for each differently named
request in your test.  For each
   request, it totals the response information and provides request count, min, max, average,
error rate, and an
   idealized throughput calculation.</description>
   </component>
   
  -<component index="15.3.8" name="View Results in Table" screenshot="table_results.png">
  +<component index="16.3.8" name="View Results in Table" screenshot="table_results.png">
   <description>This visualizer creates a row for every sample result.  Each sample
result's URL,
   time in milliseconds, success/failure is displayed.  Like the <complink name="View Results
Tree"/>,
   this visualizer uses a lot of memory.</description>
   </component>
   
  -<component index="15.3.9" name="Simple Data Writer" screenshot="">
  +<component index="16.3.9" name="Simple Data Writer" screenshot="">
   <description>This listener can record results to a file
   but not to the UI.  It is meant to provide an efficient means of
   recording data by eliminating GUI overhead.</description>
   </component>
   
  -<component index="15.3.10" name="Monitor Results" screenshot="monitor_screencap.png">
  +<component index="16.3.10" name="Monitor Results" screenshot="monitor_screencap.png">
   <description>
   <p>Monitor Results is a new Visualizer for displaying server
   status. It is designed for Tomcat 5, but any servlet container
  @@ -1161,7 +1161,7 @@
   </description>
   </component>
   
  -<component index="15.3.11" name="Distribution Graph (alpha)" screenshot="distribution_graph.png">
  +<component index="16.3.11" name="Distribution Graph (alpha)" screenshot="distribution_graph.png">
   <description>
   <p>The distribution graph will display a bar for every unique response time. Since
the
   granularity of System.currentTimeMillis() is 10 milliseconds, the 90% threshold should
be
  @@ -1182,7 +1182,7 @@
   
   </section>
   
  -<section name="15.4 Configuration Elements" anchor="config_elements">
  +<section name="16.4 Configuration Elements" anchor="config_elements">
   <description>
   	<br></br>
   	Configuration elements can be used to set up defaults and variables for later use by samplers.
  @@ -1190,7 +1190,7 @@
   	i.e. before any samplers in the same scope.
   	<br></br>
   </description>
  -<component index="15.4.1" name="HTTP Authorization Manager" screenshot="http-config/http-auth-manager.gif">
  +<component index="16.4.1" name="HTTP Authorization Manager" screenshot="http-config/http-auth-manager.gif">
   
   <description>
   <p>The Authorization Manager lets you specify one or more user logins for web pages
that are
  @@ -1249,7 +1249,7 @@
   
   </component>
   
  -<component index="15.4.2" name="HTTP Cookie Manager" screenshot="http-config/http-cookie-manager.gif">
  +<component index="16.4.2" name="HTTP Cookie Manager" screenshot="http-config/http-cookie-manager.gif">
   
   <description><p>The Cookie Manager element has two functions:<br></br>
   First, it stores and sends cookies just like a web browser. If you have an HTTP Request
and
  @@ -1275,7 +1275,7 @@
   
   </component>
   
  -<component index="15.4.3" name="HTTP Proxy Server" screenshot="proxy_control.png">
  +<component index="16.4.3" name="HTTP Proxy Server" screenshot="proxy_control.png">
   
   <description><p>The Proxy Server allows JMeter to watch and record your actions
while you browse your web application
   with your normal browser (such as Internet Explorer).  JMeter will create test sample objects
and store them
  @@ -1371,7 +1371,7 @@
   
   </component>
   
  -<component index="15.4.4" name="HTTP Request Defaults"
  +<component index="16.4.4" name="HTTP Request Defaults"
           screenshot="http-config/http-request-defaults.png">
   <description><p>This element lets you set default values that your HTTP Request
controllers use.  For example, if you are
   creating a Test Plan with 25 HTTP Request controllers and all of the requests are being
sent to the same server,
  @@ -1399,19 +1399,19 @@
   </properties>
   </component>
   
  -<component index="15.4.5" name="FTP Request Defaults"
  +<component index="16.4.5" name="FTP Request Defaults"
                   screenshot="ftp-config/ftp-request-defaults.gif">
   <description></description>
   </component>
   
  -<component index="15.4.6" name="JDBC Connection Configuration"
  +<component index="16.4.6" name="JDBC Connection Configuration"
                   screenshot="jdbc-config/jdbc-conn-config.png">
   	<description>Defines the JDBC Connection settings to be used by 
   		the <complink name="JDBC Request"/>Sampler.
   	</description>
   </component>
   
  -<component index="15.4.7" name="JDBC SQL Query Defaults"
  +<component index="16.4.7" name="JDBC SQL Query Defaults"
   	screenshot="jdbc-config/jdbc-sql-query.png">
   <description>Defines a default query for the <complink name="JDBC Request"/>Sampler.
   	<br></br>
  @@ -1419,13 +1419,13 @@
   	</description>
   </component>
   
  -<component index="15.4.8" name="Mail Reader Sampler">
  +<component index="16.4.8" name="Mail Reader Sampler">
   <description>TBA</description>
   </component>
   
   
   
  -<component index="15.4.9" name="HTTP Header Manager" screenshot="http-config/http-header-manager.gif">
  +<component index="16.4.9" name="HTTP Header Manager" screenshot="http-config/http-header-manager.gif">
   <description><p>The Header Manager lets you add or override HTTP request headers.</p>
   </description>
   
  @@ -1454,7 +1454,7 @@
   
   </component>
   
  -<component index="15.4.10" name="Login Config Element" screenshot="login-config.png">
  +<component index="16.4.10" name="Login Config Element" screenshot="login-config.png">
   <description><p>The Login Config Element lets you add or override username
and password settings in samplers that use username and password as part of their setup.</p>
   </description>
   
  @@ -1466,7 +1466,7 @@
   
   </component>
   
  -<component index="15.4.11" name="Simple Config Element" screenshot="simple_config_element.png">
  +<component index="16.4.11" name="Simple Config Element" screenshot="simple_config_element.png">
   <description><p>The Simple Config Element lets you add or override arbitrary
values in samplers.  You can choose the name of the value
   and the value itself.  Although some adventurous users might find a use for this element,
it's here primarily for developers as a basic
   GUI that they can use while developing new JMeter components.</p>
  @@ -1481,26 +1481,26 @@
   
   </component>
   
  -<component index="15.4.12" name="LDAP Request Defaults" screenshot="ldap_defaults.png">
  +<component index="16.4.12" name="LDAP Request Defaults" screenshot="ldap_defaults.png">
   <description><p>The LDAP Request Defaults component lets you set default values
for LDAP testing.  See the <complink name="LDAP Request"/>.</p>
   </description>
   
   </component>
   
  -<component index="15.4.12b" name="LDAP Extended Request Defaults" screenshot="ldapext_defaults.png">
  +<component index="16.4.12b" name="LDAP Extended Request Defaults" screenshot="ldapext_defaults.png">
   <description><p>The LDAP Extended Request Defaults component lets you set default
values for extended LDAP testing.  See the <complink name="LDAP Extended Request"/>.</p>
   </description>
   
   </component>
   
   
  -<component index="15.4.13" name="Java Request Defaults" screenshot="java_defaults.png">
  +<component index="16.4.13" name="Java Request Defaults" screenshot="java_defaults.png">
   <description><p>The Java Request Defaults component lets you set default values
for Java testing.  See the <complink name="Java Request"/>.</p>
   </description>
   
   </component>
   
  -<component index="15.4.14" name="User Defined Variables" screenshot="user_defined_variables.png">
  +<component index="16.4.14" name="User Defined Variables" screenshot="user_defined_variables.png">
   <description><p>The User Defined Variables lets you define variables for use
in other test elements, just as in the <complink name="Test Plan"/>.
   The variables in User Defined Variables components will take precedence over those defined
closer to the tree root -- including those defined in the Test Plan.</p>
   </description>
  @@ -1512,7 +1512,7 @@
   </properties>
   </component>
   
  -<component index="15.4.15" name="TCP Sampler Config" screenshot="">
  +<component index="16.4.15" name="TCP Sampler Config" screenshot="">
   <description>ALPHA Code
   </description>
   <properties>
  @@ -1522,14 +1522,14 @@
   
   </section>
   
  -<section name="15.5 Assertions" anchor="assertions">
  +<section name="16.5 Assertions" anchor="assertions">
   <description>
   	<br></br>
   	Assertions are used to perform additional checks on samplers, and are processed after
<b>each sampler</b>
   	in the same scope.
   	<br></br>
   </description>
  -<component index="15.5.1" name="Response Assertion" anchor="basic_assertion" screenshot="assertion/assertion.gif">
  +<component index="16.5.1" name="Response Assertion" anchor="basic_assertion" screenshot="assertion/assertion.gif">
   
   <description><p>The response assertion control panel lets you add pattern strings
to be compared against various
   	fields of the response.
  @@ -1584,7 +1584,7 @@
   
   </component>
   
  -<component index="15.5.2" name="Duration Assertion" screenshot="duration_assertion.png">
  +<component index="16.5.2" name="Duration Assertion" screenshot="duration_assertion.png">
   <description><p>The Duration Assertion tests that each response was received
within a given amount
   of time.  Any response that takes longer than the given number of milliseconds (specified
by the
   user) is marked as a failed response.</p></description>
  @@ -1597,7 +1597,7 @@
   </properties>
   </component>
   
  -<component index="15.5.3" name="Size Assertion" screenshot="size_assertion.png">
  +<component index="16.5.3" name="Size Assertion" screenshot="size_assertion.png">
   <description><p>The Size Assertion tests that each response contains the right
number of bytes in it.  You can specify that
   the size be equal to, greater than, less than, or not equal to a given number of bytes.</p></description>
   
  @@ -1610,7 +1610,7 @@
   </properties>
   </component>
   
  -<component index="15.5.4" name="XML Assertion" screenshot="xml_assertion.png">
  +<component index="16.5.4" name="XML Assertion" screenshot="xml_assertion.png">
   <description><p>The XML Assertion tests that the response data consists of
a formally correct XML document.  It does not
   validate the XML based on a DTD or schema or do any further validation.</p></description>
   
  @@ -1620,7 +1620,7 @@
   </properties>
   </component>
   
  -<component index="15.5.5" name="BeanShell Assertion" screenshot="bsh_assertion.png">
  +<component index="16.5.5" name="BeanShell Assertion" screenshot="bsh_assertion.png">
   <description><p>The BeanShell Assertion allows the user to perform assertion
checking using a BeanShell script.</p></description>
   
   <properties>
  @@ -1650,7 +1650,7 @@
   </p>
   </component>
   
  -<component index="15.5.6" name="MD5Hex Assertion">
  +<component index="16.5.6" name="MD5Hex Assertion">
   <description><p>The MD5Hex Assertion allows the user to check the MD5 hash
of the response data.</p></description>
   
   <properties>
  @@ -1660,7 +1660,7 @@
   </properties>
   </component>
   
  -<component index="15.5.7" name="HTML Assertion" screenshot="assertion/HTMLAssertion.png">
  +<component index="16.5.7" name="HTML Assertion" screenshot="assertion/HTMLAssertion.png">
   <description><p>The HTML Assertion allows the user to check the HTML syntax
of the response data using JTidy.</p></description>
   
   <properties>
  @@ -1677,7 +1677,7 @@
   
   </section>
   
  -<section name="15.6 Timers" anchor="timers">
  +<section name="16.6 Timers" anchor="timers">
   <description>
   	<br></br>
   	Note that timers are processed at the start of the scope in which they are found;
  @@ -1688,7 +1688,7 @@
   	child of a simple logic controller immediately after the sampler.
   	<br></br>
   </description>
  -<component index="15.6.1" name="Constant Timer" anchor="constant" screenshot="timers/constant_timer.gif">
  +<component index="16.6.1" name="Constant Timer" anchor="constant" screenshot="timers/constant_timer.gif">
   <description>
   <p>If you want to have each thread pause for the same amount of time between
   requests, use this timer.</p></description>
  @@ -1699,7 +1699,7 @@
   </properties>
   </component>
   
  -<component index="15.6.2" name="Gaussian Random Timer" screenshot="timers/gauss_random_timer.gif">
  +<component index="16.6.2" name="Gaussian Random Timer" screenshot="timers/gauss_random_timer.gif">
   
   <description><p>This timer pauses each thread request for a random amount of
time, with most
   of the time intervals ocurring near a particular value.  The total delay is the
  @@ -1716,7 +1716,7 @@
   
   </component>
   
  -<component index="15.6.3" name="Uniform Random Timer" screenshot="timers/uniform_random_timer.gif">
  +<component index="16.6.3" name="Uniform Random Timer" screenshot="timers/uniform_random_timer.gif">
   
   <description><p>This timer pauses each thread request for a random amount of
time, with
   each time interval having the same probability of occurring. The total delay
  @@ -1732,7 +1732,7 @@
   
   </component>
   
  -<component index="15.6.4" name="Constant Throughput Timer" screenshot="timers/constant_throughput_timer.gif">
  +<component index="16.6.4" name="Constant Throughput Timer" screenshot="timers/constant_throughput_timer.gif">
   
   <description><p>This timer introduces variable pauses, calculated to keep the
total throughput (in terms of samples per minute) as close as possible to a give figure. Of
course the throughput will be lower if the server is not capable of handling it, or if other
timers or time-consuming test elements prevent it.</p>
   
  @@ -1746,13 +1746,13 @@
   </component>
   </section>
   
  -<section name="15.7 Pre Processors" anchor="preprocessors">
  +<section name="16.7 Pre Processors" anchor="preprocessors">
   	<description>
   	<br></br>
   		Preprocessors are used to modify the Samplers in their scope.
   	<br></br>
   	</description>
  -<component index="15.7.1" name="HTML Link Parser" anchor="html_link_parser">
  +<component index="16.7.1" name="HTML Link Parser" anchor="html_link_parser">
   <description>
   <p>This modifier parses HTML response from the server and extracts
   links and forms.  A URL test sample that passes through this modifier will be examined
to
  @@ -1802,7 +1802,7 @@
   
   </component>
   
  -<component index="15.7.2" name="HTTP URL Re-writing Modifier" screenshot="url_rewriter.png">
  +<component index="16.7.2" name="HTTP URL Re-writing Modifier" screenshot="url_rewriter.png">
   <description><p>This modifier works similarly to the HTML Link Parser, except
it has a specific purpose for which
   it is easier to use than the HTML Link Parser, and more efficient.  For web applications
that
   use URL Re-writing to store session ids instead of cookies, this element can be attached
at the
  @@ -1826,7 +1826,7 @@
   </properties>
   </component>
   
  -<component index="15.7.3" name="HTML Parameter Mask" useinstead="Counter" screenshot="parameter_mask.png">
  +<component index="16.7.3" name="HTML Parameter Mask" useinstead="Counter" screenshot="parameter_mask.png">
   <description><p>The HTML Parameter Mask is used to generate unique values for
HTML arguments.  By
   specifying the name of the parameter, a value prefix and suffix, and counter parameters,
this
   modifier will generate values of the form "<code>name=prefixcountersuffix</code>".
 Any HTTP
  @@ -1854,7 +1854,7 @@
   </properties>
   </component>
   
  -<component index="15.7.4" name="HTTP User Parameter Modifier" useinstead="User Parameters"
screenshot="user_param_modifier.gif">
  +<component index="16.7.4" name="HTTP User Parameter Modifier" useinstead="User Parameters"
screenshot="user_param_modifier.gif">
   <description><p>The User Parameter Modifier uses an XML file get values for
HTTP arguments.  Any
   HTTP Request that this modifier modifies will be checked for the existence of the specified
   arguments.  If found, the values for those arguments will be replaced by the values found
in the
  @@ -1873,7 +1873,7 @@
   </properties>
   </component>
   
  -<component index="15.7.5" name="User Parameters" screenshot="user_params.png">
  +<component index="16.7.5" name="User Parameters" screenshot="user_params.png">
   <description><p>Allows the user to specify values for User Variables specific
to individual threads.</p>
   <p>User Variables can also be specified in the Test Plan but not specific to individual
threads. This panel allows
   you to specify a series of values for any User Variable. For each thread, the variable
will be assigned one of the values from the series
  @@ -1897,7 +1897,7 @@
   </properties>
   </component>
   
  -<component index="15.7.6" name="Counter" screenshot="counter.png">
  +<component index="16.7.6" name="Counter" screenshot="counter.png">
   <description><p>Allows the user to create a counter that can be referenced
anywhere
   in the Thread Group.  The counter config lets the user configure a starting point, a maximum,
   and the increment.  The counter will loop from the start to the max, and then start over
  @@ -1919,7 +1919,7 @@
   
   </section>
   
  -<section name="15.8 Post-Processors" anchor="postprocessors">
  +<section name="16.8 Post-Processors" anchor="postprocessors">
   	<description>
   	<br></br>
   		As the name suggests, Post-Processors are applied after samplers. Note that they are
  @@ -1927,7 +1927,7 @@
   		is applied only to a particular sampler, add it as a child of the sampler.
   	<br></br>
   	</description>
  -<component index="15.8.1" name="Regular Expression Extractor" screenshot="regex_extractor.png">
  +<component index="16.8.1" name="Regular Expression Extractor" screenshot="regex_extractor.png">
   <description><p>Allows the user to extract values from a server response using
a Perl-type regular expression.  As a post-processor,
   this element will execute after each Sample request in its <scope/>, applying the
regular expression, extracting the requested values,
   generate the template string, and store the result into the given variable name.</p></description>
  @@ -1962,7 +1962,7 @@
   </p>
   </component>
   
  -<component index="15.8.2" name="Result Status Action Handler" screenshot="resultstatusactionhandler.png">
  +<component index="16.8.2" name="Result Status Action Handler" screenshot="resultstatusactionhandler.png">
      <description>This test element allows the user to stop the thread or the whole
test if the relevant sampler failed.
      </description>
      <properties>
  @@ -1970,7 +1970,7 @@
      </properties>
   </component>
   
  -<component index="15.8.3" name="Save Responses to a file" screenshot="savetofile.png">
  +<component index="16.8.3" name="Save Responses to a file" screenshot="savetofile.png">
   	<description>This test element can be placed anywhere in the test plan.
   		For each sample in its scope, it will create a file of the response Data.
   		The primary use for this is in creating functional tests.
  @@ -1983,7 +1983,7 @@
    </properties>
   </component>
   
  -<component index="15.8.4" name="Generate Summary Results" screenshot="summary.png">
  +<component index="16.8.4" name="Generate Summary Results" screenshot="summary.png">
   	<description>This test element can be placed anywhere in the test plan.
   Generates a summary of the test run so far to the log file and/or 
   standard output. Both running and differential totals are shown.
  @@ -2000,15 +2000,15 @@
   
   </section>
   
  -<section name="15.9 Miscellaneous Features" anchor="Miscellaneous_Features">
  +<section name="16.9 Miscellaneous Features" anchor="Miscellaneous_Features">
   <description>
   		<br></br>
   </description>
  -<component index="15.9.1" name="Test Plan" screenshot="testplan.png">
  +<component index="16.9.1" name="Test Plan" screenshot="testplan.png">
   <description><p>At the Test Plan level, static variables can be defined that
allow users to abstract values that are repeated throughout their tests, such as server names.
 Here, one can instruct JMeter to save the maximum sample information to file by selecting
"functional testing".  Also, an option exists here to instruct JMeter to run the <complink
name="Thread Group"/> serially rather than in parallel.</p></description>
   </component>
   
  -<component index="15.9.2" name="Thread Group" screenshot="threadgroup.png">
  +<component index="16.9.2" name="Thread Group" screenshot="threadgroup.png">
   <description><p>A Thread Group defines a pool of users that will execute a
particular test case against your server.  In the Thread Group GUI, you can control the number
of users simulated (num of threads), the ramp up time (how long it takes to start all the
threads), the number of times to perform the test, and optionally, a start and stop time for
the test.</p></description>
   
   <properties>
  @@ -2033,11 +2033,11 @@
   </properties>
   </component>
   
  -<component index="15.9.3" name="WorkBench" screenshot="workbench.png">
  +<component index="16.9.3" name="WorkBench" screenshot="workbench.png">
   <description><p>The WorkBench simply provides a place to temporarily store
test elements while not in use, for copy/paste purposes, or any other purpose you desire.
 When you save your test plan, WorkBench items are not saved with it.  Your WorkBench can
be saved independently, if you like (right-click on WorkBench and choose Save).</p></description>
   </component>
   
  -<component index="15.9.4" name="SSL Manager" screenshot="">
  +<component index="16.9.4" name="SSL Manager" screenshot="">
   <p>
     The SSL Manager is a way to select a client certificate so that you can test
     applications that use Public Key Infrastructure (PKI).  In order to use it,
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org


Mime
View raw message