saxon

We've been spending increasing amounts of time battling with the limitations of Microsoft's XSLT 1.0 processor. I think the time has come to start using XSLT 2.0. Saxon seems to be a good choice. The problem is - the Visual Studio integrated XSLT debugger is wonderful, and nobody wants to stop using it. My question - is there a way to supply your own processor for Visual Studio to use? Even if step-through debugging didn't work, it'd still be great to be able to run the XSLT from within Visual Studio (Alt+F5) rather than having to add some other software package to our workflow. It seems

Environment: eXist-db 4.2.1 , XQuery 3.1, XSLT 2.0 In eXist-db I am loading an XSLT file which includes a reference to a collection in eXist (in order to perform a search on documents found there, using a key). This reference seems to throw an error from Saxon. Exception while transforming node: Exception thrown by URIResolver XML docs are located at /db/apps/deheresi/data/ XSLT docs are located at /db/apps/deheresi/data/styles In the transform function, I am passing a parameter from XQuery to the XSLT file for the absolute path to the data folder: <param name="paramDatauri" value="xmldb:exist

I want to use saxon for xpath queries but i don't know to load multiple xml files. I'm trying to use saxon with command line from windows I read in saxon manual that i can use the command: Query.exe -s:myDataFile.xml -q:myQueryFile -o:myOutputFile but i don't know how to load multiple xml files and not just one edit: I have many xml files myDataFile1.xml, myDataFile2.xml, myDataFile3.xml ... and i want to run the query to alla these files So i want to load all all files and then query them (I don't want to query every single file and then concatenate the results) Use the standard XPath 2.0

My Spark job with HiveContext and Saxon working fine unless no UDFs defined in code. In case of UDF implementation - HiveContext initialization failed with error. I heard there are saxon\java8 incompability solved in saxon 9.5.1.5, which is not released yet as free version in central maven repository: Caused by: java.lang.RuntimeException: XPathFactory#newInstance() failed to create an XPathFactory for the default object model: http://java.sun.com/jaxp/xpath/dom with the XPathFactoryConfigurationException: javax.xml.xpath.XPathFactoryConfigurationException: java.util.ServiceConfigurationError:

I am trying to remove elements with the same href attribute form this file: <?xml version="1.0" encoding="UTF-8"?> <images> <item id="d1e152_1" href="Pic/104764.jpg" media-type="image/jpeg"/> <item id="d1e163_2" href="Pic/104764.jpg" media-type="image/jpeg"/> <item id="d1e174_3" href="Pic/104764.jpg" media-type="image/jpeg"/> <item id="d1e218_4" href="Pic/104763.jpg" media-type="image/jpeg"/> <item id="d1e349_5" href="Pic/110001.tif" media-type="image/tif"/> <item id="d1e681_6" href="Pic/199201.tif" media-type="image/tif"/> <item id="d1e688_7" href="Pic/124566.tif" media-type="image/tif"/> <

I'm trying to use the Saxon processor from java. I'm using the the saxon9ee.jar inside saxonee9-3-0-11j.zip (just downloaded, no license - is that needed so it'll work?) Their * * resources can be found here: http://www.saxonica.com/documentation/extensibility/functions/instance-methods.xml http://www.saxonica.com/documentation/extensibility/functions/staticmethods.xml My xsl: <?xml version="1.0"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:template match="/"> <xsl:value-of select="dateUtils:getCurrentFullDate()" xmlns:dateUtils="java:com.macfaq.math

First of all I have already exhaustively checked the following questions and this issue does not seem to be the same thing: SAXParseException: Content is not allowed in prolog org.xml.sax.SAXParseException: Content is not allowed in prolog “Content is not allowed in prolog” when parsing perfectly valid XML on GAE Content is not allowed in Prolog SAXParserException These all seem to boil down to 2 things: There is one or more (possibly invisible) chars before the opening <?xml?> tag. There is some byte sequence in the body that does not fit the encoding defined in the <?xml?> tag. Well as for