You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JsonPath evaluation currently walks the AST directly (interpreter-style).
We have some ongoing work in May 2026 to support two JDT versions:
The original Java 21 interpreted version, which is fine for one-time config loading, or infrequent code paths
A Java24+ bytecode generator that makes Java21 bytecode, which is for hot path validation, where the compiling can be ahead of time to deploy validators that were generated by a build system. (Yet it can of course also be run on demand in a JDK, yet hot deploy of new schema validators seems a rather niche use case.)
This ticket serves as a marker to follow the same patterns as the JSON Path engine. Have the interpreted version and a parallel bytecode-generated version that can be run as a build-time tool.
Activity
Issue #128 Refactor JsonPath to sealed interface with AST interpreter
Issue #128 Make JsonPath an interface
Issue #128 Implement runtime compilation for JsonPath queries
Issue #128 Document runtime compilation feature
Issue #128 Add runtime-compiled JsonPath
Issue #128 Fix JsonPathAstBacked method visibility
Issue #128 Fix JsonPathRuntime slice lambdas
Issue #128 Fix unsupported recursive descent targets to match interpr…
Issue #128 Define generated JsonPath in same loader
Issue #128 Address all PR review comments