You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by aj...@apache.org on 2005/06/07 17:03:10 UTC
svn commit: r188792 - /webservices/axis/trunk/java/xdocs/userguide.html
Author: ajith
Date: Tue Jun 7 08:03:10 2005
New Revision: 188792
URL: http://svn.apache.org/viewcvs?rev=188792&view=rev
Log:
changing the sample bat file reference to the ant target reference
Modified:
webservices/axis/trunk/java/xdocs/userguide.html
Modified: webservices/axis/trunk/java/xdocs/userguide.html
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/userguide.html?rev=188792&r1=188791&r2=188792&view=diff
==============================================================================
--- webservices/axis/trunk/java/xdocs/userguide.html (original)
+++ webservices/axis/trunk/java/xdocs/userguide.html Tue Jun 7 08:03:10 2005
@@ -246,8 +246,8 @@
}
</code></pre></p>
<p>The green lines shows the set of operations that you need to perform in-order to invoke a web service while the rest is used to create the OMElement that needs to be sent and to display the response OMElement. To test this
-client you can use the "TestEchoBlockingClient.bat" that can be found in the "Axis2Home/samples/userguide/src/userguide/clients/bin" directory. The
-.bat or .sh files show the required jars that needs to be there in the classpath for one to write Web Service clients using Axis2. So if you can see the response OMElement printed in your command line (as shown below) then you have successfully tested the client as well. </p>
+client you can use the provided ant build file that can be found in the
+"Axis2Home/samples" directory. Run the "testEchoBlockingClient" target . if you can see the response OMElement printed in your command line then you have successfully tested the client as well. </p>
<p><img src="images/userguide/TestClient.jpg" width="951" height="132"></p>
<h3>PingClient</h3>
<p>In the Web Service "MyService" we had a IN-ONLY operation with the name "ping" (see Web Services Using Axis2). So let's write a client to invoke this operation as well.
@@ -267,7 +267,8 @@
</p>
<p>Since we are accessing a IN-ONLY operation we can directly use the "MessageSender" to invoke this operation. As it can be seen in the above code , it is very straight forward to invoke this type of operation. MessageSender will not block the
invocation, hence it will return the control immediately back to the client. You can
-test this client using the "TestPingClient.bat" that is in "Axis2Home/samples/userguide/src/userguide/clients/bin".</p>
+test this client by running the target "testPingClient" of the ant build
+file at "Axis2Home/samples".</p>
<p>Ok, we have invoked the two operations in our service, Are we done? No!, there are lot more to explore, Let's see some other ways to invoke
the same operations.</p>
<h3>EchoNonBlockingClient</h3>
@@ -283,7 +284,8 @@
<p>The user is expected to implement the "onComplete " and "reportError " methods of their extended call back class. Axis2 engine calls the onComplete method once the Web Service
response is received by the Axis2 Client API (Call). This will eliminate the blocking nature of the Web Service invocations and provides the user 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 "TestEchoNonBlockingClient.bat" or "TestEchoNonBlockingClient.sh" files that can be found in the "Axis2Home/samples/userguide/src/userguide/clients/bin" directory. </p>
+<p>To run the sample client ( EchoNonBlockingClient) you can simply use the "testEchoNonBlockingClient"
+target of the ant file found at the "Axis2Home/samples" directory. </p>
<h3>EchoNonBlockingDualClient </h3>
<p>The solution provided by the Non-Blocking API has one limitation when it
comes to Web Service invocations which takes long time to complete. The limitation
@@ -364,7 +366,8 @@
directory in the servlet container. </p>
<source><pre> <module ref="addressing"/></code></pre>
<p>Note: Please note that<span class="style15"><font color="#000000"> once you change the "server.xml" you need to restart the servlet container.</font></span></p>
-<p>This will enable the addressing in the server side and now you can test the "TestEchoNonBlockingDualClient" using the "TestEchoNonBlockingDualClient.bat" or "TestEchoNonBlockingDualClient.sh" provided under "Axis2Home/samples/userguide/src/userguide/clients/bin" directory.
+<p>This will enable the addressing in the server side and now you can test the "TestEchoNonBlockingDualClient" using the "testEchoNonBlockingDualClient"
+target of the ant file found at "Axis2Home/samples" directory.
If you can see the response OMElement printed in the client side, that means you
have successfully tested the Non Blocking API with two transport channels at the
client side.</p>
@@ -376,8 +379,9 @@
not use a callback object to handle response. This is a very useful mechanism
when the service invocation is IN-OUT in nature and the transports are One-Way
(e.g. SMTP). For the sample client we use two HTTP connections for request and
-response. User can test this client using the "EchoBlockingDualClient.bat" or "EchoBlockingDualClient.sh"
-found in the "Axis2Home/samples/userguide/src/userguide/clients/bin" directory.</p>
+response. User can test this client using the "echoBlockingDualClient"
+target of the ant build file
+found in the "Axis2Home/samples" directory.</p>
<p>See <a href="#configTransport">Configuring Transports</a> for use different transports.</p>
<h2>Modules</h2>
<p>Axis2 provides an extended support for modules (See
@@ -777,10 +781,9 @@
<p>Now the James is up and running with the accounts</p>
- <h2>Enable REST support</h2>
- <h3>Enable the REST support for the Server side</h3>
- <p>Add the following parameter in the server.xml file</p>
- <code><parameter name="eanbleREST" locked="xsd:false">true</parameter></code>
+ <hr>
+
+ <p> </p>
<!--
<h3>Enable the REST support for the Client side</h3>