This comment has been minimized.

The methods selectNodes() and selectSingleNode() are very XPath-1.0 oriented. If there's going to be an API change at this stage of the game, it would really make sense to anticipate XPath 2.0. Unfortunately that's potentially quite complex, for example how do you handle an XPath expression that returns a sequence of dates? For two attempts to solve this problem, you can look at the XQJ API and Saxon's s9api API.

The methods selectNodes() and selectSingleNode() are very XPath-1.0 oriented. If there's going to be an API change at this stage of the game, it would really make sense to anticipate XPath 2.0. Unfortunately that's potentially quite complex, for example how do you handle an XPath expression that returns a sequence of dates? For two attempts to solve this problem, you can look at the XQJ API and Saxon's s9api API.

Michael Kay

This comment has been minimized.

By simplifying the XPath process to just evaluateFirst() and evaluate() methods on the XPAthExpression it is now compatible with XPath2.0 libraries. There are none that are both freely available and extensible enough to extend for JDOM though, so there thus are no XPath 2.0 implementations for JDOM2. If/when one comes available, we can add an implementation in to JDOM2.

For the moment, the infrastructure is in place, and flexible enough to cover XPath2.0

By simplifying the XPath process to just evaluateFirst() and evaluate() methods on the XPAthExpression it is now compatible with XPath2.0 libraries. There are none that are both freely available and extensible enough to extend for JDOM though, so there thus are no XPath 2.0 implementations for JDOM2. If/when one comes available, we can add an implementation in to JDOM2.

For the moment, the infrastructure is in place, and flexible enough to cover XPath2.0