jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Milamber <milam...@apache.org>
Subject Re: svn commit: r1677049 - /jmeter/trunk/xdocs/usermanual/
Date Mon, 10 Aug 2015 19:39:02 GMT


On 10/08/2015 15:05, Felix Schumacher wrote:
>
> Am 10. August 2015 14:48:42 MESZ, schrieb Milamber <milamber@apache.org>:
>> The usage of right arrow sigle (&rarr;) bring an issue with the
>> printable docs in the JMeter archive (zip or tgz), the arrow is replace
>>
>> by a interrogation mark (?)
>>
>> On the docs directory (for the website), they have no issue (the arrow
>> is visible)... (use xslt transformation)
>>
>> Encoding issue? or Anakia issue (printable docs use it)...
> Yes, encoding issue. To fix it, put the properties
>
> input.encoding=utf-8
> output.encoding=utf-8
>
> into xdocs/velocity.properties and change all occurrences of iso-8859-1 in the vsl files
with utf-8.

Works better with the utf-8 properties. Now the arrows are display 
correctly on printable docs (and docs)

Patch:

Index: xdocs/stylesheets/site_printable.vsl
===================================================================
--- xdocs/stylesheets/site_printable.vsl    (revision 1695153)
+++ xdocs/stylesheets/site_printable.vsl    (working copy)
@@ -521,7 +521,7 @@
  <html>
  <head>
  <link rel="stylesheet" type="text/css" href="$cssdir/style.css"/>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
  #set ($authors = $root.getChild("properties").getChildren("author"))
  #foreach ( $au in $authors )
  #metaauthor ( $au.getText() $au.getAttributeValue("email") )
Index: xdocs/velocity.properties
===================================================================
--- xdocs/velocity.properties    (revision 1695153)
+++ xdocs/velocity.properties    (working copy)
@@ -15,4 +15,6 @@

  resource.loader.1.resource.path = xdocs/stylesheets
  # set true to debug vsl files
-runtime.references.strict=true
\ No newline at end of file
+runtime.references.strict=true
+input.encoding=utf-8
+output.encoding=utf-8
\ No newline at end of file


======================
Thanks Felix.




>
> I will commit that, when I had more time to check this solution, but feedback would be
superb.
>
> Regards,
> Felix
>
>>
>> On 30/04/2015 20:45, fschumacher@apache.org wrote:
>>> Author: fschumacher
>>> Date: Thu Apr 30 19:45:36 2015
>>> New Revision: 1677049
>>>
>>> URL: http://svn.apache.org/r1677049
>>> Log:
>>> Use rarr (right arrow) entity to show menu path
>>>
>>> Modified:
>>>       jmeter/trunk/xdocs/usermanual/build-db-test-plan.xml
>>>       jmeter/trunk/xdocs/usermanual/build-ftp-test-plan.xml
>>>      
>> jmeter/trunk/xdocs/usermanual/build-jms-point-to-point-test-plan.xml
>>>       jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml
>>>       jmeter/trunk/xdocs/usermanual/build-ldap-test-plan.xml
>>>       jmeter/trunk/xdocs/usermanual/build-ldapext-test-plan.xml
>>>       jmeter/trunk/xdocs/usermanual/build-monitor-test-plan.xml
>>>       jmeter/trunk/xdocs/usermanual/build-web-test-plan.xml
>>>       jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml
>>>
>>> Modified: jmeter/trunk/xdocs/usermanual/build-db-test-plan.xml
>>> URL:
>> http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-db-test-plan.xml?rev=1677049&r1=1677048&r2=1677049&view=diff
>> ==============================================================================
>>> --- jmeter/trunk/xdocs/usermanual/build-db-test-plan.xml (original)
>>> +++ jmeter/trunk/xdocs/usermanual/build-db-test-plan.xml Thu Apr 30
>> 19:45:36 2015
>>> @@ -18,6 +18,7 @@
>>>    
>>>    <!DOCTYPE document[
>>>    <!ENTITY sect-num '7'>
>>> +<!ENTITY rarr     "&#x02192;" >
>>>    ]>
>>>    
>>>    <document prev="build-adv-web-test-plan.html"
>> next="build-ftp-test-plan.html" id="$Id$">
>>> @@ -53,7 +54,7 @@ send requests, and the how many requests
>>>    
>>>    <p>Go ahead and add the ThreadGroup element by first selecting the
>> Test Plan,
>>>    clicking your right mouse button to get the Add menu, and then
>> select
>>> -<b>Add</b> --&gt; <b>ThreadGroup</b>.</p>
>>> +<b>Add</b> &rarr; <b>ThreadGroup</b>.</p>
>>>    
>>>    <p>You should now see the Thread Group element under Test Plan. If
>> you do not
>>>    see the element, then "expand" the Test Plan tree by clicking on
>> the
>>> @@ -108,7 +109,7 @@ will be performing.  In this section, yo
>>>    perform.</p>
>>>    
>>>    <p>Begin by selecting the JDBC Users element. Click your right
>> mouse button
>>> -to get the w<b>Add</b> menu, and then select <b>Add</b>
--&gt;
>> <b>Config Element</b> --&gt; <b>JDBC Connection Configuration</b>.
>>> +to get the w<b>Add</b> menu, and then select <b>Add</b>
&rarr;
>> <b>Config Element</b> &rarr; <b>JDBC Connection Configuration</b>.
>>>    Then, select this new element to view its Control Panel (see Figure
>> &sect-num;.3).</p>
>>>    
>>>    <p>Set up the following fields (these assume we will be using a
>> MySQL database called 'cloud'):</p>
>>> @@ -130,7 +131,7 @@ More than one JDBC Request can refer to
>>>    Figure &sect-num;.3. JDBC Configuration</figure>
>>>    
>>>    <p>Selecting the JDBC Users element again. Click your right mouse
>> button
>>> -to get the <b>Add</b> menu, and then select <b>Add</b>
--&gt;
>> <b>Sampler</b> --&gt; <b>JDBC Request</b>.
>>> +to get the <b>Add</b> menu, and then select <b>Add</b>
&rarr;
>> <b>Sampler</b> &rarr; <b>JDBC Request</b>.
>>>    Then, select this new element to view its Control Panel (see Figure
>> &sect-num;.4).</p>
>>>    
>>>    <figure image="jdbctest/JDBCRequest.png">
>>> @@ -176,9 +177,9 @@ responsible for storing all of the resul
>>>    and presenting the results.</p>
>>>    
>>>    <p>Select the <i>JDBC Users</i> element and add a <complink
>> name="Summary Report"/>
>>> -listener (<b>Add</b> --&gt; <b>Listener</b> --&gt;
<b>Summary
>> Report</b>).</p>
>>> +listener (<b>Add</b> &rarr; <b>Listener</b> &rarr;
<b>Summary
>> Report</b>).</p>
>>>    
>>> -<p>Save the test plan, and run the test with the menu <b>Run</b>
>> --&gt; <b>Start</b> or <b>Ctrl+R</b></p>
>>> +<p>Save the test plan, and run the test with the menu <b>Run</b>
>> &rarr; <b>Start</b> or <b>Ctrl+R</b></p>
>>>    
>>>    <p>The listener shows the results.</p>
>>>    
>>>
>>> Modified: jmeter/trunk/xdocs/usermanual/build-ftp-test-plan.xml
>>> URL:
>> http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-ftp-test-plan.xml?rev=1677049&r1=1677048&r2=1677049&view=diff
>> ==============================================================================
>>> --- jmeter/trunk/xdocs/usermanual/build-ftp-test-plan.xml (original)
>>> +++ jmeter/trunk/xdocs/usermanual/build-ftp-test-plan.xml Thu Apr 30
>> 19:45:36 2015
>>> @@ -19,6 +19,7 @@
>>>    <!DOCTYPE document
>>>    [
>>>    <!ENTITY sect-num '8'>
>>> +<!ENTITY rarr     "&#x02192;" >
>>>    ]>
>>>    
>>>    <document prev="build-db-test-plan.html"
>> next="build-ldap-test-plan.html" id="$Id$">
>>> @@ -51,7 +52,7 @@ requests, and the how many requests they
>>>    
>>>    <p>Go ahead and add the Thread Group element by first selecting the
>> Test Plan,
>>>    clicking your right mouse button to get the Add menu, and then
>> select
>>> -<b>Add</b> --&gt; <b>ThreadGroup.</b></p>
>>> +<b>Add</b> &rarr; <b>ThreadGroup.</b></p>
>>>    
>>>    <p>You should now see the <b>Thread Group</b> element under
<b>Test
>> Plan.</b>  If you do not
>>>    see the element, then "expand" the Test Plan tree by clicking on
>> the
>>> @@ -103,7 +104,7 @@ for your FTP requests.  And then, in sec
>>>    elements which use some of the default settings you specified
>> here.</p>
>>>    
>>>    <p>Begin by selecting the FTP Users element. Click your right mouse
>> button
>>> -to get the Add menu, and then select <b>Add</b> --&gt; <b>Config
>> Element</b> --&gt; <b>FTP Request
>>> +to get the Add menu, and then select <b>Add</b> &rarr; <b>Config
>> Element</b> &rarr; <b>FTP Request
>>>    Defaults.</b> Then, select this new element to view its Control
>> Panel (see Figure &sect-num;.3).
>>>    </p>
>>>    
>>> @@ -139,7 +140,7 @@ Figure &sect-num;.4. FTP Defaults for ou
>>>    <note>JMeter sends requests in the order that they appear in the
>> tree.</note>
>>>    
>>>    <p>Start by adding the first <complink name="FTP Request"/>
>>> -to the FTP Users element (<b>Add</b> --&gt; <b>Sampler</b>
--&gt;
>> <b>FTP Request</b>).
>>> +to the FTP Users element (<b>Add</b> &rarr; <b>Sampler</b>
&rarr;
>> <b>FTP Request</b>).
>>>    Then, select the <b>FTP Request</b> element in the tree and edit
>> the following properties
>>>    (see Figure &sect-num;.5):
>>>    <ol>
>>> @@ -178,7 +179,7 @@ responsible for storing all of the resul
>>>    a visual model of the data.</p>
>>>    
>>>    <p>Select the FTP Users element and add a <complink name="View
>> Results in Table"/>
>>> -listener (<b>Add</b> --&gt; <b>Listener</b> --&gt;
<b>View Results
>> in Table</b>).</p>
>>> +listener (<b>Add</b> &rarr; <b>Listener</b> &rarr;
<b>View Results
>> in Table</b>).</p>
>>>    <p>Run your test and view the results.</p>
>>>    
>>>    <figure image="ftptest/ftp-results.png">
>>>
>>> Modified:
>> jmeter/trunk/xdocs/usermanual/build-jms-point-to-point-test-plan.xml
>>> URL:
>> http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-jms-point-to-point-test-plan.xml?rev=1677049&r1=1677048&r2=1677049&view=diff
>> ==============================================================================
>>> ---
>> jmeter/trunk/xdocs/usermanual/build-jms-point-to-point-test-plan.xml
>> (original)
>>> +++
>> jmeter/trunk/xdocs/usermanual/build-jms-point-to-point-test-plan.xml
>> Thu Apr 30 19:45:36 2015
>>> @@ -16,7 +16,10 @@
>>>       limitations under the License.
>>>    -->
>>>    
>>> -<!DOCTYPE document[<!ENTITY sect-num '11'>]>
>>> +<!DOCTYPE document[
>>> +<!ENTITY sect-num '11'>
>>> +<!ENTITY rarr     "&#x02192;" >
>>> +]>
>>>    
>>>    <document prev="build-ws-test-plan.html"
>> next="build-jms-topic-test-plan.html" id="$Id$">
>>>    
>>> @@ -64,7 +67,7 @@ requests, and the how many requests they
>>>    
>>>                <p>Go ahead and add the ThreadGroup element by first
>> selecting the Test Plan,
>>>    clicking your right mouse button to get the Add menu, and then
>> select
>>> -Add --&gt; ThreadGroup.</p>
>>> +Add &rarr; ThreadGroup.</p>
>>>    
>>>                <p>You should now see the Thread Group element under
>> Test Plan.  If you do not
>>>    see the element, then "expand" the Test Plan tree by clicking on
>> the
>>> @@ -109,7 +112,7 @@ leave the Control Panel (for example, wh
>>>            <section name="&sect-num;.2 Adding JMS Point-to-Point
>> Sampler" anchor="adding_point_to_point_sampler">
>>>    
>>>                <p>Start by adding the sampler <complink name="JMS
>> Point-to-Point"/>
>>> -to the Point-to-Point element (Add --&gt; Sampler --&gt; JMS
>> Point-to-Point).
>>> +to the Point-to-Point element (Add &rarr; Sampler &rarr; JMS
>> Point-to-Point).
>>>    Then, select the JMS Point-to-Point sampler element in the tree.
>>>     In building the example a configuration will be provided that
>> works with ActiveMQ 3.0.
>>>                </p>
>>> @@ -201,8 +204,8 @@ a visual model of the data.
>>>                </p>
>>>    
>>>                <p>Select the Thread Group element and add a
>>> -                <complink name="Graph Results"/> listener (Add
>> --&gt; Listener
>>> ---&gt; Graph Results).  Next, you need to specify a directory and
>> filename of the
>>> +                <complink name="Graph Results"/> listener (Add
>> &rarr; Listener
>>> +&rarr; Graph Results).  Next, you need to specify a directory and
>> filename of the
>>>    output file.  You can either type it into the filename field, or
>> select the
>>>    Browse button and browse to a directory and then enter a filename.
>>>                </p>
>>>
>>> Modified: jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml
>>> URL:
>> http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml?rev=1677049&r1=1677048&r2=1677049&view=diff
>> ==============================================================================
>>> --- jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml
>> (original)
>>> +++ jmeter/trunk/xdocs/usermanual/build-jms-topic-test-plan.xml Thu
>> Apr 30 19:45:36 2015
>>> @@ -18,6 +18,7 @@
>>>    <!DOCTYPE document
>>>    [
>>>    <!ENTITY sect-num '12'>
>>> +<!ENTITY rarr     "&#x02192;" >
>>>    ]>
>>>    <document prev="build-jms-point-to-point-test-plan.html"
>> next="build-monitor-test-plan.html" id="$Id$">
>>>    
>>> @@ -62,7 +63,7 @@ send.</p>
>>>    
>>>    <p>Go ahead and add the ThreadGroup element by first selecting the
>> Test Plan,
>>>    clicking your right mouse button to get the Add menu, and then
>> select
>>> -Add --&gt; ThreadGroup.</p>
>>> +Add &rarr; ThreadGroup.</p>
>>>    
>>>    <p>You should now see the Thread Group element under Test Plan.  If
>> you do not
>>>    see the element, then "expand" the Test Plan tree by clicking on
>> the
>>> @@ -115,7 +116,7 @@ leave the Control Panel (for example, wh
>>>    not, shutdown JMeter, copy the jar files over and restart
>> JMeter.</p>
>>>    
>>>    <p>Start by adding the sampler <complink name="JMS Subscriber"/>
>>> -to the Subscribers element (Add --&gt; Sampler --&gt; JMS
>> Subscriber).
>>> +to the Subscribers element (Add &rarr; Sampler &rarr; JMS
>> Subscriber).
>>>    Then, select the JMS Subscriber element in the tree and edit the
>> following properties:
>>>    
>>>    <ol>
>>> @@ -145,7 +146,7 @@ exhibits zombie threads with one client,
>>>    Figure &sect-num;.2. JMS Subscriber</figure>
>>>    
>>>    <p>Next add the sampler <complink name="JMS Publisher"/>
>>> -to the Publisher element (Add --&gt; Sampler --&gt; JMS Subscriber).
>>> +to the Publisher element (Add &rarr; Sampler &rarr; JMS Subscriber).
>>>    Then, select the JMS Publisher element in the tree and edit the
>> following properties:
>>>    </p>
>>>    
>>> @@ -185,8 +186,8 @@ Figure &sect-num;.3. JMS Publisher</figu
>>>    responsible for storing all of the results of your HTTP requests in
>> a file and presenting
>>>    a visual model of the data.</p>
>>>    
>>> -<p>Select the Test Plan element and add a <complink name="Graph
>> Results"/> listener (Add --&gt; Listener
>>> ---&gt; Graph Results).  Next, you need to specify a directory and
>> filename of the
>>> +<p>Select the Test Plan element and add a <complink name="Graph
>> Results"/> listener (Add &rarr; Listener
>>> +&rarr; Graph Results).  Next, you need to specify a directory and
>> filename of the
>>>    output file.  You can either type it into the filename field, or
>> select the
>>>    Browse button and browse to a directory and then enter a
>> filename.</p>
>>>    
>>>
>>> Modified: jmeter/trunk/xdocs/usermanual/build-ldap-test-plan.xml
>>> URL:
>> http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-ldap-test-plan.xml?rev=1677049&r1=1677048&r2=1677049&view=diff
>> ==============================================================================
>>> --- jmeter/trunk/xdocs/usermanual/build-ldap-test-plan.xml (original)
>>> +++ jmeter/trunk/xdocs/usermanual/build-ldap-test-plan.xml Thu Apr 30
>> 19:45:36 2015
>>> @@ -19,6 +19,7 @@
>>>    <!DOCTYPE document
>>>    [
>>>    <!ENTITY sect-num '9a'>
>>> +<!ENTITY rarr     "&#x02192;" >
>>>    ]>
>>>    
>>>    <document prev="build-ftp-test-plan.html"
>> next="build-ldapext-test-plan.html" id="$Id$">
>>> @@ -46,7 +47,7 @@ repeat 4 times) = 40 LDAP requests. To c
>>>    The Thread Group tells JMeter the number of users you want to
>> simulate, how often the users should send
>>>    requests, and the how many requests  they should send.</p>
>>>                    <p>Go ahead and add the ThreadGroup element by
>> first selecting the Test Plan, clicking your
>>> -right mouse button to get the <b>Add</b> menu, and then select
>> <b>Add</b>&gt;<b>ThreadGroup</b>. You should now see
the
>>> +right mouse button to get the <b>Add</b> menu, and then select
>> <b>Add</b>&rarr;<b>ThreadGroup</b>. You should now see
the
>>>    Thread Group element under Test Plan. If you do not see the
>> element, then "expand" the Test Plan tree by
>>>    clicking on the Test Plan element.
>>>    <figure image="ldaptest/threadgroup.png">
>>> @@ -56,7 +57,7 @@ Figure &sect-num;.1. Thread Group and fi
>>>    </section>
>>>        <section name="&sect-num;.2 Adding Login Config Element"
>> anchor="add_login">
>>>            <p>Begin by selecting the <b>LDAP Users</b> element.
Click
>> your right mouse
>>> -button to get the Add menu, and then select <b>Add</b>&gt;<b>Config
>> Element</b>&gt;<b>Login Config Element</b>.
>>> +button to get the Add menu, and then select
>> <b>Add</b>&rarr;<b>Config Element</b>&rarr;<b>Login
Config Element</b>.
>>>    Then,  select this new element to view its Control Panel.</p>
>>>            <p>Like most JMeter elements, the <b>Login  Config
>> Element</b>'s Control Panel has a name
>>>    field that you can modify. In this example, leave this field with
>> the default value.</p>
>>> @@ -72,7 +73,7 @@ field that you can modify. In this examp
>>>    
>>>        <section name="&sect-num;.3 Adding LDAP Request Defaults"
>> anchor="add_defaults">
>>>                    <p>Begin by selecting the LDAP Users element. Click
>> your right mouse button
>>> -to get the <b>Add</b> menu, and then select <b>Add</b>&gt;<b>Config
>> Element</b>&gt;<b>LDAP Request Defaults</b>. Then,
>>> +to get the <b>Add</b> menu, and then select
>> <b>Add</b>&rarr;<b>Config Element</b>&rarr;<b>LDAP
Request
>> Defaults</b>. Then,
>>>    select this new element to view its Control Panel.</p>
>>>            <p>Like most JMeter elements, the <b>LDAP Request
>> Defaults</b> Control Panel has a name
>>>    field that you can modify. In this example, leave this field with
>> the default value.</p>
>>> @@ -98,8 +99,8 @@ field that you can modify. In this examp
>>>    
>>>            </ol>
>>>            <p>JMeter sends requests in the order that you add them to
>> the tree.
>>> -Start by adding the first LDAP Request to the LDAP Users element
>> (<b>Add</b>&gt;<b>
>>> -Sampler</b>&gt;<b>LDAP Request</b>). Then, select the
LDAP Request
>> element in the tree
>>> +Start by adding the first LDAP Request to the LDAP Users element
>> (<b>Add</b>&rarr;<b>
>>> +Sampler</b>&rarr;<b>LDAP Request</b>). Then, select the
LDAP Request
>> element in the tree
>>>    and edit the following properties</p>
>>>            <ol>
>>>                <li>Rename to "Add" this element</li>
>>> @@ -142,7 +143,7 @@ properties</p>
>>>    <section name="&sect-num;.5 Adding a Response Assertion"
>> anchor="ResponseAssertion">
>>>                   <p>You can add a Response Assertion element.
>>>     This element will check the received response data by verifying if
>> the response text is "successful".
>>> -  (<b>Add</b>&gt;<b>Assertion</b>&gt;<b>Response
>> Assertion</b>).<br>Note: A this position in the tree,
>>> +  (<b>Add</b>&rarr;<b>Assertion</b>&rarr;<b>Response
>> Assertion</b>).<br>Note: A this position in the tree,
>>>      the Response Assertion will be executed for each LDAP
>> Request.</br></p>
>>>              <ol>
>>>                <li>Select <b>Text Response</b> Radio button
in
>> <b>Response Field to Test</b> group</li>
>>> @@ -156,7 +157,7 @@ properties</p>
>>>                   <p>The final element you need to add to your Test
>> Plan is a Listener.
>>>     This element is responsible for storing all of the results of your
>> LDAP
>>>    requests in a file  and presenting a visual model of the data.
>> Select the LDAP
>>> -Users element and add a View Results in Table
>> (<b>Add</b>&gt;<b>Listener</b>&gt;<b>View Results
in Table</b>)</p>
>>> +Users element and add a View Results in Table
>> (<b>Add</b>&rarr;<b>Listener</b>&rarr;<b>View
Results in Table</b>)</p>
>>>    <figure image="ldaptest/viewtable.png">
>>>      Figure &sect-num;.6 View Results in Table Listener</figure>
>>>    
>>>
>>> Modified: jmeter/trunk/xdocs/usermanual/build-ldapext-test-plan.xml
>>> URL:
>> http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-ldapext-test-plan.xml?rev=1677049&r1=1677048&r2=1677049&view=diff
>> ==============================================================================
>>> --- jmeter/trunk/xdocs/usermanual/build-ldapext-test-plan.xml
>> (original)
>>> +++ jmeter/trunk/xdocs/usermanual/build-ldapext-test-plan.xml Thu Apr
>> 30 19:45:36 2015
>>> @@ -18,6 +18,7 @@
>>>    
>>>    <!DOCTYPE document[
>>>    <!ENTITY sect-num '9b'>
>>> +<!ENTITY rarr     "&#x02192;" >
>>>    ]>
>>>    
>>>    <document prev="build-ldap-test-plan.html"
>> next="build-ws-test-plan.html" id="$Id$">
>>> @@ -76,7 +77,7 @@ requests, and the how many requests  the
>>>    </p>
>>>    <p>
>>>    Go ahead and add the <code>Thread Group</code> element by first
>> selecting the <code>Test Plan</code>, clicking your
>>> -right mouse button to get the <code>Add</code> menu, and then select
>> <code>Add</code>&gt;<code>Threads (Users)</code>&gt;<code>Thread
>> Group</code>.
>>> +right mouse button to get the <code>Add</code> menu, and then select
>> <code>Add</code>&rarr;<code>Threads (Users)</code>&rarr;<code>Thread
>> Group</code>.
>>>    You should now see the <code>Thread Group</code> element under
>> <code>Test Plan</code>. If you do not see the element, then "expand"
>> the Test Plan tree by
>>>    clicking on the Test Plan element.
>>>    </p>
>>> @@ -89,7 +90,7 @@ Figure &sect-num;.1. Thread Group with D
>>>        <subsection name="&sect-num;.2 Adding LDAP Extended Request
>> Defaults" anchor="add_ldapext_defaults">
>>>    <p>
>>>    Begin by selecting the LDAP Ext Users element. Click your right
>> mouse button
>>> -to get the <code>Add</code> menu, and then select
>> <code>Add</code>&gt;<code>Config Element</code>&gt;<code>LDAP
Extended
>> Request Defaults</code>. Then,
>>> +to get the <code>Add</code> menu, and then select
>> <code>Add</code>&rarr;<code>Config Element</code>&rarr;<code>LDAP
>> Extended Request Defaults</code>. Then,
>>>    select this new element to view its Control Panel.
>>>    </p>
>>>    <p>
>>> @@ -145,8 +146,8 @@ JMeter sends requests in the order that
>>>    </p>
>>>    <p>
>>>    Adding a requests always start by:<br/>
>>> -Adding the <code>LDAP Extended Request</code> to the LDAP Ext Users
>> element (<code>Add</code>&gt;
>>> -<code>Sampler</code>&gt;<code>LDAP Ext Request</code>).
Then, select
>> the <code>LDAP Ext Request</code> element in the tree
>>> +Adding the <code>LDAP Extended Request</code> to the LDAP Ext Users
>> element (<code>Add</code>&rarr;
>>> +<code>Sampler</code>&rarr;<code>LDAP Ext Request</code>).
Then,
>> select the <code>LDAP Ext Request</code> element in the tree
>>>    and edit the following properties.</p>
>>>    
>>>    
>>> @@ -442,7 +443,7 @@ Figure &sect-num;.3.9. Unbind example</f
>>>    The final element you need to add to your Test Plan is a Listener.
>>>     This element is responsible for storing all of the results of your
>> LDAP
>>>    requests in a file  and presenting a visual model of the data.
>> Select the Thread group
>>> -element and add a <code>View Results Tree</code>
>> (<code>Add</code>&gt;<code>Listener</code>&gt;<code>View
Results
>> Tree</code>)
>>> +element and add a <code>View Results Tree</code>
>> (<code>Add</code>&rarr;<code>Listener</code>&rarr;<code>View
Results
>> Tree</code>)
>>>    </p>
>>>    <p>
>>>    <figure image="ldaptest/extviewtree.png">
>>>
>>> Modified: jmeter/trunk/xdocs/usermanual/build-monitor-test-plan.xml
>>> URL:
>> http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-monitor-test-plan.xml?rev=1677049&r1=1677048&r2=1677049&view=diff
>> ==============================================================================
>>> --- jmeter/trunk/xdocs/usermanual/build-monitor-test-plan.xml
>> (original)
>>> +++ jmeter/trunk/xdocs/usermanual/build-monitor-test-plan.xml Thu Apr
>> 30 19:45:36 2015
>>> @@ -18,6 +18,7 @@
>>>    <!DOCTYPE document
>>>    [
>>>    <!ENTITY sect-num '13'>
>>> +<!ENTITY rarr     "&#x02192;" >
>>>    ]>
>>>    <document prev="build-jms-topic-test-plan.html"
>> next="listeners.html" id="$Id$">
>>>    
>>> @@ -55,7 +56,7 @@ single server is bad and can create sign
>>>    
>>>    <p>Go ahead and add the ThreadGroup element by first selecting the
>> Test Plan,
>>>    clicking your right mouse button to get the Add menu, and then
>> select
>>> -Add --&gt; ThreadGroup.</p>
>>> +Add &rarr; ThreadGroup.</p>
>>>    
>>>    <p>You should now see the Thread Group element under Test Plan.  If
>> you do not
>>>    see the element, "expand" the Test Plan tree by clicking on the
>> Test Plan element.</p>
>>> @@ -69,7 +70,7 @@ Figure &sect-num;.1. Thread Group with D
>>>    
>>>    <section name="&sect-num;.2 HTTP Auth Manager"
>> anchor="adding_auth">
>>>    <p>Add the <complink name="HTTP Authorization Manager"/> to the
>> Thread Group element
>>> -(Add --&gt; Config element --&gt; HTTP Authorization Manager). Enter
>> the username
>>> +(Add &rarr; Config element &rarr; HTTP Authorization Manager). Enter
>> the username
>>>    and password for your webserver. Important note: the monitor only
>> works with
>>>    Tomcat5 build 5.0.19 and newer. For instructions on how to setup
>> Tomcat, please
>>>    refer to tomcat 5 documentation.</p>
>>> @@ -83,7 +84,7 @@ refer to tomcat 5 documentation.</p>
>>>    <section name="&sect-num;.3 Adding HTTP Request"
>> anchor="adding_request">
>>>    
>>>    <p>Add the <complink name="HTTP Request"/> to the Thread Group
>> element
>>> -(Add --&gt; Sampler --&gt; HTTP Request). Then, select the HTTP
>> Request element
>>> +(Add &rarr; Sampler &rarr; HTTP Request). Then, select the HTTP
>> Request element
>>>    in the tree and edit the following properties):
>>>    <ol>
>>>    <li>Change the Name field to "Server Status".</li>
>>> @@ -100,7 +101,7 @@ in the tree and edit the following prope
>>>    
>>>    <section name="&sect-num;.4 Adding Constant Timer"
>> anchor="adding_timer">
>>>    
>>> -<p>Add a timer to this thread group (Add --&gt; Timer --&gt;
>> Constant Timer).
>>> +<p>Add a timer to this thread group (Add &rarr; Timer &rarr;
>> Constant Timer).
>>>    Enter 5000 milliseconds in the "Thread Delay" box. In general,
>> using intervals shorter
>>>    than 5 seconds will add stress to your server. Find out what is an
>> acceptable interval
>>>    before you deploy the monitor in your production environment.</p>
>>> @@ -114,7 +115,7 @@ before you deploy the monitor in your pr
>>>     the raw data and statistics, make sure you use different
>> filenames.</p>
>>>    
>>>    <p>Select the thread group element and add a <complink name="Simple
>> Data Writer"/> listener
>>> -(Add --&gt; Listener --&gt; Simple Data Writer).  Next, you need to
>> specify a directory
>>> +(Add &rarr; Listener &rarr; Simple Data Writer).  Next, you need to
>> specify a directory
>>>    and filename of the output file.  You can either type it into the
>> filename field, or
>>>    select the Browse button and browse to a directory and then enter a
>> filename.</p>
>>>    
>>> @@ -123,7 +124,7 @@ select the Browse button and browse to a
>>>    <section name="&sect-num;.6 Adding Monitor Results"
>> anchor="add_monitor_listener">
>>>    
>>>    <p>Add the <a
>> href="component_reference.html#listeners">Listener</a> by selecting the
>>> -test plan element (Add --&gt; Listener -- &gt; Monitor Results).
>>> +test plan element (Add &rarr; Listener &rarr; Monitor Results).
>>>    <br></br>
>>>    By default, the Listener will select the results from the first
>> connector in the sample response.
>>>    The Connector prefix field can be used to select a different
>> connector.
>>> Modified: jmeter/trunk/xdocs/usermanual/build-web-test-plan.xml
>>> URL:
>> http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-web-test-plan.xml?rev=1677049&r1=1677048&r2=1677049&view=diff
>> ==============================================================================
>>> --- jmeter/trunk/xdocs/usermanual/build-web-test-plan.xml (original)
>>> +++ jmeter/trunk/xdocs/usermanual/build-web-test-plan.xml Thu Apr 30
>> 19:45:36 2015
>>> @@ -18,6 +18,7 @@
>>>    
>>>    <!DOCTYPE document[
>>>    <!ENTITY sect-num '5'>
>>> +<!ENTITY rarr     "&#x02192;" >
>>>    ]>
>>>    
>>>    <document prev="test_plan.html" next="build-adv-web-test-plan.html"
>> id="$Id$">
>>> @@ -58,7 +59,7 @@ requests, and how many requests they sho
>>>    
>>>    <p>Go ahead and add the ThreadGroup element by first selecting the
>> Test Plan,
>>>    clicking your right mouse button to get the Add menu, and then
>> select
>>> -Add --&gt; ThreadGroup.</p>
>>> +Add &rarr; ThreadGroup.</p>
>>>    
>>>    <p>You should now see the Thread Group element under Test Plan.  If
>> you do not
>>>    see the element, then "expand" the Test Plan tree by clicking on
>> the
>>> @@ -111,7 +112,7 @@ for your HTTP requests.  And then, in se
>>>    elements which use some of the default settings you specified
>> here.</p>
>>>    
>>>    <p>Begin by selecting the JMeter Users (Thread Group) element.
>> Click your right mouse button
>>> -to get the Add menu, and then select Add --&gt; Config Element
>> --&gt; HTTP Request
>>> +to get the Add menu, and then select Add &rarr; Config Element
>> &rarr; HTTP Request
>>>    Defaults. Then select this new element to view its Control Panel
>> (see Figure &sect-num;.3).
>>>    </p>
>>>    
>>> @@ -148,8 +149,8 @@ Group</a> in your test plan.  This will
>>>    cookies, but shared across all <complink name="HTTP Request"/>
>> objects.</p>
>>>    
>>>    <p>To add the <complink name="HTTP Cookie Manager"/>, simply select
>> the
>>> -<a href="test_plan.html#thread_group">Thread Group</a>, and choose
>> Add --&gt;
>>> -Config Element --&gt; HTTP
>>> +<a href="test_plan.html#thread_group">Thread Group</a>, and choose
>> Add &rarr;
>>> +Config Element &rarr; HTTP
>>>    Cookie Manager, either from the Edit Menu, or from the right-click
>> pop-up menu.</p>
>>>    </section>
>>>    
>>> @@ -163,7 +164,7 @@ Changes page (http://jmeter.apache.org/c
>>>    <note>JMeter sends requests in the order that they appear in the
>> tree.</note>
>>>    
>>>    <p>Start by adding the first <complink name="HTTP Request"/>
>>> -to the JMeter Users element (Add --&gt; Sampler --&gt; HTTP
>> Request).
>>> +to the JMeter Users element (Add &rarr; Sampler &rarr; HTTP
>> Request).
>>>    Then, select the HTTP Request element in the tree and edit the
>> following properties
>>>    (see Figure &sect-num;.5):
>>>    <ol>
>>> @@ -196,8 +197,8 @@ Figure &sect-num;.6. HTTP Request for JM
>>>    responsible for storing all of the results of your HTTP requests in
>> a file and presenting
>>>    a visual model of the data.</p>
>>>    
>>> -<p>Select the JMeter Users element and add a <complink name="Graph
>> Results"/> listener (Add --&gt; Listener
>>> ---&gt; Graph Results).  Next, you need to specify a directory and
>> filename of the
>>> +<p>Select the JMeter Users element and add a <complink name="Graph
>> Results"/> listener (Add &rarr; Listener
>>> +&rarr; Graph Results).  Next, you need to specify a directory and
>> filename of the
>>>    output file.  You can either type it into the filename field, or
>> select the
>>>    Browse button and browse to a directory and then enter a
>> filename.</p>
>>>    
>>>
>>> Modified: jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml
>>> URL:
>> http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml?rev=1677049&r1=1677048&r2=1677049&view=diff
>> ==============================================================================
>>> --- jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml (original)
>>> +++ jmeter/trunk/xdocs/usermanual/build-ws-test-plan.xml Thu Apr 30
>> 19:45:36 2015
>>> @@ -18,6 +18,7 @@
>>>    
>>>    <!DOCTYPE document[
>>>    <!ENTITY sect-num '10'>
>>> +<!ENTITY rarr     "&#x02192;" >
>>>    ]>
>>>    
>>>    <document prev="build-ldapext-test-plan.html"
>> next="build-jms-point-to-point-test-plan.html" id="$Id$">
>>> @@ -135,8 +136,8 @@ Figure &sect-num;.3. JMeter Users Thread
>>>    responsible for storing all of the results of your HTTP requests in
>> a file and presenting
>>>    a visual model of the data.</p>
>>>    
>>> -<p>Select the JMeter Users element and add a <complink
>> name="Aggregate Graph"/> listener (Add --&gt; Listener
>>> ---&gt; Aggregate Graph).  Next, you need to specify a directory and
>> filename of the
>>> +<p>Select the JMeter Users element and add a <complink
>> name="Aggregate Graph"/> listener (Add &rarr; Listener
>>> +&rarr; Aggregate Graph).  Next, you need to specify a directory and
>> filename of the
>>>    output file.  You can either type it into the filename field, or
>> select the
>>>    Browse button and browse to a directory and then enter a
>> filename.</p>
>>>    
>>>
>>>
>>>
>


Mime
View raw message