Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MicroProfile Client ProblemResponseExceptionMapper is not called #31

Open
jpraet opened this issue May 3, 2024 · 0 comments
Open

MicroProfile Client ProblemResponseExceptionMapper is not called #31

jpraet opened this issue May 3, 2024 · 0 comments

Comments

@jpraet
Copy link
Contributor

jpraet commented May 3, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant