jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pmoua...@apache.org
Subject svn commit: r1812913 - /jmeter/trunk/xdocs/usermanual/component_reference.xml
Date Sun, 22 Oct 2017 13:10:19 GMT
Author: pmouawad
Date: Sun Oct 22 13:10:19 2017
New Revision: 1812913

URL: http://svn.apache.org/viewvc?rev=1812913&view=rev
Log:
Fix typos

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=1812913&r1=1812912&r2=1812913&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Sun Oct 22 13:10:19 2017
@@ -1506,7 +1506,7 @@ The following table shows some values wh
 <component name="JMS Subscriber" index="&sect-num;.1.14"  width="739" height="607"
screenshot="jmssubscriber.png">
     <description>
         <p>
-        JMS Publisher will subscribe to messages in a given destination (topic or queue).
For those not
+        JMS Subscriber will subscribe to messages in a given destination (topic or queue).
For those not
         familiar with JMS, it is the J2EE specification for messaging. There are
         numerous JMS servers on the market and several open source options.
         </p>
@@ -1529,7 +1529,7 @@ The following table shows some values wh
   Be sure to add a variable like <code>${__threadNum}</code> when you have more
than one Thread.</property>
   <property name="JMS Selector" required="No">Message Selector as defined by JMS specification
to extract only 
   messages that respect the Selector condition. Syntax uses subpart of SQL 92.</property>
-  <property name="Setup" required="Yes">The destination setup type. With <code>At
startup</code>, the destination name is static (i.e. always same name during the test),
with <code>Each sample</code>, the destination name is dynamic and is evaluate
at each sample (i.e. the destination name may be a variable)</property>
+  <property name="Setup" required="Yes">The destination setup type. With <code>At
startup</code>, the destination name is static (i.e. always same name during the test),
with <code>Each sample</code>, the destination name is dynamic and is evaluated
at each sample (i.e. the destination name may be a variable)</property>
   <property name="Authentication" required="Yes">Authentication requirement for the
JMS provider</property>
   <property name="User" required="No">User Name</property>
   <property name="Password" required="No">Password (N.B. this is stored unencrypted
in the test plan)</property>



Mime
View raw message