Found this unresolved issue in my old e-mail. Adding here so we won't lose track of it again:
Recently I noticed that JaxenException now extends SAXPathException. Does this make sense? It feels to me that maybe it should be the other way around, if these two classes have an inheritance relationship at all. Possibly they should each be independent classes. Ideally I'd like to hide the org.jaxen.saxpath classes completely from public view. However, this prevents that. Should a casual user of Jaxen (i.e. someone not implementing their own navigator class or using org.jaxen.saxpath directly) encounter SAXPathExceptions, or should JaxenException be sufficient?
Compatibility wise the SAXPathException class has changed packages since 1.0, so changing the inheritance relationship would not be an additional incompatibility beyond what's already there.
I plan to fix this in beta 11. If anyone would rather not see this change, comment here. Thanks.