O'Neil Delpratt
O'Neil Delpratt- Email: oneil@saxonica.com
- Registered on: 2012-01-26
- Last connection: 2018-12-12
Issues
- Assigned issues: 41
- Reported issues: 242
Projects
Activity
2019-01-15
-
Bug fixed on the Saxon 9.9 branch. Bug #4088 (Resolved): Serialization with ResultDocumentHandler doesn't take output properties def...This is related to https://saxonica.plan.io/issues/4087 but I file this as a separate issue as I am now convinced this is a bug (various samples run fine when used with Java, both from the command line and the API, and with .NET from the... -
The issue is the handling of ResultDocuments on .NET relies on IResultDocumentHandler interface, which works with a OutputURIResolver class on Java. The OutputURIResolver interface from Saxon 9.9 is obsolescent. It is unable to handle th...· Commented on issue
2019-01-14
-
Update,
The only difference on the Saxon 9.9 is that the Serializer can only be created via the Processor. This is now inline with how it is done on the Java platform. I can confirm that we are getting the same error on Saxon 9.9 for ... Bug #4088 (In Progress): Serialization with ResultDocumentHandler doesn't take output properties ...This is related to https://saxonica.plan.io/issues/4087 but I file this as a separate issue as I am now convinced this is a bug (various samples run fine when used with Java, both from the command line and the API, and with .NET from the...
2019-01-09
-
There ha been significant changes to the XmlDestination and how we manage the sub-classes such as the Serializer in Saxon 9.9. These changes we hope are not too disruptive for users. Bug #4088: Serialization with ResultDocumentHandler doesn't take output properties defined with "...This is related to https://saxonica.plan.io/issues/4087 but I file this as a separate issue as I am now convinced this is a bug (various samples run fine when used with Java, both from the command line and the API, and with .NET from the...
-
Yes this is a bug. I have managed to reproduce the error message.· Commented on issue
2018-12-20
-
Thanks for sending the files. As it turns out this is a bug which was fixed in Saxon-HE version 9.8.0.8.
It is related to bug issue: #3062
Also some notes of the bug issue on the forum post see: https://saxonica.plan.io/boards/3/top... Saxon/C Help and Discussions: RE: Problem applying XSL xsl:copy-of when sub node has attribute xs...Greetings,
We have been so far using PHP default XSLT processor (libxslt) but would like to benefit from XSLT2 features at least. I am trying to test our current XSLs with " Saxon/C 1.1.0 running with Saxon-HE 9.8.0.4J" but I am stuck...
2018-12-19
-
Hi,
Thanks for reporting the issue you are having. Please can you send the code snippet or add it to this forum post.
It is highly possible the Saxon-HE 9.8.0.4 version used in Saxon/C has a bug which has since been fixed in a main... Saxon/C Help and Discussions: RE: Problem applying XSL xsl:copy-of when sub node has attribute xs...Greetings,
We have been so far using PHP default XSLT processor (libxslt) but would like to benefit from XSLT2 features at least. I am trying to test our current XSLs with " Saxon/C 1.1.0 running with Saxon-HE 9.8.0.4J" but I am stuck...
2018-12-13
2018-12-12
-
Update:
So far we have managed to trigger this code with the following nunit test case:
~~~ java
public static String p(String a, Object b) {return "test";}
public static String p(Object a, String b) {return "test";}
~~~
Th... Bug #4041: Overloaded extension functions in .NETThe .NET code for reflexive extension functions appears not to be handling overloaded methods (where more than one method matches the requirement and it's not possible to make an early decision which to use). (Search DotNetExtensionLibra...
2018-12-10
Also available in: Atom
.