The use case is to allow for a local implementation (with canned responses perhaps) to answer if a remote system is down. The more I think about it, I don't know if I like this being a "magic" thing, but more of a regular old pattern. I'm going to tinker a bit. Thanks for following up. On Thu, May 11, 2017 at 5:11 AM Sergey Beryozkin <[email protected]> wrote:
> Hi James > > What is available is ResponseExceptionMapper which can be registered as > JAX-RS provider and it will convert the exceptions to some custom > responses. > > JAX-RS 2.0 ClientResponseFilter can also be registered with the proxy. > > Perhaps something else can be improved for proxies, can you explain what > exactly you'd like to achieve with such a fallback support ? > > Sergey > On 10/05/17 18:34, James Carman wrote: > > Is there a way to provide an object that implements the JAX-RS service > > interface that I'm using to generate a proxy to CXF and say "if you get > an > > exception when calling the remote service, talk to this bean instead"? > > > >
