Philip Fearon
- Email: pgfearo@gmail.com
- Registered on: 2012-02-02
- Last connection: 2020-05-01
Issues
- Assigned issues: 0
- Reported issues: 59
Projects
Activity
2020-04-15
-
Yes, on reflection and from what you say, I should look into other options. Specifying an errorListenerClass looks especially appealing, at least for the short-term. Longer term, a dedicated VSCode Language Server would provide much bett... Feature #4516: When using the command-line, errors/warnings to stdout give the XSLT give filename or source, but no path(With Saxon 10.0)
When invoking an XSLT from the command-line, if warnings or errors are emitted to stdout/stderr, I would like to be able to uniquely identify the source file location that is the cause of the warning or error. Curre...
2020-04-13
-
OK, thanks for looking into this. The reason for this request was to allow any downloaded version of Saxon to integrate easily with the VSCode editor using an [extension TaskProvider](https://github.com/DeltaXML/vscode-xslt-tokenizer/wik... Feature #4516: When using the command-line, errors/warnings to stdout give the XSLT give filename or source, but no path(With Saxon 10.0)
When invoking an XSLT from the command-line, if warnings or errors are emitted to stdout/stderr, I would like to be able to uniquely identify the source file location that is the cause of the warning or error. Curre...
2020-04-10
-
Feature #4516 (Closed): When using the command-line, errors/warnings to stdout give the XSLT give filename or source, but no path(With Saxon 10.0)
When invoking an XSLT from the command-line, if warnings or errors are emitted to stdout/stderr, I would like to be able to uniquely identify the source file location that is the cause of the warning or error. Curre...
2018-11-21
-
Bug #4045 (Closed): Null pointer exception when compiling stylesheet with template containing specific XSLT instructionsUsing Saxon 9.9.0.2 professional (java), the attached saxon9902issue.xsl stylesheet fails to compile, producing the following stack trace. With Saxon 9.9.0.1, no exception is thrown.
~~~
java.lang.NullPointerException
at net.sf.saxon...
2018-05-11
-
Bug #3780 (Closed): java.lang.RuntimeException: Internal error when adding a map to the final result treeUsing Java build of Saxon 9.8.0.12.
The development XSLT supplied here is incomplete and is flawed in the sense that it is attempting to add a map to the final result tree. I would expect some exception, but not an internal error (repr...
2015-08-31
2014-04-21
2013-10-01
-
Support #1915 (Resolved): Test case for Saxon XSLT Performance comparisonThis test case for XSLT shows a significant difference in performance for different Saxon versions
so I thought it might be of interest. On Saxon 9.5.1.2 the test runs 90 time faster than for Saxon 9.3.1.1.
I just ran the XSLT from th...
2013-05-21
-
An alternative is to use a server-side service to act as a 'reverse-proxy' - where you append the required URL as an agrument in the HTTP request to your own server so its not cross-domain. Your own server then makes the request using th... Saxon-CE help: RE: state of the art with respect to cross domainwhats the best idiom for dealing with pulling down data using fn:doc these days with saxon-ce ?
2013-04-12
-
From a JavaScript function invoked with a number argument from Saxon-CE, the .constructor property of the argument returns: 'function Object() { [native code] }'
As in the following code:... Saxon-CE help: RE: Data types of numeric parameters passed to javascript functionsI've just started experimenting with Saxon-CE. I need to do some maths involving trig functions, which I think I'm better off doing in javascript (but would be happily persuaded otherwise!). However, I have not got past the basic hurdle ...
Also available in: Atom