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 di...@apache.org on 2006/09/28 22:40:24 UTC
svn commit: r451028 - in /webservices/axis2/trunk/java/xdocs/1_1:
userguide.html userguide2.html userguide5.html
Author: dims
Date: Thu Sep 28 13:40:23 2006
New Revision: 451028
URL: http://svn.apache.org/viewvc?view=rev&rev=451028
Log:
one round of review from me
Modified:
webservices/axis2/trunk/java/xdocs/1_1/userguide.html
webservices/axis2/trunk/java/xdocs/1_1/userguide2.html
webservices/axis2/trunk/java/xdocs/1_1/userguide5.html
Modified: webservices/axis2/trunk/java/xdocs/1_1/userguide.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/userguide.html?view=diff&rev=451028&r1=451027&r2=451028
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/userguide.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/userguide.html Thu Sep 28 13:40:23 2006
@@ -10,9 +10,9 @@
User's Guide</h1>
<p>This document describes how to write Web services and Web service clients
-using Axis2. It also describes how to write a custom module and engaging it
-with a Web service. Samples which are shipped with the binary distribution of
-Axis2, are also discussed. It also contains a section on Advanced Topics.</p>
+using Axis2. It also describes how to write custom modules and using them
+with a Web service. Advanced Topics and Samples which are shipped with
+the binary distribution of Axis2, are also discussed. </p>
<p align="right">Pages: <b>Content</b>, <a href="userguide1.html">1</a>, <a
href="userguide2.html">2</a>, <a href="userguide3.html">3</a>, <a
@@ -22,7 +22,6 @@
<ul>
<li><p><a href="userguide1.html#Axis2_User's_Guide">Introduction</a></p>
<ul>
- <li><a href="userguide1.html#Attention">Attention</a></li>
<li><a href="userguide1.html#What_is_Axis2_">What is Axis2?</a></li>
<li><a href="userguide1.html#Axis2_Complete_Features_List">Axis2
Feature List & Tools</a></li>
@@ -32,13 +31,12 @@
Axis2</a></p>
<ul>
<li><a
+ href="userguide2.html#Getting_started">Getting Started</a>
+ <li><a
href="userguide2.html#Writing_Web_Services_Using Axis2's_Primary_APIs">Writing
Web Services using Axis2 APIs</a>
<ul>
- <li><a
- href="userguide2.html#Creating_Web_Service__MyService_">Creating
- Web Service (MyService)</a></li>
- <li><a href="userguide2.html#How_to_write_the_Web_Service_">How to
+ <li><a href="userguide2.html#How_to_write_the_Web_Service_">How to
write the Web Service?</a>
<ul>
<li><a
@@ -61,16 +59,25 @@
href="userguide2.html#Writing_Web_Services_by_Code_Generating_Skeleton">Writing
Web Services by Code Generating Skeleton</a></p>
<ul>
- <li><a href="userguide2.html#WSDL2Java_Tool">WSDL2Java Tool</a></li>
- <li><a
- href="userguide2.html#Implement_the_Business_Logic">Implement the
- Business Logic</a></li>
- <li><a href="userguide2.html#echoString">echoString</a></li>
- <li><a
- href="userguide2.html#echoStringArray">echoStringArray</a></li>
- <li><a href="userguide2.html#echoStruct">echoStruct</a></li>
- <li><a href="userguide2.html#services_xml">services.xml</a></li>
- <li><a href="userguide2.html#Packaging">Packaging</a></li>
+ <li><a href="userguide2.html#How_to_write_the_Web_Service_2">How to
+ write the Web Service?</a>
+ <ul>
+ <li><a
+ href="userguide2.html#Step1_:Generate_skeleton">Step 1: Generate Skeleton Code</a></li>
+ <li><a
+ href="userguide2.html#Step2_Implement_Business_Logic">Step2
+ :Implement Business Logic</a></li>
+ <li><a
+ href="userguide2.html#Step3_:Verify_services_xml">Step3
+ :Verify services.xml file</a></li>
+ <li><a
+ href="userguide2.html#Step4_Create_archive">Step4
+ :Create the Web Service Archive file</a></li>
+ <li><a
+ href="userguide2.html#Step5_Deploy_web_service">Step5
+ :Deploy the Web Service</a></li>
+ </ul>
+ </li>
</ul>
</li>
</ul>
Modified: webservices/axis2/trunk/java/xdocs/1_1/userguide2.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/userguide2.html?view=diff&rev=451028&r1=451027&r2=451028
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/userguide2.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/userguide2.html Thu Sep 28 13:40:23 2006
@@ -18,47 +18,39 @@
href="userguide1.html">1</a>, <b>2</b>, <a href="userguide3.html">3</a>, <a
href="userguide4.html">4</a>, <a href="userguide5.html">5</a></p>
-<p><b><font size="4">Note (on samples):</font></b> In this page of the user's
-guide we will look at how to write and deploy Web services using Axis2. All
-samples mentioned in this guide are located in the
-<b>"samples\userguide\src"</b> directory of the binary distribution.</p>
-
<h2><a name="Web_Services_Using_Axis2">Web Services Using Axis2</a></h2>
-
-<p>Before starting, please check if you have deployed the "axis2.war" in your
-servlet container and it is working properly. (See <a
-href="installationguide.html" target="_blank">Installation Guide</a>). Users
-can select any of the following two ways to write Web services using Axis2.
+<p> In this section, we will learn how to write and deploy web services using Axis2. All
+the samples mentioned are located in the <b>"samples\userguide\src"</b>
+directory of the binary distribution.</p>
+
+<h3><a name="Getting_started">Getting Started</a></h3>
+<p>Please deploy axis2.war in your servlet container and ensure that it works fine.
+Please refer to the <a
+href="installationguide.html" target="_blank">Installation Guide</a> for instructions.
+</p>
+<p>Users can use either of the following two ways to write Web services using Axis2.
</p>
<ol>
<li><a href="#Writing_Web_Services_Using Axis2's_Primary_APIs">Use Axis2's
primary interfaces (APIs) and implement the business logic.</a></li>
<li><p><a href="#Writing_Web_Services_by_Code_Generating_Skeleton">Start
from the WSDL ->Code generate the Skeleton ->Implement the Business
- Logic.</a></p>
+ Logic.</a></p>
</li>
</ol>
-<h3><a name="Writing_Web_Services_Using Axis2's_Primary_APIs">Writing Web
-Services Using Axis2's Primary APIs</a></h3>
+<p>The complete code for this example Web service (MyService) can be found in the
+"Axis2Home/samples/userguide/src" directory under "userguide/example1"
+package. </p>
-<h4><a name="Creating_Web_Service__MyService_">Creating Web Service
-(MyService)</a></h4>
-<p>First let's see how we can write a simple Web service (MyService) using
-Axis2's primary interfaces and deploy it. For this purpose we will create a
-Web service with two operations as follows.</p>
-<pre>public void ping(OMElement element){} //IN-ONLY operation, just accepts the OMElement and do some processing.
+<h3><a name="Writing_Web_Services_Using Axis2's_Primary_APIs">1. Writing Web
+Services Using Axis2's Primary APIs</a></h3>
+In our example, the web service will have two operations.
+<pre>public void ping(OMElement element){} //IN-ONLY operation, just accepts the OMElement and does some processing.
public OMElement echo(OMElement element){}//IN-OUT operation, accepts an OMElement and
- // sends back the same again </pre>
-
-<p>Complete code for this example Web service (MyService) can be found in the
-"Axis2Home/samples/userguide/src" directory under "userguide/example1"
-package. As you can see, the two operations are very simple and need no
-explanations on what they do. Now let's see how we can write the deployment
-descriptors for the service and deploy it.</p>
-
-<h4><a name="How_to_write_the_Web_Service_">How to write the Web
+ // sends back the same again </pre>
+<h4><a name="How_to_write_the_Web_Service_">How to write a Web
Service?</a></h4>
Writing a new Web service with Axis2 involves four steps:
<ol>
@@ -67,35 +59,38 @@
<li><p style="margin-bottom: 0in">Write a services.xml file to explain the
Web service</p>
</li>
- <li><p style="margin-bottom: 0in">create a *.aar archive (Axis Archive) for
+ <li><p style="margin-bottom: 0in">Create a *.aar archive (Axis Archive) for
the Web service</p>
</li>
- <li><p>Deploy the Web service</p>
+ <li><p style="margin-bottom: 0in">Deploy the Web service</p>
</li>
</ol>
<h4><a name="Step1_:Write_the_Implementation_Class">Step1 :Write the
Implementation Class</a></h4>
-<p>Provide an implementation class that has the business logic for the Web
-service. It should have methods that match the operations in the Web service.
+<p>An implementation class has the business logic for the Web
+service and implements the operations provided by the Web service.
Unless you have data binding, the signature of the methods can have only one
parameter of type OMElement.</p>
<pre>public class MyService{
public void ping(OMElement element){
- ......
+ // Business Logic
+ ......
}
public OMElement echo(OMElement element){
......
}
}</pre>
+
+
<h4><a name="Step2_:Write_the_services_xml_file">Step2 :Write the
services.xml file</a></h4>
-<p>Axis2 uses "services.xml" to keep configurations for a Web service. Each
-Web service deployed in Axis2 needs a "services.xml" containing the
-configurations. "services.xml" for MyService will be as follows.</p>
+<p>"services.xml" has the configuration for a web Service. Each web service, deployed in Axis2 ,
+must have its configuration in "services.xml". The configuration for MyService is as follows:
+</p>
<pre><service >
<description>
This is a sample Web service with two operations, echo and ping.
@@ -113,13 +108,18 @@
<p><em>The above XML tags can be explained as follows:</em></p>
-<p>First comes the description and the service class.</p>
-<pre><parameter name="serviceClass" locked="false">userguide.example1.MyService</parameter></pre>
+<p>The description of the service class is provided in the description tag. </p>
+<pre><service >
+ <description>
+ This is a sample Web service with two operations, echo and ping.
+ </description>
+</pre>
-<p>We provide the name of the service implementation class a parameter in the
-services.xml file.</p>
+<p>The name of the service class is provided as a parameter.
+</p>
+<pre><parameter name="serviceClass" locked="false">userguide.example1.MyService</parameter></pre>
-<p>The next two xml tags describe the operations that are available in this
+<p>The "operation" xml tag describes the operations that are available in this
service with respective message receivers.</p>
<pre> <operation name="echo">
<messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
@@ -130,10 +130,10 @@
<actionMapping>urn:ping</actionMapping>
</operation></pre>
-<p>Every operation must have a corresponding MessageReceiver class. When
-Axis2 engine receives a message, after the message is being processed by the
-handlers, it will be handed over to a MessageReceiver. <br>
-For the "echo" operation we have used a
+<p>Every operation must map to a corresponding MessageReceiver class.
+After a message is processed by the handlers, Axis2 engine hands it over to
+a MessageReceiver. <br>
+For the "echo" operation, we have used a
<strong>RawXMLINOutMessageReceiver</strong> since it is an IN-OUT operation.
For IN-ONLY operation "ping", we have used
<strong>RawXMLINOnlyMessageReceiver</strong> as the message receiver.</p>
@@ -158,57 +158,72 @@
<parameter name="serviceGroupParam1" locked="false">value 1</parameter>
</serviceGroup></pre>
-<p>Note : name of the service is a compulsory attribute</p>
+<p>Note : name of the service is a compulsory attribute. </p>
<h4><a name="Step3_:Create_the_Web_Service_Archive">Step3 :Create the Web
Service Archive</a></h4>
<p>Axis2 uses ".aar" (Axis Archive) file as the deployment package for Web
-services. Therefor, for MyService we will use "MyService.aar" with the
-"services.xml" packaged in the META-INF as shown in the following picture.
-(Name of the service will be the name of the archive file , if and only if
-the services.xml contains only one service element).</p>
+services. Therefore, for MyService we will use "MyService.aar" with the
+"services.xml" packaged in the META-INF in directory structure shown below.
+Please note that the name of the archive file will be same as that of the service only if
+the services.xml contains only one service element.</p>
<p><img src="images/userguide/ServiceItems.jpg" name="Graphic1"
align="bottom" width="176" height="91" border="0"></p>
-<p>To create "MyService.aar" user can first create a jar file containing all
-the files necessary for the service and then rename the "jar" to "aar" so
-that Axis2 understands it as a service archive. This has already been created
-in the "Axis2Home/samples/userguide" directory. Now let's use it...</p>
+<p>To create the archive file, you can create a jar file containing all the necessary files
+and then rename it to .aar file.This archive file can be found in the "Axis2Home/samples/userguide" directory.
+This file now has to be deployed. </p>
<h4><a name="Step4_:Deploy_the_Web_Service">Step4 :Deploy the Web
Service</a></h4>
-<p>Deploying the service is just a matter of dropping the ".aar" in to
-"services" directory that can be found in the "\webapps\axis2\WEB-INF" of
-your servlet container, hence copy the "MyService.aar" into the
-"<b>services</b>" directory. Once these steps are completed, start the
+<p>The service can be deployed by dropping dropping the ".aar" file in to
+"services" directory in "\webapps\axis2\WEB-INF" of
+your servlet container.Start the
servlet container (if you have not already started) and check the link
"Services" on the <a href="http://localhost:8080/axis2/" target="_blank">Home
Page of Axis2 Web Application</a> (http://localhost:8080/axis2) and see
whether the MyService is deployed properly. If you can see the following
-output then you have successfully deployed MyService on Axis2.</p>
+output then you have successfully deployed MyService on Axis2. Congratulations !!</p>
<p align="center"><img src="images/userguide/MyServiceDeployed.jpg"
name="Graphic2" align="bottom" border="0"></p>
<p>Note: Axis2 provides an easy way to deploy Web services using the "Upload
-Service" tool on Axis2 Web Application's Administration module. (See the <a
+Service" tool on Axis2 Web Application's Administration module. Please refer to the <a
href="webadminguide.html" target="_blank">Web Administration Guide</a> for
-more information on this)</p>
+more information.</p>
-<h3><a name="Writing_Web_Services_by_Code_Generating_Skeleton">Writing Web
+<h3><a name="Writing_Web_Services_by_Code_Generating_Skeleton">2. Writing Web
Services by Code Generating Skeleton</a></h3>
-<p>This is the second method of writing Web services using Axis2. Let's see
-how we can generate the skeleton from a given WSDL and implement the business
-logic using Axis2. For this we use Axis2SampleDocLit.wsdl that can be found
-in the <b>wsdl</b> directory under samples.</p>
+<p>This is the second method of writing Web services using Axis2. In this method,
+we generate the skeleton from a given WSDL and implement the business
+logic in the classes generated. For this example, we will use Axis2SampleDocLit.wsdl.
+This can be found in the <b>wsdl</b> directory under samples.</p>
-<h4><a name="WSDL2Java_Tool">WSDL2Java Tool</a></h4>
+<h4><a name="How_to_write_the_Web_Service_2">How to write a Web
+Service?</a></h4>
+This method of writing a Web service with Axis2 involves five steps:
+<ol>
+ <li><p style="margin-bottom: 0in">Generate the skeleton code</p>
+ </li>
+ <li><p style="margin-bottom: 0in">Add business logic</p>
+ </li>
+ <li><p style="margin-bottom: 0in">Verify generated services.xml</p>
+ </li>
+ <li><p style="margin-bottom: 0in">Create a *.aar archive (Axis Archive) for
+ the Web service</p>
+ </li>
+ <li><p style="margin-bottom: 0in">Deploy the Web service</p>
+ </li>
+</ol>
-<p>To generate the skeleton and the required classes you can use the
+<h4><a name="Step1_:Generate_skeleton">Step1 :Generate Skeleton Code</a></h4>
+
+<p>To generate the skeleton and required classes, you can use the
WSDL2Java tool provided in Axis2. This tool is located in the bin directory
of the distribution and can be executed using the provided scripts (.bat or
.sh). The tool's parameter list is as follows and users can specify these
@@ -229,13 +244,15 @@
-u : unpacks the databinding classes
-r <repository_path> : path of the repository against which code is generated</pre>
-<p>We will use the tool with the following parameters and generate the
-skeleton and the other required classes.</p>
+<p>The parameters for wsdl2java tool in our example are as follows:</p>
+
+<h5> Windows </h5>
-<p>Windows users can use the following command in the console:</p>
+<!--<p>Windows users can use the following command in the console:</p> -->
<pre style="margin-bottom: 0.2in">WSDL2Java.bat -uri ..\samples\wsdl\Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ..\samples -p org.apache.axis2.userguide</pre>
-<p>Linux users should switch the file separator:</p>
+<h5> Linux </h5>
+<!--<p>Linux users should switch the file separator:</p> -->
<pre style="margin-bottom: 0.2in">WSDL2Java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o ../samples -p org.apache.axis2.userguide</pre>
<p>This will generate the required classes in the <b>src</b> directory inside
@@ -244,14 +261,13 @@
dir<strong></strong>. Note that these are not source files and should be
available in the class path in order to compile the generated classes.</p>
-<h4><a name="Implement_the_Business_Logic">Implement the Business
+<h4><a name="Step2_Implement_Business_Logic">Step 2: Implement Business
Logic</a></h4>
-<p>Locate the skeleton class that can be found under
-src/org/apache/axis2/userguide directory with the name
-"Axis2SampleDocLitServiceSkeleton.java". This is the skeleton for our Web
-service and we can now easily implement the business logic. The WSDL we have
-used has three operations: <!--<li><p style="margin-bottom: 0in">echoVoid - Operation that does not
+<p>Implement the business logic in the skeleton class.
+The skeleton class "Axis2SampleDocLitServiceSkeleton.java" can be found in
+src/org/apache/axis2/userguide directory. Our sample WSDL has
+three operations: <!--<li><p style="margin-bottom: 0in">echoVoid - Operation that does not
accept any input parameters and also provide no out put parameters. Just
perform some task </p>
</li>-->
@@ -259,16 +275,15 @@
<ul>
<li><p style="margin-bottom: 0in">echoString - echoes a String value </p>
</li>
- <li><p style="margin-bottom: 0in">echoStringArray - accept string array as
- the input and echoes them back</p>
+ <li><p style="margin-bottom: 0in">echoStringArray - echoes a String Array</p>
</li>
- <li><p>echoStruct - accept a Struct as the input and echoes them back.</p>
+ <li><p style="margin-bottom: 0in">echoStruct - echoes a Struct</p>
</li>
</ul>
<!--<h4>echoVoid </h4>
-<p>Locate the following code segment in the
-"Axis2SampleDocLitServiceSkeleton.java" and fill the business logic. For
+<p>Locate the following code segment in
+"Axis2SampleDocLitServiceSkeleton.java" and add the business logic. For
the explanation purpose we do not need anything to be implemented here.</p>
<pre>public void echoVoid(){
//Todo fill this with the necessary business logic
@@ -276,8 +291,8 @@
<h4><a name="echoString">echoString</a></h4>
-<p>Locate the following code segment in the
-"Axis2SampleDocLitServiceSkeleton.java" and fill the business logic as shown
+<p>Locate the following code segment in "Axis2SampleDocLitServiceSkeleton.java"
+and add the business logic as shown
below.</p>
<pre> public org.apache.axis2.userguide.xsd.EchoStringReturnDocument echoString
(org.apache.axis2.userguide.xsd.EchoStringParamDocument param4 ){
@@ -286,8 +301,8 @@
}
</pre>
-<p>Once filled with the business logic it will be as follows. The code is
-simple and the explanations are given as comments.</p>
+<p>Once the business logic is added, the source code appears as below:
+</p>
<pre>public org.apache.axis2.userguide.xsd.EchoStringReturnDocument echoString
(org.apache.axis2.userguide.xsd.EchoStringParamDocument param4) throws Exception {
//Use the factory to create the output document.
@@ -297,10 +312,12 @@
return retDoc;
}</pre>
-<p>Similarly, the following code fragments shows how you can fill the
-business logic for our first Web service.</p>
+
<h4><a name="echoStringArray">echoStringArray</a></h4>
+
+<p>The code segment for echoStringArray is shown below:</p>
+
<pre>public org.apache.axis2.userguide.xsd.EchoStringArrayReturnDocument echoStringArray
(org.apache.axis2.userguide.xsd.EchoStringArrayParamDocument param0) throws Exception {
//Use the factory to create the output document.
@@ -318,6 +335,9 @@
}</pre>
<h4><a name="echoStruct">echoStruct</a></h4>
+
+<p>The code segment for echoStruct is shown below:</p>
+
<pre>public org.apache.axis2.userguide.xsd.EchoStructReturnDocument echoStruct
(org.apache.axis2.userguide.xsd.EchoStructParamDocument param2) throws Exception {
//Use the factory to create the output document.
@@ -339,13 +359,13 @@
return retDoc;
}</pre>
-<h4><a name="services_xml">services.xml</a></h4>
-<p> Axis2 uses "services.xml" to hold the configurations for a particular Web
-service deployed in the Axis2 engine. When we generate the skeleton using the
-WSDL2Java tool, it will also generate the required services.xml for this Web
-service as well. This can be found in the same directory as the skeleton. The
-generated services.xml is as follows.</p>
+<h4><a name="Step3_:Verify_services_xml">Step3 :Verify generated services.xml</a></h4>
+
+<p> As mentioned earlier, "services.xml" file holds all the configuration informatinn for
+for a webservice. When the skeleton is generated using the WSDL2Java tool,
+the services.xml file is also generated. This file can be found in the same directory as the
+skeleton. The generated services.xml is as follows.</p>
<pre><!-- This file was auto-generated from WSDL -->
<!-- by the Apache Axis2 version: #axisVersion# #today# -->
<serviceGroup>
@@ -374,36 +394,35 @@
operations that are available in this service with respective message
receivers.</p>
-<h4><a name="Packaging">Packaging</a></h4>
+<h4><a name="Step4_Create_archive">Step 4: Create Archive file</a></h4>
-<p>The next step in this process is to package the classes in an .aar (axis2
+<p>The next step is to package the classes in an .aar (axis2
archive) and deploy it in Axis2. When the WSDL2Java tool generates the
-skeleton it will also generate the required data binding classes. These
+skeleton, it will also generate the required data binding classes. These
schema related classes are located in the
<strong>schemaorg_apache_xmlbeans</strong> directory inside resources
directory of the generated code. Copy this to your class path, compile the
-skeleton and the supporting classes. In order to create the .aar file, let's
-create the following directory structure with the required files and then
-simply use jar command to package it.</p>
+skeleton and the supporting classes. To create the .aar file, create the following
+directory structure with the required files and then jar it up.2:45 PM 9/28/2006</p>
<p><img src="images/userguide/DirectoryStructure.jpg" align="bottom"
border="0"></p>
<p>Go to the top level directory where you can find the class files for the
above service (i.e. one level up on the directory structure shown above),
-then type the following command in a command line.</p>
+then run the following on the command line</p>
<pre style="margin-bottom: 0.2in">jar -cf Axis2SampleDocLitService.aar .</pre>
-<p>Deploying the service is just a matter of dropping the ".aar" in to
-"services" directory that can be found in the "\webapps\axis2\WEB-INF" of
-your servlet container, hence copy the "Axis2SampleDocLitService.aar" into
-the "<b>services</b>" directory. Once these steps are completed, please start
-the servlet container (if you have not already started) and check the link
+<h4><a name="Step5_Deploy_web_service">Step 5: Deploy Web Service</a></h4>
+
+<p>The service can be deployed by dropping dropping the ".aar" file in to
+"services" directory in "\webapps\axis2\WEB-INF" of
+your servlet container.Start the
+servlet container (if you have not already started) and check the link
"Services" on the <a href="http://localhost:8080/axis2/" target="_blank">Home
-Page of Axis2 Web Application</a> (http://localhost:8080/axis2/) and see
-whether the Axis2SampleDocLitService is deployed properly. If you can see the
-following output then you have successfully deployed Axis2SampleDocLitService
-on Axis2.</p>
+Page of Axis2 Web Application</a> (http://localhost:8080/axis2) and see
+whether the Axis2SampleDocLitService is deployed properly. If you can see the following
+output then you have successfully deployed Axis2SampleDocLitService on Axis2. Congratulations !!</p>
<p align="center"><img src="images/userguide/ServiceDeployed.jpg"
name="Graphic4" align="bottom" border="0"></p>
Modified: webservices/axis2/trunk/java/xdocs/1_1/userguide5.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/userguide5.html?view=diff&rev=451028&r1=451027&r2=451028
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/userguide5.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/userguide5.html Thu Sep 28 13:40:23 2006
@@ -1,84 +1,56 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
- "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
- <meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
- <title>Axis2 User's Guide</title>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+ "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+ <meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
+
+<title>Axis2 User's Guide</title>
</head>
-
<body lang="en-US" dir="ltr">
<h4><a name="Axis2_User's_Guide">Axis2 User's Guide</a></h4>
-
-<p><i>User Feedback: <a
-href="mailto:axis-user@ws.apache.org">axis-user@ws.apache.org</a></i>. Prefix
-subject with [Axis2]. To subscribe to mailing list see <a
-href="http://ws.apache.org/axis2/mail-lists.html">here.</a></p>
-
-<p align="right">Pages: <a href="userguide.html">Content</a>, <a
-href="userguide1.html">1</a>, <a href="userguide2.html">2</a>, <a
-href="userguide3.html">3</a>, <a href="userguide4.html">4</a>, <b>5</b></p>
-
-<p><font size="4"><b>Note (on samples):</b></font> All samples mentioned in
-the user's guide are located at <b>"samples\userguide\src"</b> directory of
-the binary distribution.</p>
-
+<p><i>User Feedback: <a href="mailto:axis-user@ws.apache.org">axis-user@ws.apache.org</a></i>. Prefix subject with [Axis2]. To subscribe to mailing list see <a href="http://ws.apache.org/axis2/mail-lists.html">here.</a></p>
+<p align="right">Pages: <a href="userguide.html">Content</a>,
+<a href="userguide1.html">1</a>, <a href="userguide2.html">2</a>,
+<a href="userguide3.html">3</a>, <a href="userguide4.html">4</a>,
+<b>5</b></p>
+<p><font size="4">
+<b>Note (on samples):</b></font>
+All samples mentioned in the user's guide are located at <b>"samples\userguide\src"</b> directory of
+the binary distribution.</p>
<h2><a name="Other_Samples">Other Samples</a></h2>
-
-<p>To show you the power of using Axis2, three standard samples are shipped
-with the binary distribution. These are meant to interact with external Web
-services and prove the capabilities of the Axis2 system.</p>
-
-<p>The samples included are</p>
+<p>To show the power of usage of Axis2, three standard samples are shipped
+with the binary distribution. These are meant to interact with outside Web services and prove the capabilities of the Axis2 system.</p>
+<p>The included samples are</p>
<ul>
- <li><style="margin-bottom: 0in">Google spell checker sample</li>
- <li><p style="margin-bottom: 0in">Google search sample</p>
- </li>
- <li><p style="margin-bottom: 0in">Amazon queuing sample</p>
- </li>
+ <li><style="margin-bottom: 0in">Google spell checker sample</li>
+ <li><p style="margin-bottom: 0in">Google search sample</p> </li>
+ <li><p style="margin-bottom: 0in">Amazon queuing sample</p> </li>
</ul>
-
-<p>A simple introduction to each of the above samples are given below. Each
-sample contains it's own help document that talks about the usage and the
-advanced operations of that particular sample.</p>
-
-<p>All of the above samples are included in the samples directory in the
-binary distribution. The shell scripts and the batch files are in fact
-written to use the binary distribution's root directory as the home in order
-to find the libraries.</p>
-
-<p>The alternate method is to build the samples from the source. Moving them
-to modules/samples and running maven will create the samples in the
-target/samples directory. However if the samples need to be started using the
-shell scripts (or the batch files) then the AXIS2_HOME environment needs to
-be set.( the "guessed" AXIS2_HOME would not be correct in this case)</p>
-
+<p>A simple introduction to each of the above samples are given below. Each sample contains it's own
+help document that speaks about the usage and the advanced operations of that particular sample.</p>
+<p>The most obvious place to look for the samples are the binary distribution. All these samples are included in the samples directory in the binary distribution. The shell scripts and the batch files are in fact
+written to use the binary distribution's root directory as the home in order to find the libraries.</p>
+<p>The alternate method is to build the samples from source. Moving to the
+modules/samples and running maven
+will create the samples in the target/samples directory. However if the samples need to be started using
+the shell scripts (or the batch files) then the AXIS_HOME environment need to be set.( the "guessed" AXIS_HOME would not be correct in this case)</p>
<h3><a name="Google_Spell_Checker_Sample">Google Spell Checker Sample</a></h3>
-
-<p>This includes a spell checker program that uses the Google spell checking
-service. It demonstrates the blocking and non-blocking modes of calling the
-service. This sample can be found at the samples\googleSpellcheck directory
-of the dist and can be easily started using either the batch file or the
-shell script.</p>
-
+<p>This includes a spell checker program that uses the Google spell checking service. It demonstrates the blocking and non-blocking modes of calling the
+service. This sample can be found at the samples\googleSpellcheck directory and can be easily started using either the batch file or the shell script.</p>
<h3><a name="Google_Search_Sample">Google Search Sample</a></h3>
-
-<p>This includes a search program that uses the familiar Google search over
-the SOAP API. It utilizes the non-blocking mode of the client API. This
-sample can be found at the samples\googleSearch directory of the dist and can
-be easily started using either the batch file or the shell script.</p>
-
+<p>This includes a search program that uses the familiar Google search over
+the SOAP API. It utilizes the non-blocking mode of the client API. This sample can be found at the samples\googleSearch directory and can be easily
+started using either the batch file or the shell script.</p>
<h3><a name="Amazon_Queuing_Service">Amazon Queuing Service</a></h3>
-
-<p>Amazon queuing service sample shows how to use the Amazon queuing service.
-It has two user interfaces , one to enqueue and the other to dequeue. This
-sample is included in the samples\amazonQS directory of the dist with the
-required batch/shell scripts to run the sample.</p>
-
-<p align="right"><a href="userguide4.html"><img src="images/arrow_left.gif">
-Previous Page</a></p>
-
-<p>Pages: <a href="userguide.html">Content</a>, <a
-href="userguide1.html">1</a>, <a href="userguide2.html">2</a>, <a
-href="userguide3.html">3</a>, <a href="userguide4.html">4</a>, <b>5</b></p>
+<p>Amazon queuing service sample shows how to use the Amazon queuing service. It has two user interfaces,
+ one to enqueue and the other to dequeue. This sample is included in the samples\amazonQS directory with
+the required batch/shell scripts to run the sample.</p>
+<p align="right"><a href="userguide4.html"><img src="images/arrow_left.gif">Previous Page</a></p>
+<p>Pages: <a href="userguide.html">Content</a>,
+<a href="userguide1.html">1</a>,
+<a href="userguide2.html">2</a>,
+<a href="userguide3.html">3</a>,
+<a href="userguide4.html">4</a>,
+<b>5</b></p>
</body>
-</html>
+</html>
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-cvs-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-cvs-help@ws.apache.org