My vote would be to support just Saxon-HE. We can look at adding support for other XQuery providers if people request them. If there any users if these other providers, then can stick with XMLBeans 3 (until we can add back support). It just seems best not to expend too much time on this until we have evidence the time is needed.
On Sunday 30 August 2020, 23:01:24 GMT+2, Andreas Beeker <[email protected]> wrote: Hello devs, XmlBeans reflects into the following classes (and Saxon helpers) when searching for a Xquery implementation: - org.apache.xmlbeans.impl.store.OXQXBXqrlImpl - org.apache.xmlbeans.impl.store.XqrlImpl - org.apache.xmlbeans.impl.store.Xqrl2002Impl I still have to find those classes / sources, but they seem to be included in 3rd party libs. [1] [2] In the advent of using JPMS, those classes should be packaged in the xmlbeans module. How should we react? a) keep the old implementation as-is without testing it's functionality - it for sure doesn't work with JPMS b) try to reach out to the commercial providers and update the adapters c) remove the obsolete calls and only use Saxon Andi [1] https://software.databasedevelop.com/article/14040274/Unable+to+get+Metadata+Manager+for+DVM+%22TicketingServices+resources+XQ+Ticketing_AttributeValuesDVM%22 [2] http://www.oracle.com/technetwork/database/database-technologies/bdc/big-data-connectors/downloads/index.html (Oracle XQuery for Hadoop) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
