I figured it out. My ResponseExceptionMapper was using the original Response when it instantiated the WebApplicationExceptions, so it was showing as a non-null entity and the wae spec optimization stuff was kicking in. I think I know how to fix it now.
On Sat, Jan 12, 2019 at 9:22 AM James Carman <[email protected]> wrote: > I have a situation where I have one JAX-RS service calling another via a > client proxy (non-MP). It looks like CXF is not calling my registered > ExceptionMapper<WebApplicationException> when my code encounters a > WebApplicationException thrown (per my custom ResponseExceptionMapper) by a > client proxy during an invocation to a downstream service? It appears that > the Response object (or Message, more likely) received from the downstream > service is somehow taking over the current Response, because I also see > some duplicate headers (my services add some response headers to each > response). My expectation was that when my custom ResponseExceptionMapper > yields a WebApplicationException, then my custom > ExceptionMapper<WebApplicationException> would be called in order to > convert that WebApplicationException into a Response. >
