There are several cases where SAXPath will not report
syntax errors when parsing invalid XPath expressions.
For example, for both of the following expressions:
..foo
/a/b/c[@id = "something" foo]
the parse method in com.werken.saxpath.XPathReader will
not throw an exception to indicate a syntax error. Most
of these problems stem from the fact that the match
method in this class does not throw an exception if the
next token in the token stream does not match the
expected token type. The attached patch file rectifies
this behaviour. It is a patch for the 1.0 FCS release.
Patch for non-reporting of invalid XPath expressions