On Mon, 2025-06-02 at 15:12 +0000, Stankov. Yavor wrote:
> Hi Oleg,
>
> Thank you very much for the quick response! Having in mind the
> context, I'm not really sure how I can provide the a way for you to
> test this.
>
The problem is I cannot fix something I am not able to reproduce
locally.
> However if this helps a bit, before the update, my request executor
> was being invoked by the
> PoolingHttpClientConnectionManager$InternalConnectionEndpoint and to
> be more precise from the method:
>
> /**
> * @deprecated Use {@link #execute(String,
> ClassicHttpRequest, RequestExecutor, HttpContext)}
> */
> @Deprecated
> @Override
> public ClassicHttpResponse execute(
> final String exchangeId,
> final ClassicHttpRequest request,
> final HttpRequestExecutor requestExecutor,
> final HttpContext context)
>
> Which it looks like is already deprecated and it is recommended to
> use the new method with the RequestExecutor instead. So, I'm
> wondering if it's possible that the old one is never called anymore,
> which will mean that there is no way for the execution to get inside
> of my HttpRequestExecutor anymore and I need to create a
> RequestExecutor instead. However the setter of the HttpClientBuilder
> accepts only HttpRequestExecutor, so what will be the appropriate way
> to introduce such custom RequestExecutor?
>
If everything got wired correctly the default implementation of
RequestExecutor will merely delegate the request execution to your
custom HttpRequestExecutor
https://github.com/apache/httpcomponents-client/blob/master/httpclient5/src/main/java/org/apache/hc/client5/http/impl/classic/InternalExecRuntime.java#L233
Hope this helps
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org
For additional commands, e-mail: httpclient-users-h...@hc.apache.org
