fixed Matcher.hasXpath against multiple element

[night-gale]

Fixes #323 323 mentioned that Matcher.hasXpath could have unexpected behavior when given an XML document with multiple elements of the same path. The reason is that current logic only evaluates a single element out of an XML doc. It is now fixed by letting the matcher first get all possible elements. Then if any of them matches, the result will be a match, otherwise failed.

[nhojpatrick]

Going to try and kick start hamcrest, so if you want to get it merged, please rebase from the branch v2.3-candidates. Still trying to understand how has permissions to perform a release.