mstover1 2003/02/01 06:41:11
Modified: . build.xml
docs running.html
docs/usermanual component_reference.html
xdocs/usermanual component_reference.xml
Log:
Last mods before 1.8.1 release
Revision Changes Path
1.87 +7 -7 jakarta-jmeter/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/build.xml,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -r1.86 -r1.87
--- build.xml 30 Jan 2003 00:35:46 -0000 1.86
+++ build.xml 1 Feb 2003 14:41:10 -0000 1.87
@@ -338,23 +338,23 @@
<fileset refid="external.jars"/>
</copy>
<tar destfile="${dist.dir}/${dist.name}.tar" longfile="gnu">
- <tarfileset dir="." prefix="${dist.name}" excludes="${dist.executables}">
+ <tarfileset dir="." prefix="${dist.name}" excludes="${dist.executables}"
defaultexcludes="yes">
<patternset refid="dist.binaries"/>
</tarfileset>
- <tarfileset mode="755" includes="${dist.executables}" dir="."
prefix="${dist.name}"/>
+ <tarfileset mode="755" includes="${dist.executables}" dir="."
prefix="${dist.name}" defaultexcludes="yes"/>
</tar>
<gzip zipfile="${dist.dir}/${dist.name}.tgz" src="${dist.dir}/${dist.name}.tar"
/>
<zip zipfile="${dist.dir}/${dist.name}.zip">
- <zipfileset dir="." prefix="${dist.name}">
+ <zipfileset dir="." prefix="${dist.name}" defaultexcludes="yes">
<patternset refid="dist.binaries"/>
</zipfileset>
</zip>
<tar destfile="${dist.dir}/${dist.name}-javadoc.tar" longfile="gnu">
- <tarfileset includes="${docs.api.dest}/" dir="." prefix="${dist.name}"/>
+ <tarfileset includes="${docs.api.dest}/" dir="." prefix="${dist.name}"
defaultexcludes="yes"/>
</tar>
<gzip zipfile="${dist.dir}/${dist.name}-javadoc.tgz"
src="${dist.dir}/${dist.name}-javadoc.tar" />
<zip zipfile="${dist.dir}/${dist.name}-javadoc.zip">
- <zipfileset includes="${docs.api.dest}/" dir="." prefix="${dist.name}"/>
+ <zipfileset includes="${docs.api.dest}/" dir="." prefix="${dist.name}"
defaultexcludes="yes"/>
</zip>
</target>
@@ -363,8 +363,8 @@
<delete file="lib/jorphan.jar"/>
<delete dir="${jar.dest}"/>
<delete dir="${build.dir}"/>
- <delete dir="${docs.api.dest}"/> <!-- redundant but future-proof -->
- <delete dir="${docs.dest}"/>
+ <delete dir="${docs.api.dest}" defaultexcludes="yes"/> <!-- redundant but
future-proof -->
+ <delete dir="${docs.dest}" defaultexcludes="yes"/>
<delete dir="${dist.dir}"/>
</target>
1.55 +0 -0 jakarta-jmeter/docs/running.html
Index: running.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/running.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
1.30 +219 -105 jakarta-jmeter/docs/usermanual/component_reference.html
Index: component_reference.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/component_reference.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- component_reference.html 29 Jan 2003 17:18:47 -0000 1.29
+++ component_reference.html 1 Feb 2003 14:41:11 -0000 1.30
@@ -232,62 +232,62 @@
</td></tr>
<tr><td>
-
+
<p >
This sampler lets you
send an HTTP/HTTPS request to a web server. It
- also lets you control whether or not JMeter parses HTML files for images and
- Java applets and sends HTTP requests to retrieve them.
+ also lets you control whether or not JMeter parses HTML files for images and
+ Java applets and sends HTTP requests to retrieve them.
</p>
-
+
<p >
If you are going to
send multiple requests to the same web server, consider
- using an
+ using an
<a href="../usermanual/component_reference.html#HTTP_Request_Defaults">HTTP
Request Defaults</a>
- Configuration Element so you do not have to enter the same information for each
- HTTP Request.
+ Configuration Element so you do not have to enter the same information for
each
+ HTTP Request.
</p>
-
+
<p >
Or, instead of
manually adding HTTP Requests, you may want to use
- JMeter's
+ JMeter's
<a href="../usermanual/component_reference.html#HTTP_Proxy_Server">HTTP Proxy
Server</a>
to create
- them. This can save you time if you have a lot of HTTP requests or requests
with many
- parameters.
+ them. This can save you time if you have a lot of HTTP requests or
requests with many
+ parameters.
</p>
-
+
<p >
If the request
requires a login authorization, you will also have to add an
-
+
<a
href="../usermanual/component_reference.html#HTTP_Authorization_Manager">HTTP
Authorization Manager</a>
- Configuration Element. And, if the request uses cookies, then you will also
need an
-
+ Configuration Element. And, if the request uses cookies, then you will also
need an
+
<a href="../usermanual/component_reference.html#HTTP_Cookie_Manager">HTTP
Cookie Manager</a>
. You can
- add either of these elements to the Thread Group or the HTTP Request. If you
have
- more than one HTTP Request that needs authorizations or cookies, then add the
- elements to the Thread Group. That way, all HTTP Request controllers will
share the
- same Authorization Manager and Cookie Manager elements.
+ add either of these elements to the Thread Group or the HTTP Request. If
you have
+ more than one HTTP Request that needs authorizations or cookies, then add
the
+ elements to the Thread Group. That way, all HTTP Request controllers will
share the
+ same Authorization Manager and Cookie Manager elements.
</p>
-
+
<p >
If the request uses a
technique called "URL Rewriting" to maintain sessions,
- then see section
-
+ then see section
+
<a href="build-adv-web-test-plan.html#url_rewriting">
6.1 Handling User
Sessions With URL Rewriting
</a>
- for additional configuration steps.
+ for additional configuration steps.
</p>
@@ -350,26 +350,26 @@
<tr>
<td>Send Parameters With the Request</td>
<td> The query
string will
- be generated from the list of parameters you provide. Each parameter has a
+ be generated from the list of parameters you provide. Each parameter has a
<i >
name
</i>
and
-
+
<i >
value
</i>
. The query
string will be generated in the correct fashion, depending on
- the choice of "Method" you made (ie if you chose GET, the query string will be
- appended to the URL, if POST, then it will be sent separately). Also, if you
are
- sending a file using a multipart form, the query string will be created using
the
- multipart form specifications.
-
+ the choice of "Method" you made (ie if you chose GET, the query string will
be
+ appended to the URL, if POST, then it will be sent separately). Also, if
you are
+ sending a file using a multipart form, the query string will be created
using the
+ multipart form specifications.
+
<p >
- Additionally, you can specify whether each paramter should be URL encoded. If
you are not sure what this
- means, it is probably best to select it. If your values contain characters
such as & or spaces, or
- question marks, then encoding is usually required.
+ Additionally, you can specify whether each paramter should be URL encoded.
If you are not sure what this
+ means, it is probably best to select it. If your values contain characters
such as & or spaces, or
+ question marks, then encoding is usually required.
</p>
</td>
<td>
@@ -379,8 +379,8 @@
<tr>
<td>Filename</td>
<td> Name of the
file to send. If left blank, JMeter
- does not send a file, if filled in, JMeter automatically sends the request as
- a multipart form request.
+ does not send a file, if filled in, JMeter automatically sends the request
as
+ a multipart form request.
</td>
<td>
No
@@ -590,7 +590,7 @@
<tr>
<td>Name</td>
<td> Descriptive
name for this sampler
- that is shown in the tree.
+ that is shown in the tree.
</td>
<td>
No
@@ -599,7 +599,7 @@
<tr>
<td>Classname</td>
<td> The specific
implementation of
- the JavaSamplerClient interface to be sampled.
+ the JavaSamplerClient interface to be sampled.
</td>
<td>
Yes
@@ -608,8 +608,8 @@
<tr>
<td>Send Parameters with Request</td>
<td> A list of
- arguments that will be passed to the sampled class. All arguments
- are sent as Strings.
+ arguments that will be passed to the sampled class. All arguments
+ are sent as Strings.
</td>
<td>
No
@@ -644,7 +644,7 @@
<tr>
<td>Name</td>
<td> Descriptive
name for this sampler
- that is shown in the tree.
+ that is shown in the tree.
</td>
<td>
No
@@ -661,7 +661,7 @@
<tr>
<td>Soap/XML-RPC Data</td>
<td> The Soap XML
message, or XML-RPC
- instructions.
+ instructions.
</td>
<td>
No
@@ -840,7 +840,7 @@
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img
src="../images/screenshots/logic-controller/interleave2.gif"><br/>
<font size="-1">
- Figure 2 - Interleave Controller Example 2
+ Figure 2 - Interleave Controller Example 2
</font></td></tr></table></p>
@@ -890,9 +890,9 @@
<tr>
<td>Loop Count</td>
<td>
- The number of times the subelements of this controller will be
iterated each time
- through a test run.
-
+ The number of times the subelements of this controller will be
iterated each time
+ through a test run.
+
<p >
<b >
Special Case:
@@ -902,8 +902,8 @@
Thread Group
</a>
- element behaves slightly differently. Unless set to forever, it stops
the test after
- the given number of iterations have been done.
+ element behaves slightly differently. Unless set to forever, it
stops the test after
+ the given number of iterations have been done.
</p>
</td>
<td>
@@ -1183,7 +1183,109 @@
</td></tr>
<tr><td>
<blockquote>
-
<table border="0" cellspacing="0" cellpadding="2">
+
<description >
+
+Most of the listeners perform several roles in addition to "listening"
+to the test results. They frequently also provide means to view,
+save, and read saved test results.
+
+
<p >
+
+The saving and reading of test results is generic. The various
+listeners generally have a panel whereby one can specify the file to
+which the results will be written (or read). The results are stored as XML
+files, typically with a ".jtl" extension.
+ </p>
+
+
+
<p >
+
+The information to be saved is configurable. If one specifies the
+"Functional Test Mode" on the Test Plan element, one gets the largest
+amount of information. If this box is not checked, the default saved
+data includes a time stamp (the number of milliseconds since midnight,
+January 1, 1970 UTC), the data type, the thread name, the label, the
+response time, message, and code, and a success indicator.
+ </p>
+
+
+
<p >
+
+One can get a more selective set of information my modifying the
+jmeter.properties file. The following example indicates how to set
+these.
+ </p>
+
+
+
<p >
+
+
+
<code >
+
+
+
<pre >
+
+#---------------------------------------------------------------------------
+# Results file configuration
+#---------------------------------------------------------------------------
+
+# This section helps determine how result data will be saved.
+# The commented out values are the defaults.
+
+# legitimate values: xml, csv, db. Only xml is currently supported.
+#jmeter.save.saveservice.output_format=xml
+
+# true when field should be saved; false otherwise
+
+jmeter.save.saveservice.data_type=false
+jmeter.save.saveservice.label=true
+jmeter.save.saveservice.response_code=false
+jmeter.save.saveservice.response_data=false
+jmeter.save.saveservice.response_message=false
+jmeter.save.saveservice.successful=true
+jmeter.save.saveservice.thread_name=false
+jmeter.save.saveservice.time=false
+
+# legitimate values: none, ms, or a format suitable for SimpleDateFormat
+#jmeter.save.saveservice.timestamp_format=ms
+jmeter.save.saveservice.timestamp_format=MM/dd/yy HH:mm:ss
+
+# legitimate values: none, first, all
+jmeter.save.saveservice.assertion_results=first
+
+ </pre>
+
+
+ </code>
+ </p>
+
+
+
<p >
+
+The date format to be used for the timestamp is described in
+
<A
HREF="http://java.sun.com/j2se/1.4/docs/api/java/text/SimpleDateFormat.html";>
+
+
+
<B >
+ SimpleDateFormat
+ </B>
+ </A>
+ .
+Bear in mind that choosing a date format other than "ms" is likely to
+make it impossible for JMeter to interpret the value when it is read
+in later for viewing purposes.
+ </p>
+
+
+
<p >
+
+The viewing capabilities are described in the following subsections.
+ </p>
+
+
+
+ </description>
+
<table
border="0" cellspacing="0" cellpadding="2">
<tr><td>
<font face="arial,helvetica,sanserif">
<a name="Mailer_Visualizer"><h3>13.3.1 Mailer
Visualizer</h3></a>
@@ -1227,7 +1329,7 @@
<tr>
<td>SMTP Host</td>
<td> IP address or
host name of SMTP (email redirector)
- server.
+ server.
</td>
<td>
No
@@ -1252,7 +1354,7 @@
<tr>
<td>Failure Limit</td>
<td> Once this
number of failed responses are received, a failure
- email is sent.
+ email is sent.
</td>
<td>
Yes
@@ -1261,12 +1363,12 @@
<tr>
<td>Success Limit</td>
<td> Once this
number of successful responses are
- received
+ received
<strong >
after previously
reaching the failure limit
</strong>
, a success
email
- is sent. The mailer will thus only send out messages in a sequence of
failed-succeeded-failed-succeeded, etc.
+ is sent. The mailer will thus only send out messages in a sequence of
failed-succeeded-failed-succeeded, etc.
</td>
<td>
Yes
@@ -1282,7 +1384,7 @@
<tr>
<td>Failures</td>
<td> A field that
keeps a running total of number
- of failures so far received.
+ of failures so far received.
</td>
<td>
No
@@ -1392,6 +1494,18 @@
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.
+
+
<p >
+
+There are two ways two view the response, controllable by a push
+button. The default view shows all of the text contained in the
+response. The alternative view attempts to render the response as
+HTML. The rendered HTML is likely to compare poorly to the view one
+would get in any web browser; however, it does provide a quick
+approximation that is helpful for initial result evaluation.
+ </p>
+
+
<p><b>Control Panel</b></p>
<div align="center"><img
src="../images/screenshots/view_results_tree.png"></div>
</td></tr>
@@ -1740,16 +1854,16 @@
<tr>
<td>Patterns to Include</td>
<td> Regular
expressions that are matched against the full URL that is sampled. Allows filtering
of requests that are recorded. All requests pass through, but only
- those that meet the requirements of the Include/Exclude fields are
+ those that meet the requirements of the Include/Exclude fields are
<i >
recorded
</i>
. If both
Include and Exclude are
- left empty, then everything is recorded (which can result in dozens of samples
recorded for each page, as images, stylesheets,
- etc are recorded).
+ left empty, then everything is recorded (which can result in dozens of
samples recorded for each page, as images, stylesheets,
+ etc are recorded).
<b >
If there is at least
one entry in the Include field, then only requests that match one or more Include
patterns are
- recorded
+ recorded
</b>
.
</td>
@@ -1760,7 +1874,7 @@
<tr>
<td>Patterns to Exclude</td>
<td> Regular
expressions that are matched against the URL that is sampled.
-
+
<b >
Any requests that
match one or more Exclude pattern are
<i >
@@ -1929,20 +2043,20 @@
<tr>
<td>Send Parameters With the Request</td>
<td> The query
string will
- be generated from the list of parameters you provide. Each parameter has a
+ be generated from the list of parameters you provide. Each parameter has a
<i >
name
</i>
and
-
+
<i >
value
</i>
. The query
string will be generated in the correct fashion, depending on
- the choice of "Method" you made (ie if you chose GET, the query string will be
- appended to the URL, if POST, then it will be sent separately). Also, if you
are
- sending a file using a multipart form, the query string will be created using
the
- multipart form specifications.
+ the choice of "Method" you made (ie if you chose GET, the query string will
be
+ appended to the URL, if POST, then it will be sent separately). Also, if
you are
+ sending a file using a multipart form, the query string will be created
using the
+ multipart form specifications.
</td>
<td>
No
@@ -2035,7 +2149,7 @@
<tr>
<td>Name (Header)</td>
<td> Name of the
request header.
- Two common request headers you may want to experiment with
+ Two common request headers you may want to experiment with
are "User-Agent" and "Referer".
</td>
<td>
@@ -2188,7 +2302,7 @@
<tr>
<td>Start</td>
<td> The starting
number for the counter. The counter will equal this
- number during the first iteration.
+ number during the first iteration.
</td>
<td>
Yes
@@ -2197,7 +2311,7 @@
<tr>
<td>Increment</td>
<td> How much to
increment the counter by after each
- iteration.
+ iteration.
</td>
<td>
Yes
@@ -2214,7 +2328,7 @@
<tr>
<td>Reference Name</td>
<td> This controls
how you refer to this value in other elements. Syntax is
- as in
+ as in
<a href="functions.html">
user-defined values
</a>
@@ -2231,8 +2345,8 @@
<tr>
<td>Track Counter Independently for each User</td>
<td> In other
words, is this a global counter, or does each user get their
- own counter? If unchecked, the counter is global (ie, user #1 will get value
"1", and user #2 will get value "2" on
- the first iteration). If checked, each user has an independent counter.
+ own counter? If unchecked, the counter is global (ie, user #1 will get
value "1", and user #2 will get value "2" on
+ the first iteration). If checked, each user has an independent counter.
</td>
<td>
No
@@ -2289,7 +2403,7 @@
<tr>
<td>Response Field to Test</td>
<td> Instructs
JMeter to test
- against either the Response Text from the server, or against the URL
string that was sampled.
+ against either the Response Text from the server, or against the
URL string that was sampled.
</td>
<td>
Yes
@@ -2298,8 +2412,8 @@
<tr>
<td>Pattern Matching Rules</td>
<td> Indicates
whether the text being tested
- must CONTAIN or MATCH the test patterns. NOT may also be selected to indicate
the text
- should NOT CONTAIN or NOT MATCH the test patterns.
+ must CONTAIN or MATCH the test patterns. NOT may also be selected to
indicate the text
+ should NOT CONTAIN or NOT MATCH the test patterns.
</td>
<td>
Yes
@@ -2308,9 +2422,9 @@
<tr>
<td>Patterns to Test</td>
<td> A list of
regular expressions to
- be tested. Each pattern is tested separately. There is no difference between
setting up
- one Assertion with multiple patterns and setting up multiple Assertions with
one
- pattern each (assuming the other options are the same).
+ be tested. Each pattern is tested separately. There is no difference
between setting up
+ one Assertion with multiple patterns and setting up multiple Assertions
with one
+ pattern each (assuming the other options are the same).
</td>
<td>
Yes
@@ -2375,7 +2489,7 @@
<tr>
<td>Duration in Milliseconds</td>
<td> The maximum
number of milliseconds
- each response is allowed before being marked as failed.
+ each response is allowed before being marked as failed.
</td>
<td>
Yes
@@ -2725,8 +2839,8 @@
<tr>
<td>Session Argument Name</td>
<td> The name of
the parameter to grab from
- previous response. This modifier will find the parameter anywhere it exists
on the page, and
- grab the value assigned to it, whether it's in an HREF or a form.
+ previous response. This modifier will find the parameter anywhere it
exists on the page, and
+ grab the value assigned to it, whether it's in an HREF or a form.
</td>
<td>
Yes
@@ -2735,7 +2849,7 @@
<tr>
<td>Path Extension</td>
<td> Some web apps
rewrite URLs by appending
- a semi-colon plus the session id parameter. Check this box if that is so.
+ a semi-colon plus the session id parameter. Check this box if that is so.
</td>
<td>
No
@@ -2812,7 +2926,7 @@
<tr>
<td>Name (second appearing)</td>
<td> The name of
the parameter to
- modify or add to the HTTP Request.
+ modify or add to the HTTP Request.
</td>
<td>
Yes
@@ -2837,7 +2951,7 @@
<tr>
<td>Upper Bound</td>
<td> A number value
to end the counter, at which point it restarts
- with the Lower Bound value.
+ with the Lower Bound value.
</td>
<td>
Yes
@@ -2908,7 +3022,7 @@
<tr>
<td>File Name</td>
<td> Name of the
XML file in JMeter's /bin directory
- that holds the value sets.
+ that holds the value sets.
</td>
<td>
Yes
@@ -3088,12 +3202,12 @@
<tr>
<td>First arguement</td>
<td> The first
argument is the regular expression
- to be applied to the response data. It will grab all matches. Any parts of
this expression
- that you wish to use in your template string, be sure to surround in
parentheses. Example:
- <a href="(.*)">. This will grab the value of the link and store it as
the first group (there is
- only 1 group). Another example: <input type="hidden" name="(.*)"
value="(.*)">. This will
- grab the name as the first group, and the value as the second group. These
values can be used
- in your template string
+ to be applied to the response data. It will grab all matches. Any parts
of this expression
+ that you wish to use in your template string, be sure to surround in
parentheses. Example:
+ <a href="(.*)">. This will grab the value of the link and store it
as the first group (there is
+ only 1 group). Another example: <input type="hidden" name="(.*)"
value="(.*)">. This will
+ grab the name as the first group, and the value as the second group. These
values can be used
+ in your template string
</td>
<td>
Yes
@@ -3102,8 +3216,8 @@
<tr>
<td>Second argument</td>
<td> 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:
- $[group_number]$. Ie: $1$, or $2$. Your template can be any string.
+ the function at run-time. To refer to a group captured in the regular
expression, use the syntax:
+ $[group_number]$. Ie: $1$, or $2$. Your template can be any string.
</td>
<td>
Yes
@@ -3112,32 +3226,32 @@
<tr>
<td>Third argument</td>
<td> The third
argument tells JMeter which match
- to use. Your regular expression might find numerous matches. You have four
choices:
-
+ to use. Your regular expression might find numerous matches. You have
four choices:
+
<ul >
<li >
An integer - Tells
JMeter to use that match. '1' for the first found match, '2' for the
- second, and so on
+ second, and so on
</li>
-
+
<li >
RAND - Tells JMeter to
choose a match at random.
</li>
-
+
<li >
ALL - Tells JMeter to
use all matches, and create a template string for each one and then
- append them all together. This option is little used.
+ append them all together. This option is little used.
</li>
-
+
<li >
A float number between
0 and 1 - tells JMeter to find the Xth match using the formula:
- (number_of_matches_found * float_number) rounded to nearest integer.
+ (number_of_matches_found * float_number) rounded to nearest integer.
</li>
-
+
</ul>
</td>
<td>
@@ -3147,7 +3261,7 @@
<tr>
<td>Fourth argument</td>
<td> If 'ALL' was
selected for the above argument
- value, then this argument will be inserted between each appended copy of the
template value.
+ value, then this argument will be inserted between each appended copy of
the template value.
</td>
<td>
No
@@ -3201,7 +3315,7 @@
<tr>
<td>First argument</td>
<td> TRUE if you
wish each simulated user's counter
- to be kept independent and separate from the other users. FALSE for a global
counter.
+ to be kept independent and separate from the other users. FALSE for a
global counter.
</td>
<td>
Yes
@@ -3213,8 +3327,8 @@
<br >
</br>
- Stored values are of the form ${refName}. This allows you to keep one
counter and refer to its value in
- multiple places.
+ Stored values are of the form ${refName}. This allows you to keep
one counter and refer to its value in
+ multiple places.
</td>
<td>
No
@@ -3292,7 +3406,7 @@
<tr>
<td>last argument</td>
<td> A reference
name for reusing the value
- computed by this function.
+ computed by this function.
</td>
<td>
Yes
1.32 +8 -8 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.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- component_reference.xml 31 Jan 2003 22:34:50 -0000 1.31
+++ component_reference.xml 1 Feb 2003 14:41:11 -0000 1.32
@@ -382,18 +382,18 @@
The saving and reading of test results is generic. The various
listeners generally have a panel whereby one can specify the file to
which the results will be written (or read). The results are stored as XML
-files, typically with a ".jtl" extension.
+files, typically with a ".jtl" extension.</p>
<p>
The information to be saved is configurable. If one specifies the
"Functional Test Mode" on the Test Plan element, one gets the largest
amount of information. If this box is not checked, the default saved
data includes a time stamp (the number of milliseconds since midnight,
January 1, 1970 UTC), the data type, the thread name, the label, the
-response time, message, and code, and a success indicator.
+response time, message, and code, and a success indicator.</p>
<p>
One can get a more selective set of information my modifying the
jmeter.properties file. The following example indicates how to set
-these.
+these.</p>
<p>
<code>
<pre>
@@ -425,17 +425,17 @@
# legitimate values: none, first, all
jmeter.save.saveservice.assertion_results=first
</pre>
-</code>
+</code></p>
<p>
The date format to be used for the timestamp is described in <A
HREF="http://java.sun.com/j2se/1.4/docs/api/java/text/SimpleDateFormat.html";>
<B>SimpleDateFormat</B></A>.
Bear in mind that choosing a date format other than "ms" is likely to
make it impossible for JMeter to interpret the value when it is read
-in later for viewing purposes.
-<p>
-The viewing capabilities are described in the following subsections.
+in later for viewing purposes.</p>
<p>
+The viewing capabilities are described in the following subsections.</p>
+
</description>
<component index="13.3.1" name="Mailer Visualizer"
screenshot="../images/screenshots/mailer_vis.png">
<description><p>The mailer visualizer can be set up to send email if a test run
receives too many
@@ -504,7 +504,7 @@
response. The alternative view attempts to render the response as
HTML. The rendered HTML is likely to compare poorly to the view one
would get in any web browser; however, it does provide a quick
-approximation that is helpful for initial result evaluation.
+approximation that is helpful for initial result evaluation.</p>
</description>
</component>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
