Given the document:
If you try to get the XPath string after visiting the
<error/> tag, it is /error instead of
This is due to an off-by-one in XpathNodeTracker. I
have attached a patch to XpathNodeTracker and a new
Unit Test to detect regression.
To illustrate the bug, first just patch the unit tests,
verify that mine fails, then patch XpathNodeTracker and
verify that the unit test succeeds.
The patch is done against the 1.0 distribution.
Thanks for a great tool!
Log in to post a comment.