- Email: email@example.com
- Registered on: 2012-02-01
- Last connection: 2021-02-24
Solution: in CommandLineOptions.applyFileParameters() add code as follows:
List<XdmNode> nodeList = new ArrayList<>(sourceList.size());
DocumentBuilder builder = processor.newDocumentBuilder();
... Bug #4919: Line numbering not applied to files supplied on command lineWhen a file is supplied as a command line parameter using the syntax +param=filename.xml, and when the -l option is present on the command line, the supplied file does not have line numbers available.
Very hard to give much help on this, because (a) it's very dependent on your filestore configuration, and (b) Saxon isn't detecting the error, it's only passing the message on.
Have you switched on all the available diagnostic switche... Help: RE: I/O error reported by XML parser processing file when running XSLT (Saxon PE 22.214.171.124J)
We are beginning the process of migrating from a lightly-modified version of the NLM Journalpublishing 3.0 DTD to a lightly-modified version of the JATS v1.2 DTD for our in-house editing and processing. I have been working on the ini...
I don't know if it will solve the problem for you, but what you're doing is certainly inefficient. Rather than constructing the transformation result as an in-memory tree and then serializing it, you should send the output directly to a ... Support #4918: OutOfMemoryError for 48MB XML Input XdmNode.toString()Hello,
I'm creating a "serverless" Azure Functions Web API runs XSLT transforms that is used by an application I'm developing to validate XML documents.
I'm getting an `OutOfMemoryError: Java heap space` when running the Xslt30Tran...
I suspect the optimisation can be simplified anyway. I think `(A < N to M)` can be simplified to `A < M`. Bug #4916: Range expression optimization not workingTest case op:to RangeExpr-409d is running very slow. It appears not to be optimising the minimax test properly.
Bug #4915 (New): NestedIntegerValue is only partially implementedThe type saxon:nestedIntegerValue is partially implemented. It validates values of the form 123.45.00.1. It was implemented to meet a practical need and as an experiment in schema extensibility, but it is not well tested and supported. F...
Please start a new thread with the new question, and be precise: attach the files so that we can reproduce the problem.
There are some errors that can only be detected at the end, for example an IDREF attribute for which there is no c... Help: RE: Command Line to Java Programjava net.sf.saxon.Query -qs:. -s:source.xml -dtd:on
The transpiler code is being developed on the assumption that it's for our own use only -- I'm following the maxim from Fred Brooks' mythical man month that writing a program that does exactly what you need and is intended only for your ... Feature #2871: .NET Core supportHi,
We are working on an application in .NET Core and would like to use Saxon. If we target the .net framework 4.5.1 in our project we can use Saxon. But as off .NET Core 1.0 we have to copy the 'saxon9he-api.dll' dll by hand to the...
Saxon tries to handle classpath URIs wherever possible. But it can't force third-party code to handle them. Help: RE: Saxon 10.3 and classpath: schemeI have found that "classpath:" scheme does not work as I expected.
I'm not sure whether it is by design or a bug, so I just put it here:
Consider a folder structure:
Also available in: Atom