You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As observed by the code coverage, it turns out the ProblemResponseExceptionMapper is never called. Instead, the JAX-RS ProblemClientResponseFilter takes precedence, and the thrown ResponseProcessingException is being unwrapped by:
Can we remove the ProblemResponseExceptionMapper?
Are all MicroProfile REST client implementations guaranteed to implement this unwrapping behavior (which differs from JAX-RS)?
Or alternatively can we prevent the ProblemClientResponseFilter from being picked up by MicroProfile REST client?
The text was updated successfully, but these errors were encountered:
As observed by the code coverage, it turns out the ProblemResponseExceptionMapper is never called. Instead, the JAX-RS ProblemClientResponseFilter takes precedence, and the thrown ResponseProcessingException is being unwrapped by:
https://github.com/resteasy/resteasy/blob/120abda3249de866a8269b9fd2128ddce318eedb/resteasy-client-microprofile-base/src/main/java/org/jboss/resteasy/microprofile/client/ProxyInvocationHandler.java#L157-L162.
Can we remove the ProblemResponseExceptionMapper?
Are all MicroProfile REST client implementations guaranteed to implement this unwrapping behavior (which differs from JAX-RS)?
Or alternatively can we prevent the ProblemClientResponseFilter from being picked up by MicroProfile REST client?
The text was updated successfully, but these errors were encountered: