Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
MIME-Version: 1.0
In-Reply-To: <56F10B05.8090603@gmail.com>
References: 
 <CA+pBWhvF8ySMtWAc0HWArJbBrYAPMofbttMbnybKBNyF9_7xig@mail.gmail.com>
	<56F10B05.8090603@gmail.com>
Date: Wed, 23 Mar 2016 17:40:47 +0100
Message-ID: 
 <CA+pBWhuKSNHWWd8JPsA-JZ540vuojXgO++1xakJEfQ70RiZkqA@mail.gmail.com>
Subject: Re: Using Interceptors on JAX-RS 2.0 Client
From: =?UTF-8?B?RWlyaWsgQmrDuHJzbsO4cw==?= <eirbjo@gmail.com>
To: dev@cxf.apache.org
Content-Type: multipart/alternative; boundary=001a1133b3e6eea589052eb9fd1a

--001a1133b3e6eea589052eb9fd1a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Sergey,

Our observation (with 3.0.3 I think) was that the feature was not ignored,
but instead initialized once per request. Which added new interceptors to
the WebClient on every request. Not sure I understand the intention behind
this design.

I think I just assumed that I could use Interceptors for JAX-RS clients
just like JAX-WS.

We could and probably will rewrite these to JAX-RS filters, but it would of
course be even sweeter if we could simply reuse the logging interceptors we
currently use for our SOAP services.

Cheers,
Eirik.
On Mar 22, 2016 10:08 AM, "Sergey Beryozkin" <sberyozkin@gmail.com> wrote:

> Hi
>
> It is not possible to register CXF specific Feature or Interceptor
> with JAX-RS 2.0 Client API.
>
> When you do "client.register(new MyLoggingFeature())", assuming it is CXF
> Feature, then it will be currently ignored.
>
> I wonder if it might make sense to create some JAX-RS 2.0 FeatureWrapper
> which can wrap an arbitrary CXF Feature...I'll try to experiment with it.=
..
>
> Sergey
>
>
>
> On 22/03/16 01:56, Eirik Bj=C3=B8rsn=C3=B8s wrote:
>
>> Hello,
>>
>> Is the CXF implementation of the JAX-RS 2.0 client API designed to allow
>> Interceptors to be configured on Clients? If so, how should this be done=
?
>>
>> Say we have a Client built like this:
>>
>>     Client client =3D ClientBuilder.newClient();
>>
>> and we want to configure Logging[In/Out]Interceptors of this client. (Ju=
st
>> as an example).
>>
>> First I tried in various ways to get an Endpoint out of the client, but
>> failed at that.
>>
>> Then, after looking through the implementation classes of
>> Client/WebTarget,
>> I discovered that you can register CXF Features on a Client using
>> something
>> like
>>
>>      client.register(new MyLoggingFeature());
>>
>> However, with this setup MyLoggingFeature.initialize(InterceptorProvider
>> ip, Bus bus) is called _once per request_.
>>
>> Not exactly what I wanted since it lead to the interceptor chains being
>> filled up with duplicate LoggingInterceptors.
>>
>> I might perhaps have misunderstood the lifecycle of Clients and/or
>> WebTargets. Should be ok to reuse a JAX-RS 2.0 Client, right?
>>
>> Can someone please enlighten me? Did I perhaps miss some relevant
>> documentation?
>>
>> Cheers,
>> Eirik.
>>
>>
>

--001a1133b3e6eea589052eb9fd1a--