You are viewing a plain text version of this content. The canonical link for it is here.
Posted to axis-cvs@ws.apache.org by he...@apache.org on 2005/07/02 17:26:13 UTC
svn commit: r208844 - /webservices/axis/trunk/java/xdocs/tcp-transport.html
Author: hemapani
Date: Sat Jul 2 08:26:12 2005
New Revision: 208844
URL: http://svn.apache.org/viewcvs?rev=208844&view=rev
Log:
updates to tcp transport doc
Modified:
webservices/axis/trunk/java/xdocs/tcp-transport.html
Modified: webservices/axis/trunk/java/xdocs/tcp-transport.html
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/tcp-transport.html?rev=208844&r1=208843&r2=208844&view=diff
==============================================================================
--- webservices/axis/trunk/java/xdocs/tcp-transport.html (original)
+++ webservices/axis/trunk/java/xdocs/tcp-transport.html Sat Jul 2 08:26:12 2005
@@ -2,20 +2,26 @@
<body>
<h1>TCP transport</h1>
-<p>TCP transport has come up as a alternative transport with Web Services, the idea is to open the socket to the server and write SOAP Message to the server. The SOAP Message must be self contained in terms of the information needed to process the itself.</p>
-<p>Axis2 TCP transport has two parts, a transport Listener for receiving the Messages and transport Sender to send the SOAP Messages. Axis2 installation has both the components built in to itself by default. In the axis2.xml configuration file the two would look like follows. </p>
-<code>
-<pre>
-<:transportReceiver name="tcp" class="org.apache.axis2.transport.tcp.TCPServer">:
- <:parameter name="port" locked="xsd:false">:6060<:/parameter>:
-<:/transportReceiver>:
-</pre>
-</code>
-<transportSender name="tcp" class="org.apache.axis2.transport.tcp.TCPTransportSender"/>
+<p>Axis2 supports TCP as a default transport, Axis2 has support for both send and receieve SOAP Messages.
+TCP transports do not have any Application level Headers and the SOAP Message that sends should be self contained.
+This make the interaction fast and simple. Yet the main limitation of the TCP transport is absence
+of the request URI, and the Service dispatching should use a alternative method. There is two main
+alternatives methods.</p>
+<ol>
+<li>Use the name space URI of the first child element for the dispatching</li>
+<li>Enable the WS-Addressing</li>
+</ol>
+
+
+<p>When the TCP request is sent it is users responsibility either to use addressing or use alternative method.</p>
+
<h2>How to start the TCPServer</h2>
-<p>The TCP server can be started by running the class org.apache.axis2.transport.tcp.TCPServer with two parameters <a href="faq.html#b5">repository</a> and port number as argument. This class needed all the axis dependency jars in the classapth. </p>
+<p>The TCP server can be started by running the class org.apache.axis2.transport.tcp.TCPServer with two parameters
+<a href="faq.html#b5">repository</a> and port number as argument. This class needed all the axis dependency
+jars in the classapth. New Services can be added in the usual way by droping the archives to repository, read the
+<a href="userguide.html">User Guide</a> for more information</p>
<p>Alternatively the TCP Server can be run with tcp-server.bat/ tcp-server.sh file in the bin directory of the Binary distribution of TCP Server.</p>
<h2>How send SOAP Messages with TCP transport</h2>
@@ -37,5 +43,24 @@
</code>
<p>The method to note is setTransportInfo that accepts sender transport, Listener transport and should the return path of the TCP Channel need to be used. It is good Idea to engage the addressing module to make the SOAP Message self contained. Only other option I can think of is to 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 represntation of Axis2.</p>
+
+<h2>Advanced Topics</h2>
+<p>Axis2 TCP transport has two parts, a transport Listener for receiving the Messages and transport Sender
+to send the SOAP Messages. Axis2 installation has both the components built in to itself by default.
+In the axis2.xml configuration file the two would look like follows. </p>
+<p>If the TCP server is started manually this configuration does not take effect, this affect the transport
+Listeners starts by Axis2. (e.g. Listener started by the Complete Async interaction)</p>
+<code>
+<pre>
+<transportReceiver name="tcp" class="org.apache.axis2.transport.tcp.TCPServer">
+ <parameter name="port" locked="xsd:false">:6060</parameter>
+</transportReceiver>
+</pre>
+</code>
+
+<p>Following add the TCPtransport Sender</p>
+<code>
+<transportSender name="tcp" class="org.apache.axis2.transport.tcp.TCPTransportSender"/>
+</code>
</body>
</html>