fixes #117

[GavinChenYan]

No description provided.

[ddobrin]

@ChenYan71 : there is a second problem here, which IO was looking into fixing today. discussed it with @stevehu yesterday:

• the RequestValidator "is a" MiddlewareHandler, which in turn is a LightHttpHandler.

Setting the status code only, without calling the LightHttpHandler.setExchangeStatus(), will preclude us from saving the error for auditing purposes.

Ex.:
ValidatorHandler - l.80 - setExchangeStatus(exchange, ...);
is preferable.

At this time, in case of an OpenAPI validation failure, my client can't audit the failure.

Do you wish to change that as well?

[GavinChenYan]

@ddobrin I will take a look

[stevehu]

@ChenYan71 @ddobrin Do you think we should call the validateRequestBody if the contentType is null? I am thinking that we only need to validate if the header is application/json only; however, there might be the case that the user forgets to put the contentType header and we want to catch the error with the validation.

[GavinChenYan]

@stevehu @ddobrin
Light-rest-4j is used for restful API and if user enabled openapi validation from config file means user defined the API specification by openapi. In this case, if the request header didn't specify contentType, the default contentType should be treat as application/json