This handler is part of the light-rest-4j which is built on top of light-4j but focused on RESTful API only. Also, it only works with OpenAPI 3.0 specification.

It encourages design driven implementation so OpenAPI specification should be done before the implementation starts. With the light-codegen light-4j generator, the server stub can be generated and start running within seconds. However, we cannot rely on generator for validation as specification will be changed along the life cycle of the API. This is why we have provided a validator that works on top of the specification at runtime. In this way, the generator should only be used once and the validator will take the latest specification and validate according the specification at runtime.

Fail fast

As you may noticed that our Status object only supports one code and message. This is the indication the framework validation is designed as fail fast. Whenever there is an error, the server will stop processing the request and return the error to the consumer immediately. There are two reasons on this design and it is documented in fail-fast in design section.

ValidatorHandler

This is the entry point of the validator and it is injected during server start up if validator.yml enableValidator is true. By default, only RequestValidator will be called. Response validation should be done in the client module.

Configuration

From release 1.5.18, the light platform supports multiple chains of middleware handlers and multiple frameworks mixed in the same service instance. To have a validator configuration file for different frameworks, a new openapi-validator.yml with the same content has been introduced. The validator.yml is still loaded if openapi-validator.yml doesn’t exist for backward compatibility.

Here is an example of openapi-validator.yml

# This is specific OpenAPI validator configuration file. It is introduced to support multiple
# frameworks in the same server instance and it is recommended. If this file cannot be found,
# the generic validator.yml will be loaded as a fallback.
---
# Enable request validation. Response validation is not done on the server but client.
enabled: true
# Log error message if validation error occurs
logError: true

RequestValidator

It will validate the following:

• uri
• method
• header
• query parameters
• path parameters
• body if available

When necessary, json-schema-validator will be called to do json schema validation.

ResponseValidator

It will validate the following:

• header
• response code
• body if available

when necessary, json-schema-validator will be called.

SchemaValidator

If schema is defined in openapi.json, then the json-schema-validator will be called to validate the input against a json schema defined in draft v4.

Test

In order to test validator, the test suite starts a light-4j server and serves petstore api for testing. It is a demo on how to unit test your API during development.