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 2007/03/12 05:49:38 UTC
svn commit: r517097 - in /webservices/axis2/trunk/java/xdocs/1_1: toc.html
userguide-buildingservices.html userguide-codelisting5.html userguide.html
Author: chatra
Date: Sun Mar 11 21:49:38 2007
New Revision: 517097
URL: http://svn.apache.org/viewvc?view=rev&rev=517097
Log:
reviewed and committing patch in AXIS2-2304 jira
Modified:
webservices/axis2/trunk/java/xdocs/1_1/toc.html
webservices/axis2/trunk/java/xdocs/1_1/userguide-buildingservices.html
webservices/axis2/trunk/java/xdocs/1_1/userguide-codelisting5.html
webservices/axis2/trunk/java/xdocs/1_1/userguide.html
Modified: webservices/axis2/trunk/java/xdocs/1_1/toc.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/toc.html?view=diff&rev=517097&r1=517096&r2=517097
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/toc.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/toc.html Sun Mar 11 21:49:38 2007
@@ -8,6 +8,7 @@
<!--
ul { list-style-type: none; margin: 0 0 0 5px; padding: 0; border-width: 0; list-style-position: outside; }
-->
+
</style>
</head>
@@ -21,11 +22,11 @@
Modules</a></li>
<li><a href="app_server.html" target="mainFrame">Application Server
Specific Configuration Guide</a></li>
- <li><a href="quickstartguide.html" target="mainFrame">QuickStart
+ <li><a href="quickstartguide.html" target="mainFrame">Quick Start
Guide</a></li>
<li><a href="userguide.html" target="mainFrame">User's Guide</a></li>
- <li><a href="adv-userguide.html" target="mainFrame">Advance User's
- Guide</a></li>
+ <li><a href="adv-userguide.html" target="mainFrame">Advanced User's
+ Guide</a></li>
<li><a href="axis2config.html" target="mainFrame">Configuration
Guide</a></li>
<li><a href="Axis2ArchitectureGuide.html" target="mainFrame">Architecture
@@ -40,26 +41,26 @@
<li>13.2 <a href="adb/adb-advanced.html" target="mainFrame">Advanced
Features</a></li>
<li>13.3 <a href="adb/adb-codegen-integration.html"
- target="mainFrame">Code generation integration</a></li>
+ target="mainFrame">Code Generation Integration</a></li>
<li>13.4 <a href="adb/adb-tweaking.html"
target="mainFrame">Tweaking</a></li>
</ul>
</li>
- <li>JiBX Data binding
+ <li>JiBX Data Binding
<ul>
<li>14.1 <a href="jibx/jibx-codegen-integration.html"
- target="mainFrame">Code generation integration</a></li>
+ target="mainFrame">Code Generation Integration</a></li>
<li>14.2 <a href="jibx/jibx-doclit-example.html"
- target="mainFrame">doc/lit example</a></li>
+ target="mainFrame">doc/lit Example</a></li>
<li>14.3 <a href="jibx/jibx-unwrapped-example.html"
- target="mainFrame">unwrapped example</a></li>
+ target="mainFrame">unwrapped Example</a></li>
</ul>
</li>
<li>Advanced
<ul>
- <li>15.1 <a href="xmlbased-server.html" target="mainFrame">AXIOM based
+ <li>15.1 <a href="xmlbased-server.html" target="mainFrame">AXIOM Based
Service</a></li>
- <li>15.2 <a href="dii.html" target="mainFrame">AXIOM based
+ <li>15.2 <a href="dii.html" target="mainFrame">AXIOM Based
Client</a></li>
</ul>
</li>
@@ -86,14 +87,14 @@
Guide</a></li>
<li><a href="soapmonitor-module.html" target="mainFrame">SOAP
Monitor</a></li>
- <li><a href="reference.html" target="mainFrame">Command line tools</a></li>
- <li><a href="../tools/index.html" target="mainFrame">Tools/Plugins</a>
+ <li><a href="reference.html" target="mainFrame">Command Line Tools</a></li>
+ <li><a href="../tools/index.html" target="mainFrame">Tools/Plug-ins</a>
<ul>
<li>23.1 <a href="../tools/1_1/CodegenToolReference.html"
target="mainFrame">Code Generator Tool - Command Line and Ant
Task</a></li>
<li>23.2 <a href="../tools/1_1/idea/Idea_plug-in_userguide.html"
- target="mainFrame">Axis2 plugin for IntelliJ IDEA</a></li>
+ target="mainFrame">Axis2 Plug-in for IntelliJ IDEA</a></li>
<li>23.3 <a href="../tools/1_1/eclipse/servicearchiver-plugin.html"
target="mainFrame">Service Archive Generator Wizard - Eclipse
Plug-in</a></li>
Modified: webservices/axis2/trunk/java/xdocs/1_1/userguide-buildingservices.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/userguide-buildingservices.html?view=diff&rev=517097&r1=517096&r2=517097
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/userguide-buildingservices.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/userguide-buildingservices.html Sun Mar 11 21:49:38 2007
@@ -13,27 +13,27 @@
<h1>Apache Axis2 User's Guide -Building Services</h1>
<p>Now that you know how to use Axis2 to generate clients from WSDL, this
-section digs a little deeper, showing you how to create services, and how to
-create both services and clients "from scratch", so to speak.</p>
+section digs a little deeper showing you how to create services, and also how
+to create services and clients "from scratch", so to speak.</p>
<ul>
<li><a href="userguide.html#intro">Introducing Axis2</a><br />
<ul>
- <li><a href="userguide.html#whatis">What is Axis2</a></li>
- <li><a href="userguide.html#underhood">What's under the hood?</a></li>
- <li><a href="userguide.html#handlessoap">How Axis2 handles SOAP
- messages</a></li>
- <li><a href="userguide.html#distributions">Axis2 distributions</a></li>
+ <li><a href="userguide.html#whatis">What is Axis2?</a></li>
+ <li><a href="userguide.html#underhood">What's Under the Hood?</a></li>
+ <li><a href="userguide.html#handlessoap">How Axis2 Handles SOAP
+ Messages</a></li>
+ <li><a href="userguide.html#distributions">Axis2 Distributions</a></li>
<li><a href="userguide.html#sbd">The Axis2 Standard Binary
Distribution</a></li>
<li><a href="userguide.html#hierarchy">Axis2.war Directory
- hierarchy</a></li>
+ Hierarchy</a></li>
<li><a href="userguide.html#docs">Axis2 Documents Distribution</a></li>
- <li><a href="userguide.html#clients">Axis2 and clients</a></li>
+ <li><a href="userguide.html#clients">Axis2 and Clients</a></li>
</ul>
</li>
<li><a href="userguide-installingtesting.html#installingtesting">Installing
- and testing client code</a></li>
+ and Testing Client Code</a></li>
<li><a href="userguide-introtoservices.html#introservices">Introduction to
Services</a><br />
@@ -64,13 +64,13 @@
Comfortable with Available Options</strong></a></li>
<li><a
href="userguide-buildingservices.html#createscratch"><strong>Creating
- a service from scratch</strong></a></li>
+ a Service from Scratch</strong></a></li>
<li><a
href="userguide-buildingservices.html#deploypojo"><strong>Deploying
Plain Old Java Objects</strong></a></li>
<li><a
href="userguide-buildingservices.html#deployrun"><strong>Deploying
- and running an Axis2 service created from WSDL</strong></a></li>
+ and Running an Axis2 Service Created from WSDL</strong></a></li>
</ul>
</li>
<li><a href="userguide-samples.html">Samples</a></li>
@@ -79,36 +79,36 @@
<p><a name="getcomfortable"></a></p>
-<h2>Getting Comfortable with Available Options</h2>
+<h2>Getting Comfortable with the Available Options</h2>
<p>Axis2 provides a number of ways to create a service, such as:</p>
<ul>
- <li>Create a service and build it from scratch: In this case, you build
+ <li>Create a service and build it from scratch. In this case, you build
your service class to specifically access AXIOM OMElement objects, then
- create the services.xml file and package it up for deployment.</li>
+ create the services.xml file and package it for deployment.</li>
<li>Deploy Plain Old Java Objects (POJOs) as a service.</li>
- <li>Generate the service from WSDL: Just as you can generate clients with
- WSDL, you can generate the skeleton of a service.</li>
+ <li>Generate the service from WSDL. Just as you can generate clients with
+ WSDL, you can also generate the skeleton of a service.</li>
</ul>
<p>Let's look at these three options.</p>
<a name="createscratch"></a>
-<h2>Creating a Service From Scratch</h2>
+<h2>Creating a Service from Scratch</h2>
<p>Creating a service from scratch is not the most convenient way to do it,
but it does give you the most control. The process involves several steps.</p>
<p><b>The short story:</b></p>
<ol>
- <li>Create the service class, with each operation represented by a method
- that takes as its argument a org.apache.axiom.om.OMElement object. (An
- OMElement is how the AXIs2 Object Model (AXIOM) represents an XML
- element.)</li>
+ <li>Create the service class with each operation that is represented by a
+ method that takes an org.apache.axiom.om.OMElement object as its
+ argument. (An OMElement is how the AXIs2 Object Model (AXIOM) represents
+ an XML element.)</li>
<li>Create the service descriptor, services.xml, which defines the class to
be used by the service and the appropriate message receivers.</li>
<li>Create the .aar file, with the classes in their proper locations based
- on package and the services.xml file in the META-INF directory.</li>
+ on the package and the services.xml file in the META-INF directory.</li>
<li>Deploy the .aar file by using the <a href="webadminguide.html">Web
Administration application</a> or by copying it to the Axis2 services
directory.</li>
@@ -164,7 +164,7 @@
<p>Axis2 uses AXIOM, or the AXIs Object Model, a DOM (Document Object Model)
-like structure that is based on the StAX API ( Streaming API for XML).
-Methods that act as services must take as their argument an OMElement, which
+Methods that act as services must take an OMElement as their argument, which
represents the payload of the incoming SOAP message. (An OMElement is just
AXIOM's way of representing an XML element, like a DOM Element object.) In
this case, you're extracting the contents of the first child of the payload
@@ -195,7 +195,7 @@
</operation>
</service></pre>
-<p>This document defines the service, what it's called by the <a
+<p>This document defines the service, called by the <a
href="webadminguide.html">Web Administration Application</a>, and the class
used to serve requests. For each operation, it defines the appropriate
message receiver class.</p>
@@ -204,7 +204,8 @@
this case, that's the same directory that contains the org directory) and
place the services.xml file in it.</p>
-<p>Create the .aar file by typing: jar cvf SampleService.aar ./*</p>
+<p>Create the .aar file by typing: jar cvf SampleService.aar
+./*</p>
<p>Deploy the SampleService.aar file by using the <a
href="webadminguide.html">Web Administration application</a> or by copying it
@@ -271,13 +272,13 @@
<p>This class uses the same technique of sending and receiving OMElements,
but it's also important to note the use of the Options class. This class
enables you to determine properties such as the transport used for the return
-message -- the transport used for the outgoing message can be inferred from
-the URL of the destination -- and the SOAP version to use. In addition to
-providing setter and getter methods of specific properties that affect how
-the client interacts with the service, the Options class enables you to
-create inheritance relationships between Options objects, so that if a
-property is not found in the current Options object used, the client can
-check the parent Options object of the current Options object.</p>
+message (the transport used for the outgoing message can be inferred from the
+URL of the destination) and the SOAP version to use. In addition to providing
+setter and getter methods of specific properties that affect how the client
+interacts with the service, the Options class enables you to create
+inheritance relationships between Options objects. So if a property is not
+found in the current Options object used, the client can check the parent
+Options object of the current Options object.</p>
<p>Compile and run the above SampleClient.java. Make sure to have all axis2
libraries in your class path. If all has gone well, 'Hello, John' will be
@@ -315,8 +316,8 @@
}</pre>
-<p>Next, you'll need to tell Axis2 what class corresponds to what Web service
-calls. Do this by creating a file called services.xml and adding the
+<p>Next, you'll need to tell Axis2 what class corresponds with what Web
+service calls. Do this by creating a file called services.xml and adding the
following shown in Code Listing 12.</p>
<h3><b>Code Listing 12 - Creating services.xml</b></h3>
@@ -359,8 +360,8 @@
- SampleService.class</pre>
<p>Finally, deploy the service by copying the SampleService directory to the
-webapps/axis2/WEB-INF/services directory on the servlet engine. You can check to make
-sure that it's been properly deployed by checking <a
+webapps/axis2/WEB-INF/services directory on the servlet engine. You can check
+to make sure that it's been properly deployed by checking <a
href="http://<host>:<port>/axis2/services/listServices">http://<host>:<port>/axis2/services/listServices</a>.</p>
<a name="deployrun"></a>
@@ -369,13 +370,13 @@
<p>If you have a WSDL file, you can easily create and deploy a service based
on that description. For example, to create a service based on the same WSDL
file used in the <a href="userguide-creatingclients.html">clients section</a>
-of this document, you'd employ the following steps.</p>
+of this document, you will follow the steps below.</p>
<p><b>The short story:</b></p>
<ol>
- <li>If you haven't already, <a
- href="http://ws.apache.org/axis2/download/1_1/download.cgi#std-bin">download</a>
- the Axis2 standard distribution.</li>
+ <li><a
+ href="http://ws.apache.org/axis2/download/1_1/download.cgi#std-bin">Download</a>
+ the Axis2 standard distribution, if you have not done so already.</li>
<li>Generate the skeleton using the WSDL2Java utility, as in: <br />
<pre>java org.apache.axis2.wsdl.WSDL2Java -uri file:///C:/apps/axis2/samples/zSample/Axis2UserGuide.wsdl -p org.apache.axis2.axis2userguide -d adb -s -wv 1.1 -ss -sd -ssi</pre>
@@ -386,15 +387,15 @@
<li>Deploy the service by copying the build/lib/*.aar file to
<J2EE_HOME>/webapps/axis2/WEB-INF/services</li>
<li>Check http://<server>:<port>/axis2/services/listServices to
- make sure the service has been properly deployed</li>
+ make sure the service has been properly deployed.</li>
</ol>
<p><b>The long story:</b></p>
-<p>As was the case in generating clients, you will need the <a
+<p>As with generating clients, you will need the <a
href="http://ws.apache.org/axis2/download/1_1/download.cgi#std-bin">Axis2
Standard Distribution</a>, because the <a
-href="http://ws.apache.org/axis2/download/1_1/download.cgi#war">Axis2 War
+href="http://ws.apache.org/axis2/download/1_1/download.cgi#war">Axis2 WAR
Distribution</a> does not include the WSDL2Java utility. Once you've got it
downloaded and unpacked, make sure that you set the AXIS2_HOME variable to
point to the location in which you've unpacked it.</p>
@@ -414,27 +415,27 @@
<p>This statement tells the utility you want to create a service out of the
operations in the file Axis2UserGuide.wsdl, and that the Java classes
generated should be in the org.apache.axis2.axis2userguide package (-p). (You
-should see the appropriate directories created.) It also indicates that you
+can view the appropriate directories created.) It also indicates that you
want to use the Axis2 DataBinding Framework, or ADB (-d), to generate only
-synchronous, or blocking code (-s), and to generate server-side code (-ss) as
+synchronous or blocking code (-s), and to generate server-side code (-ss) as
opposed to a client, including the services.xml service descriptor file
-(-sd). It also specifies version 1.1 for the WSDL file (-wv).
-</p>
+(-sd). It also specifies version 1.1 for the WSDL file (-wv).</p>
-<p>At this point, you should see three new items in your chosen directory:
-the build.xml file, which includes instructions for Ant, the src directory,
-which includes all of the generated classes and stubs, the resources
-directory, which includes a regenerated version of the WSDL, and the
-services.xml file, which ultimately controls the service's behavior.</p>
+<p>At this point, you should see four new items in your chosen directory: the
+build.xml file, which includes instructions for Ant, the src directory, which
+includes all the generated classes and stubs, the resources directory, which
+includes a regenerated version of the WSDL, and the services.xml file, which
+ultimately controls the service's behavior.</p>
<p>You can compile the service at this point, but it doesn't actually do
anything yet. You can solve that problem by opening the
src\org\apache\axis2\axis2userguide\Axis2UserGuideServiceSkeleton.java file
and either editing the code in bold -- make sure you manage parameter numbers
--- or replacing all of the code with the following in Code Listing 15.</p>
+-- or replacing all the code with the following in Code Listing 15.</p>
<h3>Code Listing 15 - Compiling the Service</h3>
-<pre>/**
+
+<p><pre>/**
* Axis2UserGuideServiceSkeleton.java
*
* This file was auto-generated from WSDL
@@ -541,13 +542,14 @@
}
}</pre>
+</p>
-<p>As in the case of generating clients, all of these classes, such as
+<p>As with generating clients, all these classes, such as
MultipleParametersAddItemRequest and TwoWayOneParameterEchoResponse, are
generated by the utility, and can be found in the same directory as the
-skeleton file. They include methods such as setSuccessfulAdd(), which set the
-value of the content of an element in the response, and getItemName(), which
-retrieve the content of elements in the request.</p>
+skeleton file. They include methods such as setSuccessfulAdd(), which sets
+the value of the content of an element in the response, and getItemName(),
+which retrieves the content of elements in the request.</p>
<p>Save the file and compile it by typing: ant jar.server</p>
Modified: webservices/axis2/trunk/java/xdocs/1_1/userguide-codelisting5.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/userguide-codelisting5.html?view=diff&rev=517097&r1=517096&r2=517097
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/userguide-codelisting5.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/userguide-codelisting5.html Sun Mar 11 21:49:38 2007
@@ -8,7 +8,7 @@
</head>
<body>
-<h1>Code Listing 5 - Generating clients from the WSDL file</h1>
+<h1>Code Listing 5 - Generating Clients from the WSDL File</h1>
<pre><?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
xmlns:apachesoap="http://xml.apache.org/xml-soap"
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=517097&r1=517096&r2=517097
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/userguide.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/userguide.html Sun Mar 11 21:49:38 2007
@@ -10,15 +10,14 @@
<body xml:lang="en" lang="en">
<h1>Apache Axis2 User's Guide</h1>
-<p>This guide provides a starting place for users new to Apache Axis2. It
-also provides information for more experienced users, such as how to use
-Axis2 to create and deploy Web services as well as how to use WSDL to
-generate both clients and services.</p>
-For more experienced users of Apache Axis2, we would recommend you start with
-the <a href="adv-userguide.html">Advance User's Guide.</a> <a
-name="intro"></a>
+<p>This guide provides a starting place for users who are new to Apache
+Axis2. It also covers some advanced topics, such as how to use Axis2 to
+create and deploy Web services as well as how to use WSDL to generate both
+clients and services.</p>
+For experienced users of Apache Axis2, we recommend the <a
+href="adv-userguide.html">Advanced User's Guide.</a> <a name="intro"></a>
-<h1>- Introducing Axis2</h1>
+<h1>Introducing Axis2</h1>
<p>This section introduces Axis2 and its structure, including an explanation
of various directories/files included in the latest Axis2 <a
@@ -31,25 +30,25 @@
<ul>
<li><a href="userguide.html#whatis"><strong>What is
- Axis2</strong></a></li>
+ Axis2?</strong></a></li>
<li><a href="userguide.html#underhood"><strong>What's under the
hood?</strong></a></li>
<li><a href="userguide.html#handlessoap"><strong>How Axis2 handles SOAP
messages</strong></a></li>
<li><a href="userguide.html#distributions"><strong>Axis2
- distributions</strong></a></li>
+ Distributions</strong></a></li>
<li><a href="userguide.html#sbd"><strong>The Axis2 Standard Binary
Distribution</strong></a></li>
<li><a href="userguide.html#hierarchy"><strong>Axis2.war Directory
- hierarchy</strong></a></li>
+ Hierarchy</strong></a></li>
<li><a href="userguide.html#docs"><strong>Axis2 Documents
Distribution</strong></a></li>
<li><a href="userguide.html#clients"><strong>Axis2 and
- clients</strong></a></li>
+ Clients</strong></a></li>
</ul>
</li>
<li><a href="userguide-installingtesting.html#installingtesting">Installing
- and testing client code</a></li>
+ and Testing Client Code</a></li>
<li><a href="userguide-introtoservices.html#introservices">Introduction to
Services</a><br />
@@ -77,11 +76,11 @@
<li><a href="userguide-buildingservices.html#getcomfortable">Getting
Comfortable with Available Options</a></li>
<li><a href="userguide-buildingservices.html#createscratch">Creating a
- service from scratch</a></li>
+ Service from Scratch</a></li>
<li><a href="userguide-buildingservices.html#deploypojo">Deploying
Plain Old Java Objects</a></li>
<li><a href="userguide-buildingservices.html#deployrun">Deploying and
- running an Axis2 service created from WSDL</a></li>
+ Running an Axis2 Service Created from WSDL</a></li>
</ul>
</li>
<li><a href="userguide-samples.html">Samples</a></li>
@@ -94,8 +93,8 @@
<p>The Apache Axis2 project is a Java-based implementation of both the client
and server sides of the Web services equation. Designed to take advantage of
the lessons learned from Apache Axis 1.0, Apache Axis2 provides a complete
-object model and a modular architecture that makes its straight forward to
-add functionality and support for new Web services-related specifications and
+object model and a modular architecture that makes it easy to add
+functionality and support for new Web services-related specifications and
recommendations.</p>
<p>Axis2 enables you to easily perform the following tasks:</p>
@@ -103,7 +102,8 @@
<li>Send SOAP messages</li>
<li>Receive and process SOAP messages</li>
<li>Create a Web service out of a plain Java class</li>
- <li>Create implementation classes for both server and client using WSDL</li>
+ <li>Create implementation classes for both the server and client using
+ WSDL</li>
<li>Easily retrieve the WSDL for a service</li>
<li>Send and receive SOAP messages with attachments</li>
<li>Create or utilize a REST-based Web service</li>
@@ -139,8 +139,8 @@
href="userguide-introtoservices.html/">Introduction to Services</a>".) If the
system requires the use of WS* recommendations such as WS-Addressing or
WS-Security, the message may undergo additional processing before it leaves
-the sender. Once the message itself is ready, it is sent via a particular
-transport such as HTTP, JMS, and so on.</p>
+the sender. Once the message is ready, it is sent via a particular transport
+such as HTTP, JMS, and so on.</p>
<p>The message works its way over to the receiver, which takes in the message
via the transport listener. (In other words, if the application doesn't have
@@ -164,16 +164,16 @@
</p>
<p>On each end, you have an application designed to deal with the (sent or
-received) messages. In the middle, you have Axis2. Or rather, you CAN have
-Axis2. The value of Web services is that the sender and receiver (each of
-which can be either the server or the client) don't even have to be on the
-same platform, much less running the same application. But assuming that
-Axis2 is running on both sides, the process looks like this:</p>
+received) messages. In the middle, you have Axis2, or rather, you
+<em>can</em> have Axis2. The value of Web services is that the sender and
+receiver (each of which can be either the server or the client) don't even
+have to be on the same platform, much less running the same application.
+Assuming that Axis2 is running on both sides, the process looks like this:</p>
<ul>
<li>The sender creates the SOAP message.</li>
<li>Axis "handlers" perform any necessary actions on that message such as
encryption of WS-Security related messages.</li>
- <li>The Transport sender sends the message.</li>
+ <li>The transport sender sends the message.</li>
<li>On the receiving end, the transport listener detects the message.</li>
<li>The transport listener passes the message on to any handlers on the
receiving side.</li>
@@ -183,16 +183,16 @@
</ul>
<p>In Axis2, these actions are broken down into "phases", with several
-pre-defined phases such as the "pre-dispatch", "dispatch," and "message
-processing" being built into Axis2. Each phase is a collection of "handlers".
-Axis2 enables you to control what handlers go into which phases, and the
-order in which handlers are executed within phases. You can also add your own
-phases and handlers.</p>
+pre-defined phases, such as the "pre-dispatch", "dispatch," and "message
+processing", being built into Axis2. Each phase is a collection of
+"handlers". Axis2 enables you to control what handlers go into which phases,
+and the order in which the handlers are executed within the phases. You can
+also add your own phases and handlers.</p>
<p>Handlers come from "modules" that can be plugged into a running Axis2
system. These modules, such as Rampart, which provides an implementation of
WS-Security, and Sandesha, which provides an implementation of
-WS-ReliableMessaging, are the main extensibility mechanism in Axis2.</p>
+WS-ReliableMessaging, are the main extensibility mechanisms in Axis2.</p>
<a name="distributions"></a>
<h2>Axis2 Distributions</h2>
@@ -206,9 +206,9 @@
<p>If you're developing services and applications, you'll need the Axis2 <a
href="http://ws.apache.org/axis2/download/1_1/download.cgi#std-bin">Standard
-Binary Distribution</a>. The distribution includes all of the necessary *.jar
+Binary Distribution</a>. The distribution includes all the necessary *.jar
files, as well as a variety of scripts that ease development. It has the
-following structure:</p>
+following structure.</p>
<p><b>Code Listing 1: Axis2 Standard Binary Distribution</b></p>
<pre>bin
@@ -247,25 +247,25 @@
INSTALL.txt
release-notes.html</pre>
-<p>The bin directory includes a number of useful scripts, including axis2.bat
-(or axis2.sh), which enables you to easily execute a Java command without
-having to manually add all of the Axis2 jar files to the classpath,
-java2wsdl.bat (and .sh) and wsdl2java.bat (and .sh), which enables you to
+<p>The bin directory includes a number of useful scripts. They include
+axis2.bat (or axis2.sh), which enables you to easily execute a Java command
+without having to manually add all the Axis2 jar files to the classpath,
+java2wsdl.bat (and .sh) and wsdl2java.bat (and .sh), which enable you to
easily generate Java code from a WSDL file and vice versa, and
axis2server.bat (and sh), a simple Web server that enables you to build
Axis2's capability to send and receive messages into your own application.</p>
-<p>As expected, the lib directory includes all of the necessary jar files.
+<p>As expected, the lib directory includes all the necessary .jar files.
Services and modules are added to the repository directory. Axis2 comes with
a standard module implementing WS-Addressing, and you can add any other
-necessary modules such as Rampart to the repository/modules directory.</p>
+necessary module such as Rampart to the repository/modules directory.</p>
<p>conf directory includes the axis2.xml which is the global deployment
descriptor.</p>
-<p>Finally, the samples directory includes all of the sample code distributed
-with Axis2. You can find a list of the samples and their descriptions <a
-href="userguide-samples.html">here</a>.</p>
+<p>Finally, the samples directory includes all the sample code distributed
+with Axis2. See the list of <a href="userguide-samples.html">samples and
+their descriptions</a>.</p>
<a name="hierarchy"></a>
<h2>axis2.war Distribution Directory Hierarchy</h2>
@@ -302,22 +302,21 @@
href="webadminguide.html">Axis2 administration application</a>, through which
you can perform any needed actions such as adding services and engaging and
dis-engaging modules. The WEB-INF directory represents the actual Axis2
-application, including all of the *.jar files, any included modules, and even
+application, including all the *.jar files, any included modules, and even
the deployed services themselves.</p>
-<p>The classes directory holds any classes or properties files that are
-needed by Axis2 itself, such as log4j.properties. Any actual services to be
-handled by the system reside in the services directory in the form of an axis
-archive, or *.aar file. This file contains any classes related to the
-service, as well as the services.xml file, which controls any additional
-requirements, such as the definition of message senders and message
-receivers.</p>
-
-<p>But the main file in all this it is axis2.xml, which controls how the
-application deals with received messages. It defines message receivers and
-transport receivers, as well as defining transport senders and determining
-which modules are active. It also defines the order of phases, and the
-handlers to be executed within each phase.</p>
+<p>The classes directory holds any class or property files that are needed by
+Axis2 itself, such as log4j.properties. Any actual services to be handled by
+the system reside in the services directory in the form of an axis archive,
+or *.aar file. This file contains any classes related to the service, as well
+as the services.xml file, which controls any additional requirements, such as
+the definition of message senders and message receivers.</p>
+
+<p>The main file in all this is axis2.xml, which controls how the application
+deals with received messages. It defines message receivers and transport
+receivers, as well as defining transport senders and determining which
+modules are active. It also defines the order of phases, and the handlers to
+be executed within each phase.</p>
<p>You can control all of this information through the use of the Web
application, but if you restart the Axis2 application, these changes are lost
@@ -325,7 +324,7 @@
<p>Axis2 also provides a third distribution, the <a
href="http://ws.apache.org/axis2/download/1_1/download.cgi#src">source
-distribution</a>, which enables you to generate this war file yourself.</p>
+distribution</a>, which enables you to generate this .war file yourself.</p>
<a id="docs"></a>
<h2>Axis2 Documentation Distribution Directory Hierarchy</h2>
@@ -342,15 +341,14 @@
README.txt
release-notes.html</pre>
-<p>The javadocs directory includes all of the standard <a
+<p>The javadocs directory includes all the standard <a
href="../../javadocs/index.html">API documentation</a> for the Axis2 API,
-with more conversational documentation (like this document) in the xdocs
-directory.</p>
+with other documentation (like this document) in the xdocs directory.</p>
<a name="clients"></a>
<h2>Axis2 and Clients</h2>
-<p>Now that explains how Axis2 behaves as part of a Web application, but what
+<p>Now that explains how Axis2 behaves as part of a Web application. What
about a standalone client that is not part of a J2EE application? In that
case, a sender can use the Axis2 default properties, in other words, no
special handlers, and so on. But you also have the option to tell the client
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-cvs-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-cvs-help@ws.apache.org