Aiglin, Actually bus.setExtension() is one way to get this done. Other way is to create your conduit object. I am good for now. Thanks, <http://www.gaiansolutions.com/> Syed Mudassir Ahmed LMTS-2 o: +91 40 64535352 m: +91 9177674397 w: www.gaiansolutions.com
On Tue, Nov 17, 2020 at 3:17 PM Syed Mudassir Ahmed < [email protected]> wrote: > Aiglin, > As per this commit, > https://github.com/apache/cxf/commit/a18be4fac03d3886317b0201123e9917d1a33e60#diff-f5349d24a3d1a3bced2aa168ce24d586461fe743d2e0b72f0fafcfedb9a99234L132, > the access to httpProcessor is lost in 3.x version of CXF. Is there a way > the developers can regain us the access to that object in the newer > versions of CXF? > Or are you aware of how to get control of httpProcessor in 3.x version > of CXF presently? > Thanks, > <http://www.gaiansolutions.com/> > Syed Mudassir Ahmed > LMTS-2 > o: +91 40 64535352 > m: +91 9177674397 > w: www.gaiansolutions.com > > > On Tue, Nov 17, 2020 at 2:52 PM Baptiste Aiglin <[email protected]> > wrote: > >> You just need to put it in META-INF/cxf/ but I found it is not possible to >> remove the original extension file, but also found this >> https://issues.apache.org/jira/browse/CXF-3601. Maybe you can use it. >> >> Le mar. 17 nov. 2020 à 09:54, Syed Mudassir Ahmed >> <[email protected]> a écrit : >> >> > Thanks Aiglin, >> > I tried bus.setExtension() but it never worked. I can try the other >> > option, but how can I tell the CXF to pick my own .txt file?. >> > >> > Thanks, >> > <http://www.gaiansolutions.com/> >> > Syed Mudassir Ahmed >> > LMTS-2 >> > o: +91 40 64535352 >> > m: +91 9177674397 >> > w: www.gaiansolutions.com >> > >> > >> > On Tue, Nov 17, 2020 at 2:03 PM Baptiste Aiglin < >> [email protected] >> > > >> > wrote: >> > >> > > Hi Syed, >> > > as far as I know this factory is chosen after you add the dependency >> so >> > the >> > > bus-extensions.txt file is also added telling CXF how to initialize >> the >> > > implementation of HTTPConduitFactory. >> > > >> > > >> > > >> > >> org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitFactory:org.apache.cxf.transport.http.HTTPConduitFactory:true:true >> > > >> > > >> > >> org.apache.cxf.transport.http.asyncclient.AsyncHttpTransportFactory:org.apache.cxf.transport.ConduitInitiator:true:true >> > > >> > > So for sure by customizing this file somehow, you could tell CXF to >> pick >> > up >> > > your implementation instead. From a code perspective, I could not >> find a >> > > way to do so through the factories. The only way grammatically would >> be >> > to >> > > set the extension on your bus (bus.setExtension(..)), but I fear it >> may >> > > happen too late in the initialization of the different factories. >> > > >> > > Le lun. 16 nov. 2020 à 06:36, Syed Mudassir Ahmed >> > > <[email protected]> a écrit : >> > > >> > > > Hi Guys, >> > > > I am using CXF 3.4.0. >> > > > I wanted to customize the AsyncHTTPConduitFactory for my needs. >> > > > I subclasses the same, but I don't know where and how to configure >> > the >> > > > CXF to pick-up my custom factory instead of the default one. >> > > > Can anyone provide any example or reference regarding how to tell >> the >> > > CXF >> > > > to use my custom factory? >> > > > Thanks, >> > > > <http://www.gaiansolutions.com/> >> > > > Syed Mudassir Ahmed >> > > > LMTS-2 >> > > > o: +91 40 64535352 >> > > > m: +91 9177674397 >> > > > w: www.gaiansolutions.com >> > > > >> > > >> > >> >
