axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r822108 - in /webservices/axis2/branches/java/1_5: modules/documentation/xdocs/@axis2_version_dir@/http-transport.xml release-notes.html
Date Tue, 06 Oct 2009 02:43:53 GMT
Author: gdaniels
Date: Tue Oct  6 02:43:52 2009
New Revision: 822108

Update docs.


Modified: webservices/axis2/branches/java/1_5/modules/documentation/xdocs/@axis2_version_dir@/http-transport.xml
--- webservices/axis2/branches/java/1_5/modules/documentation/xdocs/@axis2_version_dir@/http-transport.xml
+++ webservices/axis2/branches/java/1_5/modules/documentation/xdocs/@axis2_version_dir@/http-transport.xml
Tue Oct  6 02:43:52 2009
@@ -19,7 +19,7 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+<html xmlns="" version="-//W3C//DTDXHTML1.1//EN">
   <meta http-equiv="content-type" content=""/>
   <title>HTTP transports</title>
@@ -54,12 +54,19 @@
 <p>CommonsHTTPTransportSender is the transport sender that is used by default in both
-the Server and Client APIs. As its name implies, it is based on commons-httpclient-3.0.1.

+the Server and Client APIs. As its name implies, it is based on <a
+        xmlns="" xml:space="preserve" href="">commons-httpclient-3.1</a>.
 For maximum flexibility, this sender supports both the HTTP GET and POST interfaces.
 (REST in Axis2 also supports both interfaces.)</p>
+<h3>Reuse and Releasing Connections</h3>
+<p>Axis2 uses a single HTTPClient instance per ConfigurationContext (which usually
means per instance
+of ServiceClient).  This pattern allows for HTTP 1.1 to automatically reuse TCP connections
- in earlier versions of Axis2 the REUSE_HTTP_CLIENT configuration property was necessary
to enable this functionality, but as of 1.5 this is no longer necessary.</p>
 <p>Commons HttpClient also provides HTTP 1.1, Chunking and KeepAlive support for Axis2.</p>
 <p>The &lt;transportSender/&gt; element defines transport senders in
 the axis2.xml configuration file as follows:</p>

Modified: webservices/axis2/branches/java/1_5/release-notes.html
--- webservices/axis2/branches/java/1_5/release-notes.html (original)
+++ webservices/axis2/branches/java/1_5/release-notes.html Tue Oct  6 02:43:52 2009
@@ -35,9 +35,11 @@
  <li>Fix for the dreaded "CLOSE_WAIT" problem (JIRA issues 935, 2883, etc).  We now
share an instance of HTTPClient across each ConfigurationContext (i.e. each Axis2 server or
ServiceClient) - connection reuse is now automatic.  This means <b>the REUSE_HTTP_CLIENT
flag is no longer necessary or useful, nor is creating your own MultithreadedHttpConnectionManager</b>.</li>
+ <li>Another important part of this fix involves automatically releasing the last OperationContext's
resources each time ServiceClient.sendReceive() is called for blocking operations.  This behavior
is controlled by setting the ServiceClient.AUTO_RELEASE_CONNECTION property in the Options
class - the default is true, but if you want to turn it off you can call <code>options.setProperty(ServiceClient.AUTO_RELEASE_CONNECTION,
false)</code> (note that if you do this you'll need to ensure that the transport connection
is cleaned up some other way, such as by manually calling cleanupTransport() on your client
or stub).</li>
  <li>Transport deployer is now actually functional, and getListenerManager() in ConfigurationContext
now creates a new LM if there isn't one already.</li>
  <li>Fix for AXIS2-4034, module versions now support real versions like "1.5.1"</li>
  <li>NPE problem (see AXIS2-4114) fixed in MessageContext while retrieving policy.</li>
+ <li>Fix a dependency problem with the JavaDocs build</li>
 <h4>Known Issues and Limitations in the @axisVersion@ Release:</h4>

View raw message