Author: fschumacher
Date: Sun Apr 26 20:11:24 2015
New Revision: 1676143
URL: http://svn.apache.org/r1676143
Log:
Markup changes. Use code and source where < or > entities are used. With
code and source blocks we don't have to escape them.
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=1676143&r1=1676142&r2=1676143&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Sun Apr 26 20:11:24
2015
@@ -2872,16 +2872,16 @@ will be displayed in the lower panel.<br
The engine of regular expression is the same that the Regular Expression
Extractor.<br/>
For example, the RE <b>(JMeter\w*).*</b> applied to the current JMeter home
page gives the following output:
<br/>
-<pre>
+<source>
Match count: 26
-Match[1][0]=JMeter - Apache JMeter&lt;/title>
+Match[1][0]=JMeter - Apache JMeter</title>
Match[1][1]=JMeter
-Match[2][0]=JMeter" title="JMeter" border="0"/>&lt;/a>
+Match[2][0]=JMeter" title="JMeter" border="0"/></a>
Match[2][1]=JMeter
-Match[3][0]=JMeterCommitters">Contributors&lt;/a>
+Match[3][0]=JMeterCommitters">Contributors</a>
Match[3][1]=JMeterCommitters
... and so on ...
-</pre>
+</source>
<br/>
The first number in [] is the match number; the second number is the group.
Group [0] is whatever matched the whole RE.
@@ -4627,8 +4627,8 @@ on XPath.
</p>
Some sample expressions:
<ul>
-<li>//title[text()='Text to match'] - matches &lt;text&gt;Text to
match&lt;/text&gt; anywhere in the response</li>
-<li>/title[text()='Text to match'] - matches &lt;text&gt;Text to
match&lt;/text&gt; at root level in the response</li>
+<li><code>//title[text()='Text to match']</code> - matches
<code><text>Text to match</text></code> anywhere in the
response</li>
+<li><code>/title[text()='Text to match']</code> - matches
<code><text>Text to match</text></code> at root level in the
response</li>
</ul>
</description>
@@ -5591,15 +5591,10 @@ extracting the node as text or attribute
Note that currently only namespaces declared on the root element will
be recognised.
A later version of JMeter may support user-definition of additional
workspace names.
Meanwhile, a work-round is to replace:
- <br></br>
- //mynamespace:tagname
- <br></br>
+ <source>//mynamespace:tagname</source>
by
- <br></br>
- //*[local-name()='tagname' and namespace-uri()='uri-for-namespace']
- <br></br>
- where "uri-for-namespace" is the uri for the "mynamespace" namespace.
-
+ <source>//*[local-name()='tagname' and
namespace-uri()='uri-for-namespace']</source>
+ where "<code>uri-for-namespace</code>" is the uri for the
"<code>mynamespace</code>" namespace.
(not applicable if Tidy is selected)
</property>
<property name="Validate XML" required="If Tidy is not selected">Check
the document against its schema.</property>
@@ -5607,8 +5602,8 @@ extracting the node as text or attribute
<property name="Fetch External DTDs" required="If Tidy is not
selected">If selected, external DTDs are fetched.</property>
<property name="Return entire XPath fragment instead of text content?"
required="Yes">
If selected, the fragment will be returned rather than the text
content.<br></br>
- For example //title would return "&lt;title>Apache
JMeter&lt;/title>" rather than "Apache JMeter".<br></br>
- In this case, //title/text() would return "Apache JMeter".
+ For example <code>//title</code> would return "<code><title>Apache
JMeter</title></code>" rather than "<code>Apache JMeter</code>".<br></br>
+ In this case, <code>//title/text()</code> would return "<code>Apache
JMeter</code>".
</property>
<property name="Reference Name" required="Yes">The name of the JMeter
variable in which to store the result.</property>
<property name="XPath Query" required="Yes">Element query in XPath
language. Can return more than one match.</property>
