lue in any object and it is not my
intention to modify the server implementation just to verify this.
Regards,
J.P.
-Original Message-
From: Andriy Redko
Sent: dinsdag 4 juli 2023 22:04
To: Jean Pierre URKENS ; CXF Dev List
Subject: Re: Apache CXF JAX-RS threadsafe clients
Hi Je
be needed to verify whether headers are passed
> correctly for each API invocation?
> Regards,
> J.P.
> -Original Message-
> From: Andriy Redko
> Sent: vrijdag 30 juni 2023 3:59
> To: Jean Pierre URKENS ; CXF Dev List
>
> Subject: Re: Apache CXF JAX-RS thread
rify whether headers are passed
correctly for each API invocation?
Regards,
J.P.
-Original Message-
From: Andriy Redko
Sent: vrijdag 30 juni 2023 3:59
To: Jean Pierre URKENS ; CXF Dev List
Subject: Re: Apache CXF JAX-RS threadsafe clients
Hi Jean,
Yes, I belie
return
> Response.status(Status.INTERNAL_SERVER_ERROR).entity(e.getMessage()).build();
> }
> }
> Regards,
> J.P.
> -Original Message-
> From: Andriy Redko
> Sent: woensdag 28 juni 2023 23:55
> To: Jean Pierre URKENS
RE: Apache CXF JAX-RS threadsafe clients
Hi Andriy,
Ok, it is clear for the 1st part, which I restructured to:
* private** static* SodexoApi* getThreadsafeProxy*(String
baseAddress)* throws* GeneralSecurityException {
JacksonJsonProvider* provider* =* new
Hi Jean,
So the 1st part is 100% correct way to create a thread safe client proxy, but
with the 2nd one
we have an issue well documented here [1]. Since you only modify headers, the
thread safe proxy
should work, but you probably could avoid using the WebClient part (just use
JAXRSClientFactor
