On Wed, Mar 29, 2017 at 1:49 AM, Sergey Beryozkin <[email protected]> wrote:
> I do not understand this question. In general one will use CXF JAX-WS or > -RS client API but can request that HttpClient is used internally to do the > sync calls. > Sergey, for some reason, the OP prefers the underlying 'plain' Apache HTTP client to the Asynchronous client. Since the Asynchronous client library is implemented on top of the plain one, I can't guess why the OP wishes for it. So the OP wishes that there were three transports: JDK, classic Apache HTTP client, and async HTTP client. > > Sergey > > On 29/03/17 02:07, cctv092 wrote: > >> Thanks for your replay! >> I see http://cxf.apache.org/docs/asynchronous-client-http-transport.html. >> It is said when "use.async.http.conduit" is true, the HttpAsyncClient will >> be used even for synchronous calls and "use.async.http.conduit" is false, >> asynchronous calls will rely on the traditional method of using >> HTTPURLConnection along with a work queue to mimic the asynchronocity. It >> is >> based on HttpAsyncClient or HTTPURLConnection. I wonder whether there is a >> method to use org.apache.http.client.HttpClient to call synchronously, >> thank >> you! >> >> >> >> -- >> View this message in context: http://cxf.547215.n5.nabble.co >> m/How-to-transprot-by-HttpClient-tp5778600p5778792.html >> Sent from the cxf-user mailing list archive at Nabble.com. >> >> >
