Added: jmeter/trunk/xdocs/images/screenshots/xpath2_extractor.png
URL:
http://svn.apache.org/viewvc/jmeter/trunk/xdocs/images/screenshots/xpath2_extractor.png?rev=1832784&view=auto
==============================================================================
Binary file - no diff available.
Propchange: jmeter/trunk/xdocs/images/screenshots/xpath2_extractor.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
URL:
http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=1832784&r1=1832783&r2=1832784&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Sun Jun 3 19:05:08
2018
@@ -5758,6 +5758,57 @@ extracting the node as text or attribute
</p>
</component>
+<component name="XPath2 Extractor" index="§-num;.8.3" width="926"
height="333" screenshot="xpath2_extractor.png">
+ <description>This test element allows the user to extract value(s) from
structured response - XML or (X)HTML -
+ using XPath2 query language.
+ </description>
+ <properties>
+ <property name="Name" required="No">Descriptive name for this element
that is shown in the tree.</property>
+ <property name="Apply to:" required="Yes">
+ This is for use with samplers that can generate sub-samples,
+ e.g. HTTP Sampler with embedded resources, Mail Reader or samples
generated by the Transaction Controller.
+ <ul>
+ <li><code>Main sample only</code> - only applies to the main
sample</li>
+ <li><code>Sub-samples only</code> - only applies to the
sub-samples</li>
+ <li><code>Main sample and sub-samples</code> - applies to both.</li>
+ <li><code>JMeter Variable Name to use</code> - extraction is to be
applied to the contents of the named variable</li>
+ </ul>
+ XPath matching is applied to all qualifying samples in turn, and all
the matching results will be returned.
+ </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 <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="Name of created variable" 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 2.0
language. Can return more than one match.</property>
+ <property name="Match No. (0 for Random)" required="No">If the XPath Path
query leads to many results, you can choose which one(s) to extract as
Variables:
+ <ul>
+ <li><code>0</code> : means random (default value)</li>
+ <li><code>-1</code> means extract all results, they will be named as
<code><em><variable name></em>_N</code> (where <code>N</code> goes from 1
to Number of results)</li>
+ <li><code>X</code> : means extract the X<sup>th</sup> result. If this
X<sup>th</sup> is greater than number of matches, then nothing is returned.
Default value will be used</li>
+ </ul>
+ </property>
+ <property name="Default Value" required="yes">Default value returned when
no match found.
+ It is also returned if the node has no value and the fragment option is
not selected.</property>
+ <property name="Namespaces list" required="No">List of namespaces aliases
you want to use to parse the document, one line per declaration.
+ You must specify them as follow : <code>prefix=namespace</code>. This
implementation makes it easier to
+ use namespaces than with the old XPathExtractor version.</property>
+ </properties>
+ <p>To allow for use in a <complink name="ForEach Controller"/>, it works
exactly the same as the above XPath Extractor</p>
+ <p>XPath2 Extractor provides some interestings tools such as an improved
syntax and much more functions than in it's first version.</p>
+ <p>Here are some exemples : </p>
+ <dl>
+ <dt><code>abs(/book/page[2])</code></dt>
+ <dd>extracts 2<sup>nd</sup> absolute value of the page from a book</dd>
+ <dt><code>avg(/librarie/book/page)</code></dt>
+ <dd>extracts the average number of page from all the books in the
libraries</dd>
+ <dt><code>compare(/book[1]/page[2],/book[2]/page[2])</code></dt>
+ <dd>return Integer value equal 0 to if the 2<sup>nd</sup> page of the
first book is equal to the 2<sup>nd</sup> page of the 2<sup>nd</sup> book, else
return -1.</dd>
+ </dl>
+ <p>To see more informations about thoses fuctions, please check <a
href="http://saxon.sourceforge.net/saxon7.9.1/functions.html";>xPath2
functions</a></p>
+</component>
+
<component name="XPath Extractor" index="§-num;.8.3" width="729"
height="317" screenshot="xpath_extractor.png">
<description>This test element allows the user to extract value(s) from
structured response - XML or (X)HTML - using XPath
Modified: jmeter/trunk/xdocs/usermanual/properties_reference.xml
URL:
http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/properties_reference.xml?rev=1832784&r1=1832783&r2=1832784&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/properties_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/properties_reference.xml Sun Jun 3 19:05:08
2018
@@ -79,6 +79,9 @@ These properties are only taken into acc
<property name="xpath.namespace.config">
Path to a Properties file containing Namespace mapping in the form
<code>prefix=Namespace</code>.
Example:
<source>ns=http://biz.aol.com/schema/2006-12-18</source></property>
+<property name="xpath2query.parser.cache.size">XPath2 query cache for storing
compiled XPath queries
+ Defaults to <code>400</code>
+ </property>
</properties>
</section>
<section name="§-num;.3 SSL configuration" anchor="ssl_config">
