- changed title to Simple way of optimizing Schema validation for url encoded form data
Simple way of optimizing Schema validation for url encoded form data
Issue #274
resolved
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)
-
reporter -
Available in v2.11.1
-
- changed status to resolved
- Log in to comment