Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Tue, 2 Oct 2012 05:55:12 +1100 (NCT)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <2095821375.149804.1349117713018.JavaMail.jiratomcat@arcas>
In-Reply-To: <854462583.136122.1348782668082.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CXF-4525) expose http client
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CXF-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467094#comment-13467094 ] 

Daniel Kulp commented on CXF-4525:
----------------------------------


Shaun, 

This should now be implemented on trunk.  See the systests/transports/src/test/java/org/apache/cxf/systest/http_jetty/JettyDigestAuthTest.java test case as it now runs the test twice:  once using CXF's auth providers and once turning on the buffering and allowing the Async client to handle it.  Can you give that a try and see if that works for you.
                
> 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