[ 
https://issues.apache.org/jira/browse/XMLBEANS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16904427#comment-16904427
 ] 

Travis Schneeberger commented on XMLBEANS-539:
----------------------------------------------

PJ,

Thanks so much for the quick reply.  I had no idea that xmlbeans supported 
other xpath implementations.  This is very helpful and will improve some 
greenfield development we are doing that relies on xmlbeans. Might I suggest 
that you document this capability here: 
[https://xmlbeans.apache.org/docs/3.0.0/guide/conSelectingXMLwithXQueryPathXPath.html]
 and/or here: [https://xmlbeans.apache.org/documentation/conInstallGuide.html]. 
 After reading the current documentation around xpath, I was under the 
impression that I had to use saxon.

 

[Side note: in case you're curious, we selected xmlbeans because of it's very 
capable SchemaTypeSystem.  As far as I can tell it is the best library in the 
java space for discovering schema information]

> Support for newer versions of Saxon as an XPath engine
> ------------------------------------------------------
>
>                 Key: XMLBEANS-539
>                 URL: https://issues.apache.org/jira/browse/XMLBEANS-539
>             Project: XMLBeans
>          Issue Type: Wish
>          Components: XPath
>            Reporter: Srecko Mandelj
>            Priority: Major
>
> It is still a limitation of using old version of Saxon to achieve xpath 
> search in XmlBeans. It would be nice to be able to use Saxon HE with 
> XmlBeans. Older versions of saxon (including early versions of HE prior to 
> 9.5) have problems with new versions of java (getting error 
> /lib/saxon9-xpath.jar/META-INF/services/javax.xml.xpath.XPathFactory:2: 
> Illegal configuration-file syntax at 
> java.xml/javax.xml.xpath.XPathFactory.newInstance(XPathFactory.java:119)).



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to