I am trying to build a complex xpath expression which will answer the following condition.
From the XML data below, returns the User entity which:
He has 2 different profiles values which are "operator" and "admin" (I don't know the exact order ahead)
<user> <login>user1</login> <name>User 1</name> <profile> <value>admin</value> <id>2</id> <description>admin users</description> </profile> <profile> <value>operator</value> <id>1</id> <description>Operator</description> </profile> </user> <user> <login>user2</login> <name>User 2</name> <profile> <value>admin</value> <id>4</id> <description>admins users</description> </profile> <profile> <value>poweruser</value> <id>5</id> <description>power users</description> </profile> </user> </root>
Can someone please supply an example for such a case?
EDIT: Added a complex profile entity
selects the union of all nodes selected by expr1 and all nodes selected by expr2. The | character denotes the XPath union operator. You can use the union operator in any case when you want the union of the nodes selected by several XPath expressions to be returned.
Predicate refers to the XPath expression written in square brackets. It refers to restrict the selected nodes in a node set for some condition.
It can store large amount of XML document and data. Native XML database is queried by the XPath-expressions. Native XML database has an advantage over the XML-enabled database. It is highly capable to store, query and maintain the XML document than XML-enabled database.
XPath (XML Path Language) is a query language that can be used to query data from XML documents. In RUEI, XPath queries can be used for content scanning of XML documents. A complete specification of XPath is available at http://www.w3.org/TR/xpath .
The following should do what you're after:
/root/user[login='user1' and name='User 1' and profile='admin' and profile='operator']
Having two tests for the profile
value might seem odd, but as there are multiple profile
nodes then the condition will be satisfied as long as at least one node matches the test.
The reason you can compare profile
directly to a string
, even though it actually is a node
is that the string-value
of an element node is the string-value
of all its descendants concatenated together, which in this case is just the contents of value
.
If profile
contained more elements than value
you'd have to use a slightly more complex predicate test to determine the existence of a matching profile
node based just on the value
(this should work with your updated question):
/root/user[login='user1' and name='User 1' and profile[value='admin'] and profile[value='operator']]
Here is a more exact answer (at present Greg Beech's answer does not check for condition 3. in the problem: the user
element must have exactly 2 profile
children):
/*/user [login='user1' and name='User 1' and not(profile[3]) and profile/value='admin' and profile/value='operator' ]
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With