Xpath is broken about jcabi-xml HOT 9 CLOSED

@yegor256/z please, pay attention to this issue

from jcabi-xml.

@piotrkot this is because the root node is not changed, when you retrieve nodes.get(1). Your root is still <root>

from jcabi-xml.

Job gh:jcabi/jcabi-xml#154 is not assigned, can't get performer

from jcabi-xml.

@yegor256 I would like to have it reopened. I had no time to react to your comment.

Let me explain the problem.
Based on the provided XML, all "a" nodes are found with doc.nodes("//a").
This indeed finds two "a" nodes, and List<XML> nodes list contains two XML elements.
With nodes.get(0) I access the first one and nodes.get(0).xpath("//x/text()").get(0) is equal to "1".
I expect with nodes.get(1) I can access the second element from the nodes list. Furthermore, I expect nodes.get(1).xpath("//x/text()").get(0) to be equal to "2" as stated in the assert. But this is not true. nodes.get(1).xpath("//x/text()").get(0) is equal to "1".
I believe this is a bug.
Please, explain how does it refer to the root.

from jcabi-xml.

@piotrkot the XPath location // means "search from the ROOT of the document". Thus, no matter where you are at the moment, it will find you everything that exists in the entire document. This is a feature, not a bug :)

from jcabi-xml.

@yegor256 Now I understand. Replacing xpath("//x/text()") with xpath("x/text()") solves my problem.
Thank you (and good to have you back with short response times :) )

from jcabi-xml.

@piotrkot wring.io helps me a lot :)

from jcabi-xml.

@yegor256 Yes, I know. I read you blog regularly :) But this issue was opened for 5 months ;)

from jcabi-xml.

@piotrkot now I'm almost live on GitHub)

from jcabi-xml.