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 ch...@apache.org on 2006/10/12 09:20:47 UTC
svn commit: r463144 - /webservices/axis2/branches/java/1_1/xdocs/1_1/dii.html
Author: chatra
Date: Thu Oct 12 00:20:41 2006
New Revision: 463144
URL: http://svn.apache.org/viewvc?view=rev&rev=463144
Log:
reviewd and committed patch in Jira issue AXIS2-1351. Thanks isuru
Modified:
webservices/axis2/branches/java/1_1/xdocs/1_1/dii.html
Modified: webservices/axis2/branches/java/1_1/xdocs/1_1/dii.html
URL: http://svn.apache.org/viewvc/webservices/axis2/branches/java/1_1/xdocs/1_1/dii.html?view=diff&rev=463144&r1=463143&r2=463144
==============================================================================
--- webservices/axis2/branches/java/1_1/xdocs/1_1/dii.html (original)
+++ webservices/axis2/branches/java/1_1/xdocs/1_1/dii.html Thu Oct 12 00:20:41 2006
@@ -1,18 +1,18 @@
<h1><a name="Web_Service_Clients_Using_Axis2">Writing Web Service Clients Using Axis2's Primary APIs</a></h1>
-<p>This section presents complex yet powerful <strong>XML based client API</strong> which is intended for advanced users.However if you are a new user we recommend using code generation given in the <a href="userguide.html">user guide</a>.
+<p>This section presents complex yet powerful <strong>XML based client API</strong> which is intended for advanced users. However if you are a new user we recommend using code generation given in the <a href="userguide.html">user guide</a>.
</p>
<p>Web services can be used to provide a wide-range of functionality to user
-from simple, less time consuming operations such as "getStockQuote" to time
+from simple, less time consuming operations such as "getStockQuote" to time
consuming business services. When we utilize (invoke using client
applications) these Web services we cannot use simple generic invocation
paradigms that suite all the timing complexities involved in the service
operations. For example, if we use a single transport channel (such as HTTP)
to invoke a Web service with an IN-OUT operation that takes a long time to
complete, then most often we may end up with "connection time outs". On the
-other hand, if there are simultaneous service invocations that we need to
+other hand, if there are simultaneous service invocations that we need to
perform from a single client application, then the use of a "blocking" client
API will degrade the performance of the client application. Similarly there
are various other consequences such as One-Way transports that come in to
@@ -37,7 +37,7 @@
</li>
</ul>
-<p>Both these mechanisms work in the API level. Let's name the asynchronous
+<p>Both these mechanisms work in the API level. Let's name the asynchronous
behavior that we can get using the Non-Blocking API as <b>API Level
Asynchrony.</b></p>
@@ -62,7 +62,7 @@
<td width="33%" height="19"><p><strong>API
(Blocking/Non-Blocking)</strong></p>
</td>
- <td width="33%"><p><strong>Â Dual Transports (Yes/No)</strong></p>
+ <td width="33%"><p><strong>Dual Transports (Yes/No)</strong></p>
</td>
<td width="33%"><p><strong>Description</strong></p>
</td>
@@ -105,10 +105,10 @@
</tbody>
</table>
-<p>FoAxis2 provides the user with all these possibilities to invoke Web
+<p>Axis2 provides the user with all these possibilities to invoke Web
services.</p>
-<p>Following section present cleints that use different posibilites presented above to invoke a Web Service using <code>ServiceClient</code>s. All samples mentioned in this guide are located at the
+<p>Following section present clients that use different possibilities presented above to invoke a Web Service using <code>ServiceClient</code>s. All samples mentioned in this guide are located at the
<b><font color="#000000">"samples\userguide\src"</font></b> directory of the
binary distribution.</p>
@@ -118,7 +118,7 @@
<li>Request-Response, Blocking Client</li>
<li>One Way Client</li>
<li>Request-Response, Non-Blocking that uses one transport connection</li>
- <li>Request-Response, Non-Blocking that uses one transport connections</li>
+ <li>Request-Response, Non-Blocking that uses two transport connections</li>
</ol>
<h4><a name="EchoBlockingClient">Request-Response, Blocking Client</a></h4>
@@ -155,7 +155,7 @@
<p>To test this client, use the provided ant build file that can be found in
the "<strong>Axis2_HOME/samples/userguide</strong>" directory. Run the
"testEchoBlockingClient" target. If you can see the response OMElement
-printed in your command line, then you have successfully tested the client.
+printed in your command line, then you have successfully tested the client.
</p>
<h4><a name="PingClient">One Way Client</a></h4>
@@ -194,7 +194,7 @@
<h4><a name="EchoNonBlockingClient">Request-Response, Non-Blocking that uses one transport connection</a></h4>
-<p>In the EchoBlockingClient once the "serviceClient.sendReceive(payload);"
+<p>In the "EchoBlockingClient" once the "serviceClient.sendReceive(payload);"
is called, the client is blocked till the operation is complete. This
behavior is not desirable when there are many Web service invocations to be
done in a single client application or within a GUI. A solution would be to
@@ -203,7 +203,7 @@
<p>A sample client for this can be found under
"<strong>Axis2_HOME/samples/userguide/src/userguide/clients</strong>" with
-the name EchoNonBlockingClient. If we consider the changes that users may
+the name "EchoNonBlockingClient". If we consider the changes that users may
have to do with respect to the "EchoBlockingClient" that we have already
seen, it will be as follows:</p>
<pre style="margin-bottom: 0.2in">serviceClient.sendReceiveNonblocking(payload, callback);</pre>
@@ -215,20 +215,20 @@
public boolean isComplete() {}</pre>
<p>The user is expected to implement the "onComplete " and "onError " methods
-of their extended call back class. The Axis2 engine calls the onComplete
+of their extended call back class. The Axis2 engine calls the "onComplete"
method once the Web service response is received by the Axis2 Client API
(ServiceClient). This will eliminate the blocking nature of the Web service
invocation and provide users with the flexibility to use Non Blocking API for
Web service Clients.</p>
-<p>To run the sample client ( EchoNonBlockingClient) you can simply use the
+<p>To run the sample client ("EchoNonBlockingClient") you can simply use the
"testEchoNonBlockingClient" target of the ant file found at the
"<strong>Axis2_HOME/samples</strong>" directory.</p>
-<h4><a name="EchoNonBlockingDualClient">Request-Response, Non-Blocking that uses one transport connections</a></h4>
+<h4><a name="EchoNonBlockingDualClient">Request-Response, Non-Blocking that uses two transport connections</a></h4>
<p>The solution provided by the Non-Blocking API has one limitation when it
-comes to Web service invocations which take a long time to complete. The
+comes to Web service invocations which take a long time to complete. The
limitation is due to the use of single transport connections to invoke the
Web service and to retrieve the response. In other words, client API provides
a non blocking invocation mechanism for users, but the request and the
@@ -242,7 +242,7 @@
to be solved is the correlation (correlating the request and the response).
<a href="http://www.w3.org/2002/ws/addr/" target="_blank">WS-Addressing</a>
provides a neat solution to this using <wsa:MessageID> and
-<wsa:RelatesTo> headers. Axis2 provides support for addressing based
+<wsa:RelatesTo> headers. Axis2 provides support for addressing based
correlation mechanism and a complying Client API to invoke Web services with
two transport connections. (Core of Axis2 does not depend on WS-Addressing,
but contains a set of parameters like in addressing that can be populated in
@@ -303,3 +303,7 @@
engine to use separate transport connections for request and response.
Finally "<b>service.finalizeInvoke()</b>" informs the Axis2 engine to stop
the client side listener started to retrieve the response.</font></font></p>
+
+<p>To run the sample client ("EchoNonBlockingDualClient") you can simply use the
+"testEchoNonBlockingDualClient" target of the ant file found at the
+"<strong>Axis2_HOME/samples</strong>" directory.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-cvs-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-cvs-help@ws.apache.org