cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r833772 - in /websites/production/cxf/content: cache/docs.pageCache docs/27-migration-guide.html docs/asynchronous-client-http-transport.html
Date Tue, 02 Oct 2012 16:47:27 GMT
Author: buildbot
Date: Tue Oct  2 16:47:27 2012
New Revision: 833772

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/27-migration-guide.html
    websites/production/cxf/content/docs/asynchronous-client-http-transport.html

Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/docs/27-migration-guide.html
==============================================================================
--- websites/production/cxf/content/docs/27-migration-guide.html (original)
+++ websites/production/cxf/content/docs/27-migration-guide.html Tue Oct  2 16:47:27 2012
@@ -121,7 +121,12 @@ Apache CXF -- 2.7 Migration Guide
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><h3><a shape="rect" name="2.7MigrationGuide-NewFeatures"></a>New
Features</h3>
+<div id="ConfluenceContent">
+<h3><a shape="rect" name="2.7MigrationGuide-MajorNotes"></a>Major Notes</h3>
+<ul><li>CXF 2.7.x no longer supports Java 5.   In order to upgrade to 2.7.0,
you must be using Java 6 (or newer).  Many of the dependencies that CXF uses have moved to
Java 6 and in order to get fixes and updates, we have moved to Java 6 as well.</li></ul>
+
+
+<h3><a shape="rect" name="2.7MigrationGuide-NewFeatures"></a>New Features</h3>
 
 <ul><li>New <a shape="rect" href="udp-transport.html" title="UDP Transport">UDP
Transport</a>.</li><li>New optional <a shape="rect" href="asynchronous-client-http-transport.html"
title="Asynchronous Client HTTP Transport">HTTP transport</a> based on <a shape="rect"
class="external-link" href="http://hc.apache.org/httpcomponents-asyncclient-dev/index.html">Apache
HTTP Components HttpAsyncClient</a>.</li><li>Support for the <a shape="rect"
href="soap-over-udp.html" title="SOAP over UDP">SOAP over UDP</a>.</li><li>Ability
to only apply schema validation to incoming or outgoing messages by setting the "schema-validation-enabled"
property to "IN", "OUT", "BOTH", or "NONE".   @SchemaValidationEnabled annotation updated
to have a type=IN|OUT|BOTH|NONE parameter.</li><li>Support for <a shape="rect"
href="ws-discovery.html" title="WS-Discovery">WS-Discovery</a>.
 	<ul><li>Services can send Hello/Bye when started/stopped as well as respond
to Probe requests</li><li>API for sending probes and resolving to EndpointReferences</li></ul>

Modified: websites/production/cxf/content/docs/asynchronous-client-http-transport.html
==============================================================================
--- websites/production/cxf/content/docs/asynchronous-client-http-transport.html (original)
+++ websites/production/cxf/content/docs/asynchronous-client-http-transport.html Tue Oct 
2 16:47:27 2012
@@ -129,7 +129,31 @@ Apache CXF -- Asynchronous Client HTTP T
 
 <p>CXF also has an HTTP client transport that is based on the <a shape="rect" class="external-link"
href="http://hc.apache.org/httpcomponents-asyncclient-dev/index.html">Apache HTTP Components
HttpAsyncClient</a> library.   The HttpAsyncClient library uses a non-blocking IO model.
 This allows many more requests to be outstanding without consume extra background threads.
  It also allows greater control over things like Keep-Alive handling which is very difficult
or impossible with the HttpURLConnection based transport.   However, the non-blocking model
does not perform quite as well as the blocking model for pure synchronous request/response
transactions.</p>
 
-<p>By default, if the cxf-rt-transports-http-hc module is found on the classpath, CXF
will use the HttpAsyncClient based implementation for any Async calls, but will continue to
use the HttpURLConnection based transport for synchronous calls.   This allows a good balance
of performance for the common synchronous cases with scalability for the asynchronous cases.
 However, using a contextual property of "use.async.http.conduit" and set to true/false, you
can control whether the async or blocking version is used.   </p>
+<p>By default, if the cxf-rt-transports-http-hc module is found on the classpath, CXF
will use the HttpAsyncClient based implementation for any Async calls, but will continue to
use the HttpURLConnection based transport for synchronous calls.   This allows a good balance
of performance for the common synchronous cases with scalability for the asynchronous cases.
 However, using a contextual property of "use.async.http.conduit" and set to true/false, you
can control whether the async or blocking version is used.</p>
+
+<h3><a shape="rect" name="AsynchronousClientHTTPTransport-SettingCredentials"></a>Setting
Credentials</h3>
+
+<p>The "normal" CXF/JAX-WS method of setting user credentials via the BindingProvider.USERNAME_PROPERTY/PASSWORD_PROPERTY
will work with the Async transport as well.   However, the HttpAsyncClient library does have
some additional capabilities around NTLM that can be leveraged.  In order to use that, you
need to:</p>
+
+<ul><li>Turn on the AutoRedirect and turn off the Chunking for the Conduit. 
 This will allow CXF to cache the response in a manner that will allow the transport to keep
resending the request during the authentication negotiation.</li></ul>
+
+
+<ul><li>Force the use of the Async transport even for synchronous calls 
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-java">
+bp.getRequestContext().put(<span class="code-quote">"use.async.http.conduit"</span>,
<span class="code-object">Boolean</span>.TRUE);
+</pre>
+</div></div></li></ul>
+
+
+<ul><li>Set the property "org.apache.http.auth.Credentials" to an instance of
the Credentials.  For example: 
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-java">
+Credentials creds = <span class="code-keyword">new</span> NTCredentials(<span
class="code-quote">"username"</span>, <span class="code-quote">"pswd"</span>,
<span class="code-keyword">null</span>, <span class="code-quote">"domain"</span>);
+bp.getRequestContext().put(Credentials.class.getName(), creds);
+</pre>
+</div></div></li></ul>
+
 
 
 <h3><a shape="rect" name="AsynchronousClientHTTPTransport-Configuration"></a>Configuration
</h3>
@@ -159,7 +183,6 @@ Apache CXF -- Asynchronous Client HTTP T
 <div class="table-wrap">
 <table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1"
class="confluenceTd">org.apache.cxf.transport.http.async.usePolicy</td><td colspan="1"
rowspan="1" class="confluenceTd"> ALWAYS, ASYNC_ONLY, NEVER.   </td></tr></tbody></table>
 </div>
-
 </div>
            </div>
            <!-- Content -->



Mime
View raw message