Getting Return Code 422 for invalid models expecting 400

[bjoernhoeper]

Problem

When you specify a model that is malformed or missing information the server generates a HTTP status code 422 (Unprocessable Content) which is not specified as status code in the Swagger and thus leads to problems with generated clients as the response can not be deserialized.

** Proposed Solution **

Return status code 400 (Bad Request) or trigger adaptation of the specification to accept 422 as status code.