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 2006/03/26 14:36:17 UTC
svn commit: r388901 - in /jakarta/jmeter/branches/rel-2-1/xdocs: changes.xml
usermanual/component_reference.xml
Author: sebb
Date: Sun Mar 26 04:36:17 2006
New Revision: 388901
URL: http://svn.apache.org/viewcvs?rev=388901&view=rev
Log:
Remove SQL Config GUI documentation
Re-order Configuration section
Modified:
jakarta/jmeter/branches/rel-2-1/xdocs/changes.xml
jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/component_reference.xml
Modified: jakarta/jmeter/branches/rel-2-1/xdocs/changes.xml
URL: http://svn.apache.org/viewcvs/jakarta/jmeter/branches/rel-2-1/xdocs/changes.xml?rev=388901&r1=388900&r2=388901&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-1/xdocs/changes.xml (original)
+++ jakarta/jmeter/branches/rel-2-1/xdocs/changes.xml Sun Mar 26 04:36:17 2006
@@ -117,6 +117,7 @@
<li>Expanded user documentation</li>
<li>Added MANIFEST, NOTICE and LICENSE to all jars</li>
<li>Extract htmlparser interface into separate jarfile to make it possible to replace the parser</li>
+<li>Removed SQL Config GUI as no longer needed (or working!)</li>
</ul>
<hr/>
Modified: jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewcvs/jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/component_reference.xml?rev=388901&r1=388900&r2=388901&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/component_reference.xml (original)
+++ jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/component_reference.xml Sun Mar 26 04:36:17 2006
@@ -172,7 +172,6 @@
<link href="test_plan.html#assertions">Assertion</link>
<link href="build-db-test-plan.html">Building a Database Test Plan</link>
<complink name="JDBC Connection Configuration"/>
- <complink name="JDBC SQL Query Defaults"/>
</links>
</component>
@@ -1635,7 +1634,34 @@
i.e. before any samplers in the same scope.
<br></br>
</description>
-<component name="HTTP Authorization Manager" index="§-num;.4.1" screenshot="http-config/http-auth-manager.gif">
+
+<component name="CSV Data Set Config" index="§-num;.4.1" screenshot="csvdatasetconfig.png">
+<description>
+ <p>
+ CSV DataSet Config is used to read lines from a file, and split them into variables.
+ It is easier to use than the __CSVRead() and _StringFromFile() functions.
+ </p>
+ <p>
+ As a special case, the string "\t" (without quotes) is treated as a Tab.
+ </p>
+</description>
+<properties>
+ <property name="Name" required="">Descriptive name for this element that is shown in the tree.</property>
+ <property name="Filename" required="Yes">Name of the file to be read.
+ Relative file names are resolved with respect to the current test plan.
+ Absolute file names are also supported, but note that they are unlikely to work in remote mode,
+ unless the remote server has the same directory structure.
+ </property>
+ <property name="Variable Names" required="Yes">List of variable names (comma-delimited)</property>
+ <property name="Delimiter" required="Yes">Delimiter to be used to split the records in the file.</property>
+</properties>
+</component>
+
+<component name="FTP Request Defaults" index="§-num;.4.2" screenshot="ftp-config/ftp-request-defaults.gif">
+<description></description>
+</component>
+
+<component name="HTTP Authorization Manager" index="§-num;.4.3" screenshot="http-config/http-auth-manager.gif">
<note>If there is more than one Authorization Manager in the scope of a Sampler,
there is currently no way to sepcify which one is to be used.</note>
@@ -1701,7 +1727,7 @@
</component>
-<component name="HTTP Cookie Manager" index="§-num;.4.2" screenshot="http-config/http-cookie-manager.png">
+<component name="HTTP Cookie Manager" index="§-num;.4.4" screenshot="http-config/http-cookie-manager.png">
<note>If there is more than one Cookie Manager in the scope of a Sampler,
there is currently no way to specify which one is to be used.</note>
@@ -1735,7 +1761,7 @@
</component>
-<component name="HTTP Proxy Server" index="§-num;.4.3" screenshot="proxy_control.png">
+<component name="HTTP Proxy Server" index="§-num;.4.5" screenshot="proxy_control.png">
<note>The Proxy Server can only record HTTP traffic.
There is currently no support for recording HTTPS (SSL) sessions.</note>
<description><p>The Proxy Server allows JMeter to watch and record your actions while you browse your web application
@@ -1851,7 +1877,7 @@
</component>
-<component name="HTTP Request Defaults" index="§-num;.4.4"
+<component name="HTTP Request Defaults" index="§-num;.4.6"
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,
@@ -1879,12 +1905,45 @@
</properties>
</component>
-<component name="FTP Request Defaults" index="§-num;.4.5"
- screenshot="ftp-config/ftp-request-defaults.gif">
-<description></description>
+<component name="HTTP Header Manager" index="§-num;.4.7" screenshot="http-config/http-header-manager.gif">
+<note>If there is more than one Header Manager in the scope of a Sampler,
+there is currently no way to sepcify which one is to be used.</note>
+
+<description><p>The Header Manager lets you add or override HTTP request headers.</p>
+</description>
+
+<properties>
+ <property name="Name" required="No">Descriptive name for this element that is shown in the tree. </property>
+ <property name="Name (Header)" required="No (You should have at least one, however)">Name of the request header.
+ Two common request headers you may want to experiment with
+are "User-Agent" and "Referer".</property>
+ <property name="Value" required="No (You should have at least one, however)">Request header value.</property>
+ <property name="Add Button" required="N/A">Add an entry to the header table.</property>
+ <property name="Delete Button" required="N/A">Delete the currently selected table entry.</property>
+ <property name="Load Button" required="N/A">Load a previously saved header table and add the entries to the existing
+header table entries.</property>
+ <property name="Save As Button" required="N/A">Save the current header table to a file.</property>
+</properties>
+
+<example title="Header Manager example" anchor="header_manager_example">
+
+<p><a href="../demos/HeaderManagerTestPlan.jmx">Download</a> this example. In this example, we created a Test Plan
+that tells JMeter to override the default "User-Agent" request header and use a particular Internet Explorer agent string
+instead. (see figures 9 and 10).</p>
+
+<figure image="http-config/header-manager-example1a.gif">Figure 12 - Test Plan</figure>
+<figure image="http-config/header-manager-example1b.gif">Figure 13 - Header Manager Control Panel</figure>
+</example>
+
</component>
-<component name="JDBC Connection Configuration" index="§-num;.4.6"
+<component name="Java Request Defaults" index="§-num;.4.8" 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 name="JDBC Connection Configuration" index="§-num;.4.9"
screenshot="jdbc-config/jdbc-conn-config.png">
<description>Creates a database connection pool (used by <complink name="JDBC Request"/>Sampler)
with JDBC Connection settings.
@@ -1911,47 +1970,22 @@
</properties>
</component>
-<component name="JDBC SQL Query Defaults" index="§-num;.4.7"
- screenshot="jdbc-config/jdbc-sql-query.png">
-<description>Defines a default query for the <complink name="JDBC Request"/>Sampler.
- <br></br>
- Connection settings are defined by the <complink name="JDBC Connection Configuration"/>element.
- </description>
-</component>
-
-<component name="HTTP Header Manager" index="§-num;.4.8" screenshot="http-config/http-header-manager.gif">
-<note>If there is more than one Header Manager in the scope of a Sampler,
-there is currently no way to sepcify which one is to be used.</note>
-
-<description><p>The Header Manager lets you add or override HTTP request headers.</p>
+<component name="JNDI Default Configuration" index="§-num;.4.10" screenshot="jndi_config.png">
+<description>
+ <p>
+ TBA.
+ </p>
</description>
-
<properties>
- <property name="Name" required="No">Descriptive name for this element that is shown in the tree. </property>
- <property name="Name (Header)" required="No (You should have at least one, however)">Name of the request header.
- Two common request headers you may want to experiment with
-are "User-Agent" and "Referer".</property>
- <property name="Value" required="No (You should have at least one, however)">Request header value.</property>
- <property name="Add Button" required="N/A">Add an entry to the header table.</property>
- <property name="Delete Button" required="N/A">Delete the currently selected table entry.</property>
- <property name="Load Button" required="N/A">Load a previously saved header table and add the entries to the existing
-header table entries.</property>
- <property name="Save As Button" required="N/A">Save the current header table to a file.</property>
+ <property name="Name" required="">Descriptive name for this element that is shown in the tree.</property>
+ <property name="Initial Context Factory" required="No">TBA</property>
+ <property name="Provider URL" required="No">TBA</property>
</properties>
+</component>
-<example title="Header Manager example" anchor="header_manager_example">
-
-<p><a href="../demos/HeaderManagerTestPlan.jmx">Download</a> this example. In this example, we created a Test Plan
-that tells JMeter to override the default "User-Agent" request header and use a particular Internet Explorer agent string
-instead. (see figures 9 and 10).</p>
-
-<figure image="http-config/header-manager-example1a.gif">Figure 12 - Test Plan</figure>
-<figure image="http-config/header-manager-example1b.gif">Figure 13 - Header Manager Control Panel</figure>
-</example>
-</component>
-<component name="Login Config Element" index="§-num;.4.9" screenshot="login-config.png">
+<component name="Login Config Element" index="§-num;.4.11" 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>
@@ -1963,53 +1997,21 @@
</component>
-<component name="Simple Config Element" index="§-num;.4.10" 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>
-</description>
-
-<properties>
- <property name="Name" required="No">Descriptive name for this element that is shown in the tree. </property>
- <property name="Parameter Name" required="Yes">The name of each parameter. These values are internal to JMeter's workings and
- are not generally documented. Only those familiar with the code will know these values.</property>
- <property name="Parameter Value" required="Yes">The value to apply to that parameter.</property>
-</properties>
-</component>
-<component name="LDAP Request Defaults" index="§-num;.4.11" screenshot="ldap_defaults.png">
+<component name="LDAP Request Defaults" index="§-num;.4.12" 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 name="LDAP Extended Request Defaults (ALPHA)" index="§-num;.4.12" screenshot="ldapext_defaults.png">
+<component name="LDAP Extended Request Defaults (ALPHA)" index="§-num;.4.13" 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 (ALPHA)"/>.</p>
</description>
</component>
-
-<component name="Java Request Defaults" index="§-num;.4.13" 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 name="User Defined Variables" index="§-num;.4.14" 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>
-<properties>
- <property name="Name" required="">Descriptive name for this element that is shown in the tree.</property>
- <property name="User Defined Variables" required="">Variable name/value pairs. The string under the "Name"
- column is what you'll need to place inside the brackets in ${...} constructs to use the variables later on. The
- whole ${...} will then be replaced by the string in the "Value" column.</property>
-</properties>
-</component>
-
-<component name="TCP Sampler Config" index="§-num;.4.15" screenshot="tcpsamplerconfig.png">
+<component name="TCP Sampler Config" index="§-num;.4.14" screenshot="tcpsamplerconfig.png">
<note>ALPHA CODE</note>
<description>
<p>
@@ -2026,39 +2028,31 @@
</properties>
</component>
-<component name="CSV Data Set Config" index="§-num;.4.16" screenshot="csvdatasetconfig.png">
-<description>
- <p>
- CSV DataSet Config is used to read lines from a file, and split them into variables.
- It is easier to use than the __CSVRead() and _StringFromFile() functions.
- </p>
- <p>
- As a special case, the string "\t" (without quotes) is treated as a Tab.
- </p>
+<component name="User Defined Variables" index="§-num;.4.15" 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>
<properties>
<property name="Name" required="">Descriptive name for this element that is shown in the tree.</property>
- <property name="Filename" required="Yes">Name of the file to be read.
- Relative file names are resolved with respect to the current test plan.
- Absolute file names are also supported, but note that they are unlikely to work in remote mode,
- unless the remote server has the same directory structure.
- </property>
- <property name="Variable Names" required="Yes">List of variable names (comma-delimited)</property>
- <property name="Delimiter" required="Yes">Delimiter to be used to split the records in the file.</property>
+ <property name="User Defined Variables" required="">Variable name/value pairs. The string under the "Name"
+ column is what you'll need to place inside the brackets in ${...} constructs to use the variables later on. The
+ whole ${...} will then be replaced by the string in the "Value" column.</property>
</properties>
</component>
-<component name="JNDI Default Configuration" index="§-num;.4.17" screenshot="jndi_config.png">
-<description>
- <p>
- TBA.
- </p>
+<component name="Simple Config Element" index="§-num;.4.16" 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>
</description>
+
<properties>
- <property name="Name" required="">Descriptive name for this element that is shown in the tree.</property>
- <property name="Initial Context Factory" required="No">TBA</property>
- <property name="Provider URL" required="No">TBA</property>
+ <property name="Name" required="No">Descriptive name for this element that is shown in the tree. </property>
+ <property name="Parameter Name" required="Yes">The name of each parameter. These values are internal to JMeter's workings and
+ are not generally documented. Only those familiar with the code will know these values.</property>
+ <property name="Parameter Value" required="Yes">The value to apply to that parameter.</property>
</properties>
+
</component>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org