I received NullPointerException using Saxon 10, but was able to fix it, as follows:
In Saxon10Core, change:
new LargeAttributeMap(attributeList),
to:
attributeList.size() == 0 ? EmptyAttributeMap.getInstance() : new LargeAttributeMap(attributeList),
Hi Christopher,
that is interesting because my implementation is intensely tested with Saxon10 against the XProc 3.0 testsuite. No errors show up, so there seems to be a missing case in the testsuite.
Could you provide us with an XProc example where the error shows up and the error message raised by MorganaXProc-IIIse.
As I currently do not see, what problem you are going to fix, I need an example pipeline for my implementation report to.
Thanks for this,
Achim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
See attached break10.xpl for the pipeline that exhibits the behavior. See attached break10.log for Morgana's output. It crashes on the <xsl:copy> because it doesn't have any attributes.
Thank Christopher. As I see from you log, the bug comes in with Saxon 10.1, while I test against Saxon 10.0.
Saxon 10.1 was released after the Saxon10Connector, so it not supported currently. If you switch back to Saxon 10 the bug will disappear.
There is already a feature request for supporting 10.1. As a general rule I will allways support the stable version (9.9.17) and possibly another one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm a bit confused by your statement regarding release dates.
"The June release (rel 0.9.3.7-beta) was published on 2020-06-27."
"Saxon 10.1 maintenance release for Java, released 14 May 2020."
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for beeing inprecise: Saxon10Connector was added with rel. 0.9.1.7 on March 22th. According to "changelog.txt" it has not been updated since then.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Christopher,
that is interesting because my implementation is intensely tested with Saxon10 against the XProc 3.0 testsuite. No errors show up, so there seems to be a missing case in the testsuite.
Could you provide us with an XProc example where the error shows up and the error message raised by MorganaXProc-IIIse.
As I currently do not see, what problem you are going to fix, I need an example pipeline for my implementation report to.
Thanks for this,
Achim
See attached
break10.xplfor the pipeline that exhibits the behavior. See attachedbreak10.logfor Morgana's output. It crashes on the<xsl:copy>because it doesn't have any attributes.Thank Christopher. As I see from you log, the bug comes in with Saxon 10.1, while I test against Saxon 10.0.
Saxon 10.1 was released after the Saxon10Connector, so it not supported currently. If you switch back to Saxon 10 the bug will disappear.
There is already a feature request for supporting 10.1. As a general rule I will allways support the stable version (9.9.17) and possibly another one.
I'm a bit confused by your statement regarding release dates.
"The June release (rel 0.9.3.7-beta) was published on 2020-06-27."
"Saxon 10.1 maintenance release for Java, released 14 May 2020."
Sorry for beeing inprecise: Saxon10Connector was added with rel. 0.9.1.7 on March 22th. According to "changelog.txt" it has not been updated since then.
It looks like Saxon wants us to call
net.sf.saxon.om.AttributeMap.fromList. That way it will be compatible with both 10.0 and 10.1.Maybe. I have not yet decided what Saxon version will be supported for the July release. I think its to early to tell now.
Fixed with 0.9.4-beta