Simple way of optimizing Schema validation for url encoded form data

Issue #274 resolved
Sven Döring created an issue

In case of url encoded form data the request body is parsed in the RequestBodyValidator. Then all form data is put into an ObjectNode. And that ObjectNode is transformed into a JSON string. In the next class, the SchemaValidator, this JSON string is parsed back into a JsonNode and the validation is done. 😏

Why not add a second method to the SchemaValidator, which takes a ready JsonNode instead of a String? That would save the extra serializing and deserializing step.

Comments (3)

  1. Log in to comment