cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Carman <ja...@carmanconsulting.com>
Subject Re: Local "Fallback" Support?
Date Thu, 11 May 2017 10:58:52 GMT
I'm thinking this is less of a "JAX-RS thing" and more of an "object
thing", meaning the pattern is more general.
On Thu, May 11, 2017 at 6:55 AM Sergey Beryozkin <sberyozkin@gmail.com>
wrote:

> WriterInterceptor registered on the client side can set a custom
> entity...ClientResponseFiler - a custom entity stream...
>
> Sergey
> On 11/05/17 11:53, James Carman wrote:
> > 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 <sberyozkin@gmail.com>
> > 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"?
> >>>
> >>
> >>
> >
>
>
> --
> Sergey Beryozkin
>
> Talend Community Coders
> http://coders.talend.com/
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message