Global and Per-client properties to disable default ResponseExceptionMappe #408
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Global and Per-client properties to disable default ResponseExceptionMapper
and properties to disable invoking ResponseExceptionMapper when method return type is jakarta.ws.rs.core.Response
documentation will need to be updated downstream:
New property effective in both programatic client api and global config:
microprofile.rest.client.disable.response.exceptions - disables invoking client exception mapper when the proxy method return type is akarta.ws.rs.core.Response
New annotation keyed properties:
{fqcn | key}/mp-rest/disableResponseExceptions - per client
microprofile.rest.client.disable.response.exceptions
configuration{fqcn | key}/mp-rest/disableDefaultMapper - per client
microprofile.rest.client.disable.default.mapper
configurationCloses #23957, #44813