Last modified by Erik Bakker on 2023/01/24 15:10
From version 21.1
edited by Erik Bakker
on 2022/08/09 08:07
Change comment: There is no comment for this version
To version 23.1
edited by Erik Bakker
on 2022/08/09 08:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -49,7 +49,7 @@
49 49  
50 50  * /Projects/Project/ID
51 51  * //Project/ID
52 -* //ID
52 +* ~//ID
53 53  
54 54  At this point you probably wonder why anyone would start their journey on the XPath "path" from the root level. Well imagine the following **input** message:
55 55  
... ... @@ -68,12 +68,12 @@
68 68  
69 69  * It is the direct way to find the element
70 70  * Disadvantage of the absolute XPath is that if there are any changes made in the path of the element then that XPath gets failed.
71 -* Starts with the single forward-slash(/), which means you can select the element from the root node.
71 +* Starts with the single forward-slash(~/), which means you can select the element from the root node.
72 72  
73 73  **Relative XPath**
74 74  
75 75  * Finds the element(s) in the whole message, not considering the structure.
76 -* Starts with the double forward-slash (//), which means it can search the element anywhere at the message.
76 +* Starts with the double forward-slash (~//), which means it can search the element anywhere at the message.
77 77  
78 78  === 3.4 Namespaces ===
79 79