HI Jaroslav
Has this been solved in version 2.0.10 and 2.1.4?
On Tue, Jan 27, 2009 at 1:31 AM, Jaroslav Libak <[email protected]> wrote:
> Hello
>
> This simply cannot work, because there is only one conduit object per web
> client. So if you make calls from multiple threads, one thread could
> override
> configuration for another thread. I have another solution, if I don't
> forget I
> can post a patch here tomorrow.
>
> Jaroslav
>
> Christopher Cheng schrieb:
> > actually the quick fix is to ignore the "useHttps" in here. If the
> value of
> > ENDPOINT_ADDRESS_PROPERTY starts with https, I set the value of useHttps
> to
> > true, false otherwise. It seems to work just fine in my production
> > environment now.
> >
> > if (useHttps
> > || configuredConduit.getTlsClientParameters() != null) {
> >
> > TLSClientParameters params = configuredConduit.getTlsClientParameters();
> >
>
