[
https://issues.apache.org/jira/browse/CXF-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681574#comment-13681574
]
Oleg Kalnichevski commented on CXF-5071:
----------------------------------------
Aymeric,
Blocking and non-blocking i/o models are very different and in many ways are
not quite compatible. SSL support is one of those aspects that differ
substantially. SocketFactory class and SocketFactory#createSocket methods in
particular are inherently blocking and sockets instantiated in such a way
cannot be used for asynchronous i/o. SSLContext class though is generic enough
to be applicable to both blocking and non-blocking i/o models. (I presume CXF
HTTP conduits can also be configured by providing a custom SSLContext).
Oleg
> Async Http transport: Injecting an sslSocketFactory in the
> tlsClientParameters has no effect
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-5071
> URL: https://issues.apache.org/jira/browse/CXF-5071
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.7.5
> Reporter: Aymeric Levaux
>
> When using the async http transport, the sslSocketFactory injected in the
> tlsClientParameters is not taken into account.
> TLSClientParameters.getSSLSocketFactory() is only used in
> HttpsURLConnectionFactory.
> This issue prevents the integration with custom JSSE implementations (e.g.:
> using the Websphere JSSEHelper to get a specific SSLSocketFactory).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
