Consider moving from java-json-tools/json-schema-validator to networknt/json-schema-validator
#1396
Comments
|
@lbroudoux I want to work on this issue. |
|
Awesome! Do you need some guidance? |
|
@lbroudoux I started exploring both the libraries. Can you suggest some documentation for |
|
Not really as I didn't start exploring it on my own... However I remember checking this one https://github.com/networknt/json-schema-validator/blob/master/doc/schema-retrieval.md that looks of interest for our external schema or fragments retrieval use-case. In current library, it's called |
|
@lbroudoux I did some research on the classes of |
|
Looks like it is called See the example on the README: Set<ValidationMessage> assertions = schema.validate(input, InputFormat.JSON, executionContext -> {
// By default since Draft 2019-09 the format keyword only generates annotations and not assertions
executionContext.getExecutionConfig().setFormatAssertionsEnabled(true);
}); |
Reason/Context
As of today, we used
java-json-tools/json-schema-validatorfor all the things related to JSON schema validation in OpenAPI, AsyncAPI and GraphQL schema tests. However, this library seems to be no longer maintained with the latest release being more that 4 years old (see https://github.com/java-json-tools/json-schema-validator).Description
New Java Json Schema validation implementations have been started since then and are in active development. The JSON Schema website list a few of them here.
According to Creekservice Performance Benchmark (see here) and Bowtie service ran by the JSON Schema community (see here), the
networknt/json-schema-validatorseems to be a very good candidate with recent releases, very active community and compatible license.We should give it a try as a replacement for the current solution and check if there are performance benefits.
Implementation ideas
No response
The text was updated successfully, but these errors were encountered: