Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #6576

open

EE-Python erroring out when trying to create a Processor

Added by Matt Patterson about 2 months ago.

Status:
New
Priority:
Low
Assignee:
Matt Patterson
Category:
Saxon-C Internals
Start date:
2024-10-31
Due date:
% Done:

0%

Estimated time:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Found in version:
Fixed in version:
SaxonC Languages:
SaxonC Platforms:
All
SaxonC Architecture:

Description

With the current refactored-build version of SaxonC, when trying to run anything using EE, there's an exception:

Flag is true to create SaxonProcessor with license
Java DEBUG: j_getErrorMessageWithErrorCode called
Java Debug: Exception found: Could not initialize class net.sf.saxon.s9api.Processor
java.lang.NoClassDefFoundError: Could not initialize class net.sf.saxon.s9api.Processor
        at net.sf.saxon.option.cpp.SaxonCAPI.createSaxonProcessor(SaxonCAPI.java:153)

SaxonProc: JVM finalized calling !
Traceback (most recent call last):
  File "/Users/matt/Documents/work/saxonica/build-refactoring-cython/python/testsuite_driver/qt3_test_suite_driver.py", line 34, in <module>
    driver_proc = saxonc.PySaxonProcessor(license=True)
  File "src/saxonc/saxonc.pyx", line 226, in saxoncee.PySaxonProcessor.__cinit__
saxonc.SaxonApiException: Could not initialize class net.sf.saxon.s9api.Processor. Line number: -1

It's not clear what's going on here. The class in question appears to be present in the Jar fed to GraalVM.

No data to display

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF