Hello Sergey, Thank you very much for clarification. Based on the examples I encountered, I suspected that's the case and by looking at the source code, I could not figure out where registered provider would be called to deserialize the response inputstream into an object. But I could not be 100% sure. I settled with a solution where my ResponseExceptionMapper can optionally take a mapping of response status code - corresponding Throwable (and configure Jackson ObjectMapper to ignore unknown properties) and creates an appropriate instance of Throwable instance (if all fails, just return ServerWebApplicationException). When proxies is used, then, it'll be used via provider configuration and if webClient is used, then call "fromResponse" explicitly in the catch clause and get deserialized Throwable and throw that instead. I very much appreciate you taking time to respond to my question! Best regards!
-- View this message in context: http://cxf.547215.n5.nabble.com/WebClient-ResponseExceptionMapper-provider-mapper-is-not-being-called-tp5520604p5523444.html Sent from the cxf-user mailing list archive at Nabble.com.
