[
https://issues.apache.org/jira/browse/CXF-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465893#comment-13465893
]
Daniel Kulp commented on CXF-4525:
----------------------------------
It's not creating a DefaultHttpAsyncClient per HTTPConduit. It's not a
singleton per Bus/Factory. It calls into the factory in case you DO want/need
to customize something on a more global level.
I did put a getter on the Conduit: getHttpAsyncClient()
Thus, you can do:
{code}
Client client = ClientProxy.getClient( proxy );
HTTPConduit http = (HTTPConduit)client.getConduit();
if ( http instanceof AsyncHTTPConduit ) {
AsyncHTTPConduit asyncHTTPConduit = (AsyncHTTPConduit)http;
DefaultHttpAsyncClient defaultHttpAsyncClient =
asyncHTTPConduit.getHttpAsyncClient();
defaultHttpAsyncClient.getCredentialsProvider()
.setCredentials( AuthScope.ANY, new NTCredentials( _userName,
_password, "", _domain ) );
}
{code}
> expose http client
> ------------------
>
> Key: CXF-4525
> URL: https://issues.apache.org/jira/browse/CXF-4525
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.7.0
> Reporter: Shaun Elliott
> Assignee: Daniel Kulp
> Fix For: 2.7.0
>
>
> The class: CXFAsyncRequester hides the DefaultHttpAsyncClient, thus
> preventing interaction from outside classes. One use case would be to
> leverage the embedded DefaultHttpAsyncClient to do NTLM authentication, which
> is currently not possible with CXF.
> AsyncHTTPConduit will also need a getter on the factory field.
--
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
