axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cha...@apache.org
Subject svn commit: r472034 - /webservices/axis2/branches/java/1_1/xdocs/1_1/tcp-transport.html
Date Tue, 07 Nov 2006 08:47:09 GMT
Author: chatra
Date: Tue Nov  7 00:47:08 2006
New Revision: 472034

URL: http://svn.apache.org/viewvc?view=rev&rev=472034
Log:
reviewed and committing minor changes in jira issue AXIS2-1627

Modified:
    webservices/axis2/branches/java/1_1/xdocs/1_1/tcp-transport.html

Modified: webservices/axis2/branches/java/1_1/xdocs/1_1/tcp-transport.html
URL: http://svn.apache.org/viewvc/webservices/axis2/branches/java/1_1/xdocs/1_1/tcp-transport.html?view=diff&rev=472034&r1=472033&r2=472034
==============================================================================
--- webservices/axis2/branches/java/1_1/xdocs/1_1/tcp-transport.html (original)
+++ webservices/axis2/branches/java/1_1/xdocs/1_1/tcp-transport.html Tue Nov  7 00:47:08 2006
@@ -1,4 +1,5 @@
 <html>
+
 <head>
   <meta content="">
   <meta content="">
@@ -9,6 +10,7 @@
 
 <body lang="en">
 <h1>TCP Transport</h1>
+
 This document will explain how to send and receive SOAP Messages via TCP in
 Axis2. 
 
@@ -25,29 +27,29 @@
   <li><a href="#samples">Samples</a></li>
   <li><a href="#components">Transport Components</a></li>
 </ul>
-<a name="intro"></a>
 
+<a name="intro"></a>
 <h2>Introduction</h2>
 
-<p>Axis2 supports TCP as a transport. It has support for both send and
-receive SOAP Messages via TCP. TCP transport does not have any application
+<p>Axis2 supports TCP as a transport. It has support for both send and receive SOAP

+Messages via TCP. TCP transport does not have any application
 level headers and the SOAP Message that is sent should be self contained.
-This makes the interaction fast and simple. However since there are no
+This makes the interaction fast and simple. However, since there are no
 application headers, it does not have the privilege of having request URI,
 and Service dispatching should be done by an alternative method. Thus,
-RequestURIBasedDispatcher can not be used. Following are the two main
-alternatives available for dispatching in the Axis2 environment.</p>
+RequestURIBasedDispatcher can not be used. The following are the two main
+alternatives available for dispatching in the Axis2 environment:</p>
 <ol>
   <li>Use the name space URI of the first child element of SOAPBody.
-    (SOAPMessageBodyBasedDispatcher)</li>
+    (SOAPMessageBodyBasedDispatcher).</li>
   <li>Enable WS-Addressing. In the case of version 1.1 release Addressing is
-    default (SOAPActionBasedDispatcher)</li>
+    default (SOAPActionBasedDispatcher).</li>
 </ol>
 
 <p>When the TCP request is sent it is the user's responsibility to use either
 Addressing or SOAP body base mechanism.</p>
-<a name="start"></a>
 
+<a name="start"></a>
 <h2>How to Start the TCPServer</h2>
 
 <p>The TCP server can be started by running the class
@@ -60,11 +62,10 @@
 <p>Alternatively the TCP Server can run with tcp-server.bat/ tcp-server.sh
 file in the bin directory of the Binary distribution of TCP Server.</p>
 <a name="send"></a>
-
 <h2>How to Send SOAP Messages Using TCP Transport</h2>
 
-<p>TCP transport can be enabled easily from the call API. Following code
-segment demonstrate how it can be done.</p>
+<p>TCP transport can be enabled easily from the call API. The following code
+segment demonstrates how it can be done.</p>
 <source><pre>OMElement payload = ...
 
 ServiceClient serviceClient = new ServiceClient();
@@ -82,9 +83,9 @@
 use the URI of the first child of the SOAP Body to dispatch the service. The
 Parameter is of the type <a href="../faq.html#a2">OMElement</a>, the XML
 representation of Axis2.</p>
-<a name="sample"></a>
 
-<h2>Sample</h2>
+<a name="samples"></a>
+<h2>Samples</h2>
 
 <p>Sample for a TCP Client can be found from the
 samples/userguide/src/userguide/clients/TCPClient.java in the binary
@@ -94,8 +95,8 @@
 href="userguide.html">Axis2 User's Guide</a> samples. Since sample is already
 deployed in the repository while trying the userguide it will be
 automatically available.</p>
-<a name="components"></a>
 
+<a name="components"></a>
 <h2>Transport Components</h2>
 
 <p>Axis2 TCP transport has two components, a transport Listener for receiving
@@ -108,12 +109,15 @@
 effect. In return this effects the transport Listener's start by Axis2. (e.g.
 Listener started by the Complete Async interaction)</p>
 
-<p>Following xml lines initializes the TCPTransport Receiver:</p>
+<p>The following xml lines initializes the TCPTransport Receiver:</p>
 <source><pre>&lt;transportReceiver name="tcp" class="org.apache.axis2.transport.tcp.TCPServer"&gt;
     &lt;parameter name="port" locked="false"&gt;6060&lt;/parameter&gt;
 &lt;/transportReceiver&gt;</pre>
 </source>
-<p>Following xml lines adds the TCPTransport Sender:</p>
+<p>The following xml lines adds the TCPTransport Sender:</p>
 <source><pre>&lt;transportSender name="tcp" class="org.apache.axis2.transport.tcp.TCPTransportSender"/&gt;</pre>
-</source></body>
+</source>
+
+</body>
+
 </html>



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-cvs-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-cvs-help@ws.apache.org


Mime
View raw message