Howdy folks--
The constructors of XPaths now throw a JaxenException instead
of just a bare SAXPathException.
JaxenException still extends SAXPathException, so this should not break
code, unless you're catching an org.saxpath.XPathSyntaxException, in
which case, you now want to catch an org.jaxen.XPathSyntaxException,
which looks exactly like the SAXPath one.
If some other saxpath-esque exception occurs, you'll get a normal
JaxenException upon which you may call getRootCause() if you want
to delve deeper.
Tests still pass, and the demos have been updated to reflect the
new exception usage.
-bob
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
