Saxon » SaxonC

I have now also tried to compile the stylesheet and to use an executable but that hits a different error:

from saxonche import *

with PySaxonProcessor(license=False) as saxon_proc:
    xslt30_processor = saxon_proc.new_xslt30_processor()

    element_names = ['foo', 'foobar']

    xslt_param = PyXdmValue()

    for name in element_names:
        xslt_param.add_xdm_item(saxon_proc.make_string_value(name))

    print(xslt_param)

    xslt30_processor.set_parameter('cdata-tag-names', xslt_param)

    xslt30_executable = xslt30_processor.compile_stylesheet(stylesheet_file='serialize-wrap-in-cdata1.xsl')

    xslt30_executable.transform_to_file(source_file='sample2.xml', output_file='result-sample2.xml')

Error

Traceback (most recent call last):
  File "C:\Users\marti\PycharmProjects\SaxonCHEWrapChildrenInCDATA\main3.py", line 17, in <module>
    xslt30_executable = xslt30_processor.compile_stylesheet(stylesheet_file='serialize-wrap-in-cdata1.xsl')
  File "python_saxon\saxonc.pyx", line 1157, in saxonche.PyXslt30Processor.compile_stylesheet
saxonche.PySaxonApiError: NullPointer exception found: java.lang.NullPointerException
	at net.sf.saxon.s9api.XsltCompiler.setParameter(XsltCompiler.java:161)
	at net.sf.saxon.option.cpp.Xslt30Processor.setStaticParametersFromArray(Xslt30Processor.java:449)
	at net.sf.saxon.option.cpp.Xslt30Processor.compileFromFile(Xslt30Processor.java:305)
. Line number: -1

Using SaxonC HE 12.2 from the command line (in Powershell) with a cmd line as ` & 'C:\Program Files\Saxonica\libsaxon-HEC-windows-v12.2\command\Transform.exe' -t -s:.\sample2.xml -xsl:.\serialize-wrap-in-cdata1.xsl ?cdata-tag-names="'foo','foobar'" works fine so the XSLT seems fine; just need to find a way to pass the parameter from Python.

O'Neil Delpratt wrote in #note-3:

I think this bug is the same as #6053 which has now been fixed. Available in the next maintenance release.

Probably not a practical workaround but you could avoid using the for loop to create the XdmAtomicValue's.

So not using a loop and using e.g.

    xslt30_processor = saxon_proc.new_xslt30_processor()

    xslt_param = PyXdmValue()


    xslt_param.add_xdm_item(saxon_proc.make_string_value('foo'))
    xslt_param.add_xdm_item(saxon_proc.make_string_value('foobar'))

    print(xslt_param)

    xslt30_processor.set_parameter('cdata-tag-names', xslt_param)

should avoid the crash? I still get

Traceback (most recent call last):
  File "C:\Users\marti\PycharmProjects\SaxonCHEWrapChildrenInCDATA\main5.py", line 20, in <module>
    xslt30_executable = xslt30_processor.compile_stylesheet(stylesheet_file='serialize-wrap-in-cdata1.xsl')
  File "python_saxon\saxonc.pyx", line 1157, in saxonche.PyXslt30Processor.compile_stylesheet
saxonche.PySaxonApiError: NullPointer exception found: java.lang.NullPointerException
	at net.sf.saxon.s9api.XsltCompiler.setParameter(XsltCompiler.java:161)
	at net.sf.saxon.option.cpp.Xslt30Processor.setStaticParametersFromArray(Xslt30Processor.java:449)
	at net.sf.saxon.option.cpp.Xslt30Processor.compileFromFile(Xslt30Processor.java:305)
. Line number: -1

I can't tell from the description in https://saxonica.plan.io/issues/6053 how "PydmNode object gets deleted before reuse" is a duplicate of this bug throwing while trying to create a sequence of XdmAtomicValues and pass it as a parameter to XSLT.

Bug https://saxonica.plan.io/issues/6053 was fixed weeks ago, any chance there is a Window wheel with the fix in the Saxonica Github build artefacts so I could test whether this parameter passing works? Or did you test it? Then let me know.

Sorry for asking but on the surface the "duplicate" resolution is not clear, the description there sounds quite different and there is no stack trace to tell.