Thanks so much Dan K. I am done with creating a custom AsyncHTTPConduitFactory. Where/what can I configure to get my factory picked up?
Thanks, <http://www.gaiansolutions.com/> Syed Mudassir Ahmed LMTS-2 o: +91 40 64535352 m: +91 9177674397 w: www.gaiansolutions.com On Tue, Nov 10, 2020 at 8:58 PM Daniel Kulp <[email protected]> wrote: > > > I am presently using CXF 2.7.8. I need to migrate to 3.x version to be > able to work on Java11. However, I see that there is a drastic change from > 2.x to 3.x in CXF. One such commit is > > https://github.com/apache/cxf/commit/a18be4fac03d3886317b0201123e9917d1a33e60 > . > In this commit, I can here > > https://github.com/apache/cxf/commit/a18be4fac03d3886317b0201123e9917d1a33e60#diff-f5349d24a3d1a3bced2aa168ce24d586461fe743d2e0b72f0fafcfedb9a99234R114 > , > that there is no0 longer a http processor present in the http async conduit > factory. Whats the alternative for it in cxf 3.x? I am not able to find > any reference so far. Please advise and guide me here to complete the java > 11 migration. > > > With the recent HTTPAsyncClient stuff using fluent style builders, most of > the objects are more or less immutable after the build method is called. > Thus, you would likely need to subclass the AsyncHTTPConduitFactory and > override the > adaptClientBuilder(HttpAsyncClientBuilder httpAsyncClientBuilder) method > to modify the builder in ways that you need prior to CXF calling the > build() and then start methods. Not really 100% sure on that, but that’s > likely how it would need to be done. > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend - http://talend.com <http://coders.talend.com> > >
