svn commit: r1676065 - /jmeter/trunk/xdocs/usermanual/component_reference.xml

[fs...@apache.org]

Author: fschumacher
Date: Sat Apr 25 20:31:35 2015
New Revision: 1676065

URL: http://svn.apache.org/r1676065
Log:
Markup changes (mostly code and complink)

Modified:
    jmeter/trunk/xdocs/usermanual/component_reference.xml

Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=1676065&r1=1676064&r2=1676065&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Sat Apr 25 20:31:35 2015
@@ -671,19 +671,19 @@ See <a href="build-ws-test-plan.html">Bu
 </note>
 <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
-POST content. 
-To change the "Content-type" from the default of "text/xml", use a HeaderManager. 
-Note that the sampler will use all the headers from the HeaderManager.
-If a SOAP action is specified, that will override any SOAPaction in the HeaderManager.
+POST content.
+To change the "<code>Content-type</code>" from the default of "<code>text/xml</code>", use a <complink name="HTTP Header Manager" />.
+Note that the sampler will use all the headers from the <complink name="HTTP Header Manager"/>.
+If a SOAP action is specified, that will override any <code>SOAPaction</code> in the <complink name="HTTP Header Manager"/>.
 The primary difference between the soap sampler and
 webservice sampler, is the soap sampler uses raw post and does not require conformance to
 SOAP 1.1.</p>
 <note>For versions of JMeter later than 2.2, the sampler no longer uses chunked encoding by default.<br/>
 For screen input, it now always uses the size of the data.<br/>
 File input uses the file length as determined by Java.<br/>
-On some OSes this may not work for all files, in which case add a child Header Manager
-with Content-Length set to the actual length of the file.<br/>
-Or set Content-Length to -1 to force chunked encoding.
+On some OSes this may not work for all files, in which case add a child <complink name="HTTP Header Manager"/>
+with <code>Content-Length</code> set to the actual length of the file.<br/>
+Or set <code>Content-Length</code> to <code>-1</code> to force chunked encoding.
 </note>
 </description>
 
@@ -691,8 +691,8 @@ Or set Content-Length to -1 to force chu
         <property name="Name" required="No">Descriptive name for this sampler
          that is shown in the tree.</property>
         <property name="URL" required="Yes">The URL to direct the SOAP request to.</property>
-        <property name="Send SOAP action" required="No">Send a SOAP action header? (overrides the Header Manager)</property>
-        <property name="Use KeepAlive" required="No">If set, sends Connection: keep-alive, else sends Connection: close</property>
+        <property name="Send SOAP action" required="No">Send a SOAP action header? (overrides the <complink name="HTTP Header Manager"/>)</property>
+        <property name="Use KeepAlive" required="No">If set, sends <code>Connection: keep-alive</code>, else sends <code>Connection: close</code></property>
         <property name="Soap/XML-RPC Data" required="No">The Soap XML message, or XML-RPC instructions.
         Not used if the filename is provided.
         </property>