OpenAPI4J
Table of contents
- Introduction
- Modules
- Versioning and compatibility
- Performance
- Native compilation (GraalVM)
- Supported versions
- Contributing
- License
Introduction
This is the home page of the openapi4j project for Java (Jakarta or JVM platform in general).
openapi4j is a suite of tools, including the following :
- Open API specification parser and validator.
- Open API Schema Object validator.
- JSON reference implementation.
- Request and response validator.
- For internal use only, performance project reports some numbers to ‘manually’ check any improvements or regressions between versions.
Modules
- Parser allows the (de-)serialization and manipulation of the schema and its validation.
- Schema validator allows the validation of data against a given schema.
- Request validator is high level module to manage validation for requests and/or responses against operations. More details in the related project.
- Request adapters is the repository of specific adapters to wrap requests and responses.
Versioning and compatibility
All modules follow the Semantic Versioning 2.0.0 and are aligned on each release even there’re no changes.
<dependency>
<groupId>org.openapi4j</groupId>
<artifactId>openapi-[module]</artifactId>
</dependency>
Snapshot is available for latest valid commit on ‘master’ branch.
Performance
Check here for some values.
Native compilation (GraalVM)
From version 0.7, the toolset is fully compliant with native compilation (AOT).
This was tested with GraalVM 19.3.1.
No further configuration or directive is needed to include the modules if available on classpath.
shell script native-image -H:+ReportExceptionStackTraces --no-fallback -jar your-app.jar
FYI, testing runs made don’t show much performance improvements but parser module.
Supported versions
The modules currently support the OpenAPI Specification (OAS) version 3.x.x.
See related projects for limitations and issues.
Contributing
Reporting issues, making comments, … Any help is welcome !
We accept Pull Requests via GitHub.
There are some guidelines which will make applying PRs easier for us :
- Respect the code style and indentation. .editorconfig file is provided to not be worried about this.
- Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted create a separate PR for this change.
- Provide JUnit tests for your changes and make sure your changes don’t break anything by running
gradlew clean check
. - Provide a self explanatory but brief commit message with issue reference if any, as it will be reported directly for release changelog.
License
openapi4j and all the modules are released under the Apache 2.0 license.
See LICENSE for details.