#482 Support for application/problem+json deserialization for RestClients

[lwitkowski]

Changes

• jackson deserializer for HttpProblem
• jsonb deserializer for HttpProblem
• ThrowingHttpProblemClientExceptionMapper for RestClients to deserialize application/problem+json and throw as HttpProblem
• fix for MAJOR: Response is truncated when calling from one service to another and error happens on backend #429
• documentation

Closes #482, closes #429, related to #473

[lwitkowski]

In the fix for #429 I still decided to pass all headers except the one that caused issue ('content-length'), but the more I think about it the more I believe this extension should not pass any header by default (mainly for safety reasons, but it may be also error-prone).

Maybe we should introduce quarkus.resteasy.problem.proxy-pass-header config option (default empty) with explicit list of headers developers decide they want to pass from upstream service to gateway clients. In both scenarios (with ThrowingHttpProblemClientExceptionMapper and without).

WDYT?

edit: I've extracted this topic to #485, I suggest we continue the discussion over there.

[pazkooda]

Beside one minor thing look really good!

[lwitkowski]

Beside one minor thing look really good!

Thanks man, would you mind having a look at this comment? #483 (comment)

edit: followed up #485

[melloware]

This is great!

[melloware]

I have archived my Repo and left a note saying that all features have been ported into this extension:
https://github.com/melloware/quarkus-openapi-problem