On Friday, August 05, 2011 11:32:08 AM Penmatsa, Vinay wrote: > Hi Prisca, > Thanks for the link. > This can be fallback solution, but I prefer to do it programmatically. > While debugging the source, it seems a new conduit object is created in > HttpTransportFactory.getConduit(). So, the client.getConduit() in my code > is ignored. Not sure how to fix that
Do you have a different ConduitSelector installed on the client? The default one should just be creating a single Conduit for the client and re-using it. I'm not sure why a second call to HttpTransportFactory.getConduit would be occuring. Dan > > Regards, > Vinay > > -----Original Message----- > From: Prisca POLYTE [mailto:[email protected]] > Sent: Friday, August 05, 2011 11:18 AM > To: [email protected] > Subject: Re: TLSClientParameters > > Hey, > > is it possible for you to use Spring for instance ? > > If it is then you should have a look to > http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html# > ClientHTTPTransport%28includingSSLsupport%29-ConfiguringSSLSupport > > HTH > > Regards > -- > Prisca > > On Fri, Aug 5, 2011 at 5:10 PM, Penmatsa, Vinay <[email protected]>wrote: > > I'm unable to set the 'disableCNCheck' programmatically as below: > > > > HTTPConduit http = (HTTPConduit) client.getConduit(); > > TLSClientParameters param = new TLSClientParameters(); > > param.setDisableCNCheck(true); > > http.setTlsClientParameters(param); > > > > > > What's the correct way to do this? > > > > > > Thanks, > > Vinay -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
