ws-axis-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chath...@apache.org
Subject svn commit: r154943 - webservices/axis/trunk/java/xdocs/userguide.html
Date Wed, 23 Feb 2005 03:50:45 GMT
Author: chathura
Date: Tue Feb 22 19:50:43 2005
New Revision: 154943

URL: http://svn.apache.org/viewcvs?view=rev&rev=154943
Log:
Revieved samples

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?view=diff&r1=154942&r2=154943
==============================================================================
--- webservices/axis/trunk/java/xdocs/userguide.html (original)
+++ webservices/axis/trunk/java/xdocs/userguide.html Tue Feb 22 19:50:43 2005
@@ -247,12 +247,16 @@
   <li>Deploying </li>
   <li>Running the client  </li>
 </ul>
+<<<<<<< .mine
+<p>It is assumed that the sample is already compiled. Please refer "Building Sample1"
above.</p>
+=======
 <h3><strong>Building the sample </strong></h3>
 <p>Building the sample will take only one step provided that pre-conditions are met.
In the build file there is a target called compile that will compile the sample and create
the sample1.jar in the build/services directory. So the user should open a command prompt
and cd to the &quot;modules/samples&quot; directory and type </p>
 <p>&gt;ant compile </p>
 <p>and it will show the following output. </p>
 <p align="center"><img width="648" height="362" src="images/clip_image016.jpg"></p>
 <p>Now the user can actually go check for the sample1-all.jar in the lib directory
and the packaged web service in the <strong>sample1.jar </strong>in the modules\samples\build\services
directory. </p>
+>>>>>>> .r154941
 <h3><strong>Deploying the sample </strong></h3>
 <p>Before deploying the sample, it is necessary to package the web service. The actual
web service implementation is the EchoXML.java and it is necessary to write a service.xml
so that the necessary statistics about the service will be available to the Axis 2 engine
at the runtime. </p>
 <p class="style1 style2 style3">&lt;service provider=&quot;org.apache.axis.providers.RawXMLProvider&quot;
style=&quot;rpc&quot;&gt; <br> 
@@ -269,7 +273,7 @@
 <p>&gt;ant compile </p>
 <p>The web service will get packaged into the build\services directory. Now the user
can deploy the service by one of the following methods. Since Axis2 supports the hot deployment
of services can be deployed while the container is up and running. For option 2 below actually
requires the container to be online. </p>
 <p>&gt;ant deploy </p>
-<p align="center"><img width="648" height="467" src="images/clip_image018.jpg"></p>
+<p align="center"><img src="images/clip_image018.jpg"></p>
 <p>&nbsp; </p>
 <p>&#149;&nbsp; Uploading the jar using the web interface provided in the <strong>http://
&lt;host :port&gt;/ axis2 </strong>location. Please refer the Installation guide
for further information. </p>
 <p>&#149;&nbsp; Manually copying the sample1.jar in build\services to the AXIS_HOME\WEB-INF\services
directory. </p>
@@ -295,8 +299,7 @@
 <br><br>public void revoke(MessageContext msgContext){ 
 <br>&nbsp;&nbsp;log.info(&quot;Incoming message Revoked at the server &quot;+msgContext.getTo().getAddress()
); 
 <br>} </p>
-<h3><strong>Building the sample </strong></h3>
-<p>Building the sample once will build all required classes and jars for all three
cases. The ant task would be ant Compile. Please refer the building of the <strong>“Echo
Synchronous call” </strong> above. </p>
+<p>It is assumed that the sample is compiled. Please refer "Building Sample" above.</p>
 <h3><strong>Deploying the sample </strong></h3>
 <p>The implementation of the web service will be EchoXML, operation will be echo and
the provider will be org.apache.axis.providers.RawXMLProvider, which are similar to that of
the <strong>“Echo Synchronous call” </strong>. The difference is that there
will be a handler that will be added in the server side. For further discussion refer the
following service.xml which will be used in deploying the service. </p>
 <p class="style1 style2 style3">&lt;service provider=&quot;org.apache.axis.providers.RawXMLProvider&quot;
style=&quot;rpc&quot;&gt; <br>
@@ -400,10 +403,9 @@
 <p>In this case the example focuses on calling a synchronous web service in an asynchronous
manner in the client side. If this example is compared with the first example, which is <strong>“Echo
Synchronous call” </strong>, the server side is identical for both the cases. The difference
will be in the web service client that will be used. </p>
 <p>In this case the client will make a web service call and it will register a call
back handler and sends the message out. The difference will be that the client application
that is doing the web service call will not hang till the response. Rather it will get returned
and once the response returns the client will get notified by way of the registered callback
(This is one of the two methods this can be done in Axis 2.0. Refer <a href="ClientAPI.html">Client
Api Tutorial </a> for more information). </p>
 <p>The callback handler that will be used is ClientEchoCallbackHandler.java and the
client program is AsynchronousClient.java. </p>
-<h3><strong>Building the sample </strong></h3>
-<p>Building the sample once will build all required classes and jars for all three
cases. The ant task would be “ant Compile”. Please refer the building of the <strong>“Echo
Synchronous call” </strong> above. </p>
-<h3><strong>Deploying the sample </strong></h3>
-<p>The web service that will be called is the <strong>sample1 </strong>
service which is used in the <strong>“Echo Synchronous call” </strong> case.
If the web service is not already deployed please refer “Deploying the sample” of <strong>“Echo
Synchronous call” </strong> above. </p>
+
+<p>It is assumed that the sample is already compiled. Please refer the "Building Sample1"
above. </p>
+<p>On the other hand the Case3 uses the <strong>sample1</strong> web service.
Thus if the user has already deployed sample1 web service in Case1 above then there is no
requirement of deploying again. Please refer Case1 deploying to deploy the required service
above.</p>
 <h3><strong>Running the sample </strong></h3>
 <p>The class to run is AsynchronousClient.java and it will intialise the web service
call. It will register a call back in this case an instance of the ClientEchoCallbackHandler
and then client will sleep to keep the thread alive. Eventually when the response is received
the callback handler will be called(if all goes well onComplete() method will be called),
in this case the ClientEchoCallbackHandler instance that was registered. </p>
 <p>Inside the ClientEchoCallbackHandler it will print the received SOAP message. Please
refer the code. </p>



Mime
View raw message