With programmatic configuration:
Allow for the creation and injection of a default set of TLSClientParameters to be set, which will be used by all HTTPConduits. This could be accomplished, for example, through a call to
When trying to connect to a SOAP service over HTTPS, the HTTPConduit created only uses the default TLSClientParameters. This causes a connection failure (evidenced by a WSDL parsing exception), if there are any specific requirements needed to make the SSL connection (for example, specific cipher suites).
This can be worked around by implementing both ConduitInitiatorManager and ConduitInitiator wrappers, which can set the TLSClientParamters as needed before the HTTPConduit is returned for usage. However, this is a bit unwieldy, as well as creates set of classes whose reasons for existence may be unclear to developers not familiar with their creation.