Author: pmouawad
Date: Mon Sep 10 20:49:13 2018
New Revision: 1840493
URL: http://svn.apache.org/viewvc?rev=1840493&view=rev
Log:
Clarify documentation for XPath and Namespaces
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=1840493&r1=1840492&r2=1840493&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Mon Sep 10 20:49:13
2018
@@ -4697,17 +4697,19 @@ Some sample expressions:
The non-tolerant parser can be quite slow, as it may need to download the DTD
etc.
</note>
<note>
-<b>NAMESPACES</b>
-As a work-round for namespace limitations of the Xalan XPath parser
implementation on which JMeter is based,
-you can provide a Properties file which contains mappings for the namespace
prefixes:
+<b>NAMESPACES</b><br/>
+As a work-round for namespace limitations of the Xalan XPath parser
(implementation on which JMeter is based) you need to:
+<ul>
+<li>provide a Properties file (if for example your file is named
namespaces.properties) which contains mappings for the namespace prefixes:
<source>
-prefix1=Full Namespace 1
-prefix2=Full Namespace 2
+prefix1=http\://foo.apache.org
+prefix2=http\://toto.apache.org
…
-</source>
+</source></li>
-You reference this file in <code>jmeter.properties</code> file using the
property:
- <source>xpath.namespace.config</source>
+<li>reference this file in <code>user.properties</code> file using the
property:
+ <source>xpath.namespace.config=namespaces.properties</source></li>
+</ul>
</note>
</component>
<component name="XML Schema Assertion" index="§-num;.5.9" width="472"
height="132" screenshot="assertion/XMLSchemaAssertion.png">
@@ -5901,17 +5903,19 @@ extracting the node as text or attribute
</note>
<note>
-<b>NAMESPACES</b>
-As a work-round for namespace limitations of the Xalan XPath parser
implementation on which JMeter is based,
-you can provide a Properties file which contains mappings for the namespace
prefixes:
+<b>NAMESPACES</b><br/>
+As a work-round for namespace limitations of the Xalan XPath parser
(implementation on which JMeter is based) you need to:
+<ul>
+<li>provide a Properties file (if for example your file is named
namespaces.properties) which contains mappings for the namespace prefixes:
<source>
-prefix1=Full Namespace 1
-prefix2=Full Namespace 2
+prefix1=http\://foo.apache.org
+prefix2=http\://toto.apache.org
…
-</source>
+</source></li>
-You reference this file in <code>jmeter.properties</code> file using the
property:
- <source>xpath.namespace.config</source>
+<li>reference this file in <code>user.properties</code> file using the
property:
+ <source>xpath.namespace.config=namespaces.properties</source></li>
+</ul>
</note>
<p></p>
Another option is to use the following code: