Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Version 2.3
-
None
Description
This is an enhancement proposal.
Currently, XMLBeans looks for certain engines in certain orders to process XPath/XQuery expressions. In particular, it searches for the Saxon XQuery engine. There has been a request (XMLBEANS-366) to support the use of JXPath for processing XPath expressions. The patch from the user changes the engine lookup logic to add looking for JXPath if Saxon is not found. I propose to make the choice of engine more pluggable instead of hardcoding logic to lookup Saxon/JXPath/etc.