Skip to content

Conversation

@Ostrzyciel
Copy link
Member

@Ostrzyciel Ostrzyciel commented Sep 14, 2025

Closes #220

This took me a while to figure out. Unfortunately we cannot query the XML parsing limits directly, as that's considered JVM-internal, so we instead check the JVM version. If someone uses a different JVM that does not follow these limits... well, sorry, we have no way of checking that, really.

We set the higher limits through a barely documented (just Javadoc) API in Graal. This is also used by Quarkus, so it should be fine.

The new jelly-cli v output looks like:

jelly-cli   0.7.1+7-315c088c+20250914-1349-SNAPSHOT
-------------------------------------------------------------
Jelly-JVM   3.5.1
Apache Jena 5.3.0
JVM         Substrate VM 24+36
-------------------------------------------------------------
[X] JVM reflection: supported. Parsing optimizations enabled.
[X] Large RDF/XML file parsing: supported.

Copyright (C) 2025 NeverBlink and contributors.
Licensed under the Apache License, Version 2.0.
For details, see https://www.apache.org/licenses/LICENSE-2.0
This software comes with no warranties and is provided 'as-is'.
Documentation and author list: https://github.com/Jelly-RDF/cli

@Ostrzyciel Ostrzyciel enabled auto-merge (squash) September 14, 2025 12:28
@Ostrzyciel Ostrzyciel merged commit d1a7d17 into main Sep 14, 2025
8 checks passed
@Ostrzyciel Ostrzyciel deleted the GH-220/support-large-xml-files branch September 14, 2025 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Large XML file parsing fails in AoT builds due to JAXP limits

2 participants