You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by ch...@apache.org on 2005/06/07 17:14:49 UTC

cvs commit: ws-site/targets/axis2 ServiceArchiveToolReference.html installationguide.html team-list.html userguide.html

chinthaka    2005/06/07 08:14:49

  Modified:    targets/axis2 ServiceArchiveToolReference.html
                        installationguide.html team-list.html
                        userguide.html
  Log:
  Adding changed docs to Axis2 site
  
  Revision  Changes    Path
  1.2       +6 -4      ws-site/targets/axis2/ServiceArchiveToolReference.html
  
  Index: ServiceArchiveToolReference.html
  ===================================================================
  RCS file: /home/cvs/ws-site/targets/axis2/ServiceArchiveToolReference.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ServiceArchiveToolReference.html	7 Jun 2005 14:49:07 -0000	1.1
  +++ ServiceArchiveToolReference.html	7 Jun 2005 15:14:48 -0000	1.2
  @@ -5,13 +5,15 @@
                   	Last published: 07 June 2005
                     | Doc for M2</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis_2_0"><h5>Axis 2.0</h5><ul><li class="none"><a href="index.html">Home</a></li><li class="none"><a href="news.html">News</a></li><li class="expanded"><a href="svn.html">Get Invloved</a><ul><li class="none"><a href="overview.html">Overview</a></li><li class="none"><a href="svn.html">Setting Up</a></li><li class="none"><a href="guidelines.html">Guide Lines</a></li><li class="none"><a href="refLib.html">Reference Library</a></li><li class="none"><a href="mail-lists.html">Mailing Lists</a></li><li class="none"><a href="siteHowTo.html">How to build site</a></li></ul></li><li class="expanded"><a href="">References</a><ul><li class="none"><a href="docs.html">Documentation</a></li><li class="none"><a href="http://wiki.apache.org/ws/FrontPage/Axis2" class="externalLink" title="External Link">Wiki</a></li><li class="none"><a href="Axis2ArchitectureGuide.html">Architecture Guide</a></li><li class="none"><a href="userguide.html">User Guide</a></li><li class="none"><a href="installationguide.html">Installation Guide</a></li><li class="none"><a href="webadminguide.html">Web Administration Guide</a></li><li class="none"><a href="OMTutorial.html">AXIOM Tutorial</a></li><li class="none"><a href="CodegenToolReference.html">Code Generation Tutorial</a></li><li class="none"><a href="m1.html">M1 Documents</a></li></ul></li><li class="expanded"><a href="">Downloads</a><ul><li class="none"><a href="releases.html">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis/trunk/?root=Apache-SVN" class="externalLink" title="External Link">Source Code</a></li><li class="none"><a href="axis2tools.html">Tools</a></li></ul></li><li class="expanded"><a href="">Modules</a><ul><li class="none"><a href="multiproject/axis2-core/index.html">Core</a></li><li class="none"><a href="multiproject/axis2-xml/index.html">XML</a></li><li class="none"><a href="multiproject/axis2-wsdl/index.html">WSDL</a></li><li class="none"><a href="multiproject/axis2-tools/index.html">Tools</a></li><li class="none"><a href="multiproject/axis2-samples/index.html">Samples</a></li></ul></li><li class="expanded"><a href="">Project Information</a><ul><li class="none"><a href="mail-lists.html">Mailing Lists</a></li><li class="none"><a href="team-list.html">Project Team</a></li><li class="none"><a href="issue-tracking.html">Issue Tracking</a></li></ul></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="./images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="Service_Archive_Wizard_-_Eclipse_Plug-in"></a><h2>Service Archive Wizard - Eclipse Plug-in</h2><p>Axis2 comes with a simple service archiver tool. This tool provides easy to use functionality to develop a axis archive or an "aar" file or a "jar" file that can be deployed as a web service to the Axis2. This tool is in the form of 
   an Eclipse plug-in and can be downloaded from the downloads section. The 
  -following sections describe how the tool can be used.</p><div class="subsection"><a name="Installation"></a><h3>Installation</h3><p>Download the binary version of the plug-in and extract the content of the zip 
  +following sections describe how the tool can be used.</p><div class="subsection"><a name="Installation"></a><h3>Installation</h3><p>
  +Download the binary version of the plug-in and extract the content of the zip 
   file into the Eclipse installation folder. (The plug-in will actually go into 
  -the plugins directory in the Eclipse installation root). Restart Eclipse to set 
  -the plug-in automatically.</p></div><div class="subsection"><a name="Operation"></a><h3>Operation</h3><p>If the plug-in is properly installed you should see a new wizard under the 
  +the plugins directory in the Eclipse installation root). Restarting Eclipse will set 
  +the plug-in automatically.
  +</p></div><div class="subsection"><a name="Operation"></a><h3>Operation</h3><p>If the plug-in is properly installed you should see a new wizard under the 
   "New" section.(use the File -&gt; New -&gt; Other or Ctrl + N ) </p><p>
   <img border="0" src="images/tools/ServiceWizardSelection.JPG" width="500" height="500" alt=""></img></p><p>Selecting the wizard and pressing the next button will start the code 
  -generator wizard. Following is the first wizard page.</p><p><img border="0" src="images/tools/ServicePage1.JPG" width="500" height="500" alt=""></img></p><p>Once the class file location is given (which should be a folder in the file 
  +generator wizard. Following is the first wizard page.</p><p><img border="0" src="images/tools/ServicePage1.JPG" width="500" height="500" alt=""></img></p><p>Once the class file folder� is given (which should be a folder in the file 
   system) the next button will be enabled. Page 2 of the wizard requires you to 
   locate the server.xml</p><p><img border="0" src="images/tools/ServicePage2.JPG" width="500" height="500" alt=""></img></p><p>Note that the automatic generation of the service.xml is disabled for this 
   release. After the service.xml is located you can point to the output location 
  
  
  
  1.2       +14 -15    ws-site/targets/axis2/installationguide.html
  
  Index: installationguide.html
  ===================================================================
  RCS file: /home/cvs/ws-site/targets/axis2/installationguide.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- installationguide.html	7 Jun 2005 14:49:07 -0000	1.1
  +++ installationguide.html	7 Jun 2005 15:14:48 -0000	1.2
  @@ -6,19 +6,19 @@
                     | Doc for M2</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis_2_0"><h5>Axis 2.0</h5><ul><li class="none"><a href="index.html">Home</a></li><li class="none"><a href="news.html">News</a></li><li class="expanded"><a href="svn.html">Get Invloved</a><ul><li class="none"><a href="overview.html">Overview</a></li><li class="none"><a href="svn.html">Setting Up</a></li><li class="none"><a href="guidelines.html">Guide Lines</a></li><li class="none"><a href="refLib.html">Reference Library</a></li><li class="none"><a href="mail-lists.html">Mailing Lists</a></li><li class="none"><a href="siteHowTo.html">How to build site</a></li></ul></li><li class="expanded"><a href="">References</a><ul><li class="none"><a href="docs.html">Documentation</a></li><li class="none"><a href="http://wiki.apache.org/ws/FrontPage/Axis2" class="externalLink" title="External Link">Wiki</a></li><li class="none"><a href="Axis2ArchitectureGuide.html">Architecture Guide</a></li><li class="none"><a href="userguide.html">User Guide</a></li><li class="none"><a href="installationguide.html">Installation Guide</a></li><li class="none"><a href="webadminguide.html">Web Administration Guide</a></li><li class="none"><a href="OMTutorial.html">AXIOM Tutorial</a></li><li class="none"><a href="CodegenToolReference.html">Code Generation Tutorial</a></li><li class="none"><a href="m1.html">M1 Documents</a></li></ul></li><li class="expanded"><a href="">Downloads</a><ul><li class="none"><a href="releases.html">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis/trunk/?root=Apache-SVN" class="externalLink" title="External Link">Source Code</a></li><li class="none"><a href="axis2tools.html">Tools</a></li></ul></li><li class="expanded"><a href="">Modules</a><ul><li class="none"><a href="multiproject/axis2-core/index.html">Core</a></li><li class="none"><a href="multiproject/axis2-xml/index.html">XML</a></li><li class="none"><a href="multiproject/axis2-wsdl/index.html">WSDL</a></li><li class="none"><a href="multiproject/axis2-tools/index.html">Tools</a></li><li class="none"><a href="multiproject/axis2-samples/index.html">Samples</a></li></ul></li><li class="expanded"><a href="">Project Information</a><ul><li class="none"><a href="mail-lists.html">Mailing Lists</a></li><li class="none"><a href="team-list.html">Project Team</a></li><li class="none"><a href="issue-tracking.html">Issue Tracking</a></li></ul></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="./images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="Introduction"></a><h2>Introduction</h2><p>Axis 2.0 can be downloaded as a <a href="releases.html">zipped binary </a> or the <a href="cvs-usage.html">source </a>.
   This section describes how Axis2 can be installed either as a
   standalone server or as part of a J2EE compliant servlet container. </p></div><div class="section"><a name="Prerequisites"></a><h2>Prerequisites</h2><p>Axis2 requires the Java Runtime Environment to be properly
  -installed. Axis is developed to be run on JRE 1.4 and upwards but it
  +installed. Axis2 is developed to be run on JRE 1.4 and upwards but it
   has not been fully tested with the latest JRE 1.5. Hence it is safe to
  -run Axis with Java 1.4. If the JRE is not already in place it must be
  +run Axis2 with Java 1.4. If the JRE is not already in place it must be
   installed to proceed further. For instructions on setting up the JRE in
   different operating systems, please visit <a href="http://java.sun.com/" class="externalLink" title="External Link">http://java.sun.com </a>. </p><p>All the required jars are shipped with the binary distribution and
   if the source distribution is used, running the maven build will
   automatically download the required jars for you. </p><p>Following sections describe how each type of distribution needs to
   be installed. Since the process with the source distribution is similar
   to the binary distribution after building, the first section explains
  -the process of building Axis from source. If you have the binary
  +the process of building Axis2 from source. If you have the binary
   distribution you can skip the build sections and directly go to the
   binary installation section. </p></div><div class="section"><a name="Building_Axis2_from_source"></a><h2>Building Axis2 from source</h2><div class="subsection"><a name="Setting_up_the_Environment_and_the_tools"></a><h3>Setting up the Environment and the tools</h3><p>The Axis2 build is based on <a href="http://maven.apache.org/" class="externalLink" title="External Link">Maven </a>.
  -Hence the prerequisite to build Axis2 from source is to have Maven
  +Hence the only prerequisite to build Axis2 from source distribution is to have Maven
   installed. Even though extensive instruction guides are available at
   the Maven site, this guide also contains the easiest path for quick
   environment setting. Advanced users who wish to know more about Maven
  @@ -29,20 +29,19 @@
   version in the command prompt. </p><p align="center">
   <img alt="clip_image002 (15K)" src="images/clip_image002.jpg" height="211" width="477"></img>
   </p><p>� </p><p>
  -For Linux users the tar ball or the zip archive is the best
  -options. (Unfortunately there is no rpm as such that can be easily
  -installed) Once the archive is downloaded expand it to a directory of
  +For Unix/Linux users the tar ball or the zip archive is the best
  +option. Once the archive is downloaded expand it to a directory of
   choice and set the environment variable MAVEN_HOME and add
   MAVEN_HOME/bin to the path as well. More instructions for installing
  -Maven in UNIX based operating systems can be found <a href="http://maven.apache.org/start/install.html" class="externalLink" title="External Link">here </a>. </p><p>Once maven is properly installed it's all that is needed to start building Axis2. </p></div><div class="subsection"><a name="The_Axis_source_distribution"></a><h3>The Axis source distribution</h3><p>The <a href="releases.html">source distribution </a> is available as
  -a zipped archive or a tar ball. All the necessary build scripts are
  +Maven in Unix based operating systems can be found <a href="http://maven.apache.org/start/install.html" class="externalLink" title="External Link">here </a>. </p><p>Once maven is properly installed it's all that is needed to start building Axis2. </p></div><div class="subsection"><a name="The_Axis2_source_distribution"></a><h3>The Axis2 source distribution</h3><p>The <a href="releases.html">source distribution </a> is available as
  +a zipped archive. All the necessary build scripts are
   included with the source distribution. Once the source archive is
   expanded into a directory of choice, moving to the particular directory
  -and typing maven will build the axis jar file. </p><p align="center"><img alt="clip_image004 (43K)" src="images/maven.jpg" height="338" width="669"></img></p><p>Once the command completes, the binaries (jar files in this case) can be found at a newly created target directory. </p><p><strong>Note  For the first Maven build (if the maven repository is
  +and running maven command will build the Axis2 jar file. </p><p align="center"><img alt="clip_image004 (43K)" src="images/maven.jpg" height="338" width="669"></img></p><p>Once the command completes, the binaries (jar files in this case) can be found at a newly created "target" directory. </p><p><strong>Note  For the first Maven build (if the maven repository is
   not built first) it will take a while since required jars need to be
   downloaded. However this is a once only process and will not affect any
   successive builds. </strong></p><p><strong> </strong>The default maven build will however build only
  -the Axis2 jar file. To obtain a WAR (Web Archive), maven war command
  +the Axis2 jar file. To obtain a WAR (Web Archive), "maven war" command
   should be issued. This will create a complete WAR with the name
   axis2.war inside the target directory. </p><p>Once this build step is complete, the binaries are ready to be deployed. </p></div></div><div class="section"><a name="Installing_Axis2_in_a_Servlet_container"></a><h2>Installing Axis2 in a Servlet container</h2><p>Installation of the WAR is quite simple. It's a matter of dropping
   the war in the webapps folders and most servlet containers will
  @@ -57,9 +56,9 @@
   install properly or some essential jars are missing. At such a situation the 
   documentation of the particular servlet container should be consulted to find 
   the problem. The following page is a successful validation. Note the statement 
  -core axis libraries are present.
  +core Axis2 libraries are present.
   </p><p align="center"><strong><img src="images/happyaxis.jpg" alt=""></img></strong></p><p>
  -The axis web application also provides an interface to upload services. 
  +The Axis2 web application also provides an interface to upload services. 
   Once a service is created according to the service specification as described in 
   userguide that jar file can be uploaded using the upload page.
   </p><p align="center"><strong><img src="images/clip_image010.jpg" alt=""></img></strong></p><p>The uploaded jar files will be stored in the default service
  @@ -71,6 +70,6 @@
   installed without the container being restarted. </p><p>To check the successful installation of a service <strong><em>available services link </em></strong>
   is provided. The services and the operations of successfully installed
   services will be displayed in the available services page.</p><p align="center"><strong><img src="images/clip_image012.jpg" alt=""></img></strong></p><p>If the service has deployment time error it will listed out those services as faulty services. 
  -And If you click on the link it will show your the deployment fault</p><p align="center"><strong><img src="images/faultService.jpg" alt=""></img></strong></p><p>Deployment time error message</p><p align="center"><strong><img src="images/faultmsg.jpg" alt=""></img></strong></p><p>� </p><p>� </p><p>Axis2 Administration  is all about configuring axis2 at the run time and
  +And If you click on the link it will show your the deployment fault</p><p align="center"><strong><img src="images/faultService.jpg" alt=""></img></strong></p><p>Deployment time error message</p><p align="center"><strong><img src="images/faultmsg.jpg" alt=""></img></strong></p><p>� </p><p>� </p><p>Axis2 Administration  is all about configuring Axis2 at the run time and
   the configuration will be transient , and more descriptions are avilable in 
  -axis2 admin web module guide</p></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">� 2004-2005, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
  \ No newline at end of file
  +<a href="webadminguide.html">Axis2 admin web guide</a></p></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">� 2004-2005, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
  \ No newline at end of file
  
  
  
  1.5       +7 -5      ws-site/targets/axis2/team-list.html
  
  Index: team-list.html
  ===================================================================
  RCS file: /home/cvs/ws-site/targets/axis2/team-list.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- team-list.html	7 Jun 2005 14:49:07 -0000	1.4
  +++ team-list.html	7 Jun 2005 15:14:48 -0000	1.5
  @@ -64,8 +64,8 @@
                       </td><td></td><td><span id="developer-ashu">Unknown</span></td></tr>
                   <tr class="b"><td>Jayachandra Sekhara Rao Sunkara</td><td><a name="jaya"></a>jaya</td><td><a href="mailto:jayachandra@gmail.com">jayachandra@gmail.com</a></td><td>Computer Associates</td><td>
                       </td><td></td><td><span id="developer-jaya">Unknown</span></td></tr>
  -                <tr class="a"><td>Thilina Gunarathne</td><td><a name="yhilina"></a>yhilina</td><td><a href="mailto:thilina@opensource.lk">thilina@opensource.lk</a></td><td>Lanka Software Foundation / Virtusa</td><td>
  -                    </td><td></td><td><span id="developer-yhilina">Unknown</span></td></tr>
  +                <tr class="a"><td>Thilina Gunarathne</td><td><a name="thilina"></a>thilina</td><td><a href="mailto:thilina@opensource.lk">thilina@opensource.lk</a></td><td>Lanka Software Foundation / Virtusa</td><td>
  +                    </td><td></td><td><span id="developer-thilina">Unknown</span></td></tr>
                   </tbody></table></div><div class="subsection"><a name="Contributors"></a><h3>Contributors</h3><p>
           The following additional people have contributed to this project
           through the way of suggestions, patches or documentation.
  @@ -78,10 +78,12 @@
                       </td></tr>
                   <tr class="a"><td>Chamil Thanthrimudalige</td><td><a href="mailto:chamil@opensource.lk">chamil@opensource.lk</a></td><td>Lanka Software Foundation</td><td>
                       </td></tr>
  -                <tr class="b"><td>Nadana Gunarathna</td><td><a href="mailto:nadana@opensource.lk">nadana@opensource.lk</a></td><td>Lanka Software Foundation</td><td>
  +                <tr class="b"><td>Ruchith Fernando</td><td><a href="mailto:ruchithf@apache.lk">ruchithf@apache.lk</a></td><td>Lanka Software Foundation</td><td>
                       </td></tr>
  -                <tr class="a"><td>Saminda Abeyruwan</td><td><a href="mailto:saminda@opensource.lk">saminda@opensource.lk</a></td><td>Lanka Software Foundation</td><td>
  +                <tr class="a"><td>Nadana Gunarathna</td><td><a href="mailto:nadana@opensource.lk">nadana@opensource.lk</a></td><td>Lanka Software Foundation</td><td>
                       </td></tr>
  -                <tr class="b"><td>Gayan Asanka</td><td><a href="mailto:gayan@opensource.lk">gayan@opensource.lk</a></td><td>Lanka Software Foundation</td><td>
  +                <tr class="b"><td>Saminda Abeyruwan</td><td><a href="mailto:saminda@opensource.lk">saminda@opensource.lk</a></td><td>Lanka Software Foundation</td><td>
  +                    </td></tr>
  +                <tr class="a"><td>Gayan Asanka</td><td><a href="mailto:gayan@opensource.lk">gayan@opensource.lk</a></td><td>Lanka Software Foundation</td><td>
                       </td></tr>
                   </tbody></table></div></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">� 2004-2005, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
  \ No newline at end of file
  
  
  
  1.5       +72 -39    ws-site/targets/axis2/userguide.html
  
  Index: userguide.html
  ===================================================================
  RCS file: /home/cvs/ws-site/targets/axis2/userguide.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- userguide.html	7 Jun 2005 14:49:07 -0000	1.4
  +++ userguide.html	7 Jun 2005 15:14:48 -0000	1.5
  @@ -17,7 +17,7 @@
     <li><strong>WSDL support.</strong> Axis 2.0 supports the <a href="http://www.w3.org/TR/wsdl" class="externalLink" title="External Link">Web Service Description Language </a>, version 1.1 and 2.0, which allows you to easily build stubs to access remote services, and also to automatically export machine-readable descriptions of your deployed services from Axis. </li>
   </ul><p>We hope you enjoy using Axis. Please note that this is an open-source effort - if you feel the code could use some new features or fixes, please get involved and lend a hand! The Axis developer community welcomes your participation . </p><p>Let us know what you think! </p><p>Please send feedback about the package to " <a href="mailto:axis-user@ws.apache.org">axis-user@ws.apache.org </a>" and make sure to prefix the subject of the mail with [Axis2]. </p></div><div class="subsection"><a name="What_s_in_this_release_"></a><h3>What's in this release?</h3><p>This release includes the following features:</p><ul>
     <li>AXIOM, a SOAP specific streaming XML infoset model for SOAP 1.1/1.2 Messages</li>
  -  <li>Modules, mechnisum to extend the SOAP Processing Model</li>
  +  <li>Modules, mechanism to extend the SOAP Processing Model</li>
     <li>Support for WS-Addressing</li>
     <li>Client API</li>
     <li>Support for One-Way Messaging</li>
  @@ -26,7 +26,7 @@
           <li>Synchronous, Using a two way transport</li>
           <li>Asynchronous, Using a two way transport</li>
           <li>Synchronous, Using a one way transport</li>
  -        <li>Aynchronous, Using a two way transport</li>
  +        <li>Asynchronous, Using a one way transport</li>
         </ol>
     </li>
     <li>Hot deployment of Web Services and Module deployment based on the archived modules </li>
  @@ -55,30 +55,39 @@
   user guide samples are located at the <b> <span class="style9">
   <font color="#000000">"samples/userguide/src"</font></span></b> directory 
   of the binary distribution. So.. let's  explore the samples.</p><p>Note: Please note that the rest of this user guide assumes that the user has downloaded the binary distribution of Axis2. If you have already downloaded the source tree of Axis2 then please create the binary distribution by simply using the maven command <strong>maven dist-bin </strong>This will create the "axis2-M2-bin.zip" and "axis2-M2-bin.tar"  in the "target/dist" directory. Extract the zip or the tar ball to any 
  -directory in your machine and for the explanations purposes we will name this as "Axis2Home". </p></div><div class="subsection"><a name="Web_Services_Using_Axis2"></a><h3>Web Services Using Axis2</h3><p>Before starting, please check wither you have deployed the "axis2.war" in your servlet container and it is working 
  +directory in your machine and for the explanations purposes we will name this 
  +directory as "Axis2Home". </p></div><div class="subsection"><a name="Web_Services_Using_Axis2"></a><h3>Web Services Using Axis2</h3><p>Before starting, please check whether you have deployed the "axis2.war" in your servlet container and it is working 
   properly. (See <a href="installationguide.htm">Installation Guide</a>)</p></div><div class="subsection"><a name="MyService"></a><h3>MyService</h3><p>First let's see how we can write a simple Web Service (MyService) and deploy it. For this purpose we will create a Web Service with two operations as follows.</p>
  -    <div class="source"><pre><pre>//IN-ONLY operation, just accepts the OMElement and do some processing.
  -public void ping(OMElement element){} 
  -//IN-OUT operation, accepts an OMElement and responds with another OMElement after processing.
  -public OMElement echo(OMElement element){}</pre></pre></div>
  -  <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 are doing. So let's see how we can write the deployment descriptors for the service and deploy it.</p><p>Axis2 uses "service.xml" to keep configurations for a Web Service. Each Web Service deployed 
  +    <div class="source"><pre><pre>public void ping(OMElement element){} //IN-ONLY operation, just accepts the OMElement and do some processing.
  +public OMElement echo(OMElement element){}//IN-OUT operation, accepts an OMElement and responds with another OMElement after processing.</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 are doing. So let's see how we can write the deployment descriptors for the service and deploy it.</p>
  +<p>Axis2 uses "service.xml" to keep configurations for a Web Service. Each Web Service deployed 
   in Axis2 needs a "service.xml" containing the configurations. "service.xml" for MyService will be as follows; we will see what each parameter means later.</p>
  -    <div class="source"><pre><pre>&lt;service name="MyService"&gt;<br></br>    &lt;description&gt;<br></br>        This is a sample Web Service with two operations, echo and ping.<br></br>    &lt;/description&gt;<br></br>    &lt;parameter name="ServiceClass" locked="xsd:false"&gt;userguide.example1.MyService&lt;/parameter&gt;<br></br>    &lt;operation name="echo"&gt;<br></br>        &lt;messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageRecevier"/&gt;<br></br>    &lt;/operation&gt;<br></br>     &lt;operation name="ping"&gt;<br></br>        &lt;messageReceiver class="org.apache.axis.receivers.RawXMLINOnlyMessageRecevier"/&gt;<br></br>    &lt;/operation&gt;<br></br> &lt;/service&gt;</pre></pre></div>
  -  <p>As it can be seen, first line of the "service.xml" gives the name of the Web Service. This is used in the URL to the service as the service name. Next comes the description and the service class. The next two xml tags describe the operations that are available in this service with respective message receivers. For the "echo" operation we have used a <strong>RawXMLINOutMessageRecevier</strong> since it is an 
  -IN-OUT operation. For IN-ONLY operation, "ping" we have used <strong>RawXMLINOnlyMessageRecevier</strong> as the message receiver. </p><p>Axis2 use ".aar" (Axis Archive) file as the deployment package for Web Services. So, 
  +
  +    <div class="source"><pre><pre>&lt;service name="MyService"&gt;<br></br>    &lt;description&gt;<br></br>        This is a sample Web Service with two operations, echo and ping.<br></br>    &lt;/description&gt;<br></br>    &lt;parameter name="ServiceClass" locked="xsd:false"&gt;userguide.example1.MyService&lt;/parameter&gt;<br></br>    &lt;operation name="echo"&gt;<br></br>        &lt;messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageRecevier"/&gt;<br></br>    &lt;/operation&gt;<br></br>     &lt;operation name="ping"&gt;<br></br>        &lt;messageReceiver class="org.apache.axis.receivers.RawXMLINOnlyMessageRecevier"/&gt;<br></br>    &lt;/operation&gt;<br></br> &lt;/service&gt;</pre>
  +<p>As it can be seen, first line of the "service.xml" gives the name of the Web Service. This is used in the URL to the service as the service name. Next comes the description and the service class. The next two xml tags describe the operations that are available in this service with respective message receivers. For the "echo" operation we have used a <strong>RawXMLINOutMessageRecevier</strong> since it is an 
  +IN-OUT operation. For IN-ONLY operation, "ping" we have used <strong>RawXMLINOnlyMessageRecevier</strong> as the message receiver. </p>
  +<p>Axis2 use ".aar" (Axis Archive) file as the deployment package for Web Services. So, 
   for MyService we will use "MyService.aar" with the "service.xml" packaged 
  -in the META-INF as shown in the following picture.</p><p><img src="images/userguide/ServiceItems.jpg" width="176" height="91" alt=""></img></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. 
  +in the META-INF as shown in the following picture.</p>
  +<p><img src="images/userguide/ServiceItems.jpg" width="176" height="91" alt=""></img></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, 
  -and let's use it.. </p><p>Deploying the service� is just a matter of 
  +and let's use it.. </p>
  +<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 and hence please copy the "MyService.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 "List Available services" in the page http://localhost:8080/axis2/index.jsp and see whether the MyService is deployed properly. If 
  -everything is ok, you will see the following out put.. </p><p align="center"><img src="images/userguide/MyServiceDeployed.jpg" width="797" height="654" alt=""></img> </p><p>If you can see the above out put then you have successfully deployed MyService on Axis2. Now let's see how we can write Web Service client to use this services. 
  +everything is ok, you will see the following out put.. </p>
  +<p align="center"><img src="images/userguide/MyServiceDeployed.jpg" width="797" height="654" alt=""></img> </p>
  +<p>If you can see the above output then you have successfully deployed MyService on Axis2. Now let's see how we can write Web Service client to use this services. 
   Axis2 provides an easy way to deploy a Web Services using, index.jsp. (See the 
  -installation guide for more information on this)</p></div><div class="subsection"><a name="Web_Service_Clients_Using_Axis2"></a><h3>Web Service Clients Using Axis2</h3><p> Web services can be used to provide wide range of functionality to the users 
  +installation guide for more information on this)</p>
  +<h2> Web Service Clients Using Axis2 </h2>
  +<p> Web services can be used to provide wide range of functionality to the users 
   ranging from simple less time consuming� operations such as "getStockQuote"� 
  -to time consuming business data processing. When we utilize (write client 
  +to time consuming business services. When we utilize (invoke using client 
   applications) these Web Service we cannot use some simple generic invocation 
   paradigm that suites all the timing complexities involved in the service 
   operations. For example, if we use a single transport channel (such as HTTP) to 
  @@ -87,10 +96,12 @@
   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 come in to play when we 
  +various other consequences such as One-Way transports that come in to play when we 
   need to invoke Web Services. So let's try to analyze some common service 
  -invocation paradigms.</p><p> Many web service engines provide the users with a Blocking and Non-Blocking 
  -client APIs. </p><ul>
  +invocation paradigms.</p>
  +<p> Many web service engines provide the users with a Blocking and Non-Blocking 
  +client APIs. </p>
  +<ul>
     <li><b>Blocking API</b> -Once the service invocation is called, the client 
     application hangs and gets the control back only when the operation completes 
     and the client receives a response or a fault. This is the simplest way of 
  @@ -101,21 +112,29 @@
     This approach provides the flexibility to the client application to invoke 
     several Web Services simultaneously with out blocking on the operation already 
     invoked.</li>
  -</ul><p> Both these mechanism works in the API level and let's name the� 
  +</ul>
  +<p> Both these mechanism works in the API level and let's name the� 
   asynchronous behavior that we can get using the Non-Blocking API as <b>API Level 
  -Asynchrony.</b></p><p> Both these mechanisms use single transport connection to send the request 
  +Asynchrony.</b></p>
  +<p> Both these mechanisms use single transport connection to send the request 
   and to receive the response. They severely lags the capability of using two 
   transport connections for the request and the response (either One-Way of 
   Two-Way). So both of these mechanisms fail to address the problem of long 
   running transactions (the transport connection may times-out before the 
   operation completes). A possible solution would be to use two separate transport 
   connections for request and response. The asynchronous behavior that we gain 
  -using can be called, <b>Transport Level Asynchrony</b>.</p><p> By combining the two we can obtain four different invocation patterns for web 
  -services as shown in the following table.</p><table class="bodyTable"><tr class="a"><td width="33%" height="19">API (Blocking/Non-Blocking)</td><td width="33%" height="19">�Dual Transports (Yes/No)</td><td width="33%" height="19">Description</td></tr><tr class="b"><td width="33%" height="19">Blocking</td><td width="33%" height="19">No</td><td width="33%" height="19">Simplest and the familiar invocation pattern</td></tr><tr class="a"><td width="33%" height="19">Non-Blocking</td><td width="33%" height="19">No</td><td width="33%" height="19">Using callbacks or polling</td></tr><tr class="b"><td width="33%" height="19">Blocking</td><td width="33%" height="19">Yes</td><td width="33%" height="19">This is useful when the service operation is 
  -    IN-OUT in nature but the transport used is One-Way (e.g. SMTP)</td></tr><tr class="a"><td width="33%" height="19">Non-Blocking</td><td width="33%" height="19">Yes</td><td width="33%" height="19">This is can be used to gain the maximum 
  +using can be called, <b>Transport Level Asynchrony</b>.</p>
  +<p> By combining the two we can obtain four different invocation patterns for web 
  +services as shown in the following table.</p>
  +<table class="bodyTable"><tr class="b"><td width="33%" height="19">API (Blocking/Non-Blocking)</td><td width="33%" height="19">�Dual Transports (Yes/No)</td><td width="33%" height="19">Description</td></tr><tr class="a"><td width="33%" height="19">Blocking</td><td width="33%" height="19">No</td><td width="33%" height="19">Simplest and the familiar invocation pattern</td></tr><tr class="b"><td width="33%" height="19">Non-Blocking</td><td width="33%" height="19">No</td><td width="33%" height="19">Using callbacks or polling</td></tr><tr class="a"><td width="33%" height="19">Blocking</td><td width="33%" height="19">Yes</td><td width="33%" height="19">This is useful when the service operation is 
  +    IN-OUT in nature but the transport used is One-Way (e.g. SMTP)</td></tr><tr class="b"><td width="33%" height="19">Non-Blocking</td><td width="33%" height="19">Yes</td><td width="33%" height="19">This is can be used to gain the maximum 
       asynchronous behavior. No blocking in the API level and also in the 
  -    transport level</td></tr></table><p><b>Axis2 provides the user with all these possibilities to invoke Web 
  -Services� and let's see how to use them Now!</b></p></div><div class="subsection"><a name="EchoBlockingClient"></a><h3>EchoBlockingClient</h3><p>Axis2 provides the user with several invocation patterns for Web Services, ranging from pure blocking single channel invocations to a non-blocking dual channel invocations. First let's see how we can write a client to invoke "echo" operation of "MyService" using the simplest good old blocking invocation. The client code that you need to write will be as follows.</p>
  +    transport level</td></tr></table>
  +<p><b>Axis2 provides the user with all these possibilities to invoke Web 
  +Services� and let's see how to use them Now!</b></p>
  +<h3>EchoBlockingClient</h3>
  +<p>Axis2 provides the user with several invocation patterns for Web Services, ranging from pure blocking single channel invocations to a non-blocking dual channel invocations. First let's see how we can write a client to invoke "echo" operation of "MyService" using the simplest good old blocking invocation. The client code that you need to write will be as follows.</p>
  +
       <div class="source"><pre><pre>  try {
               OMElement payload = ClientUtil.getEchoOMElement();
               <span class="style10">Call call = new Call();
  @@ -136,11 +155,15 @@
               e.printStackTrace();
           }
   }
  -</pre></pre></div>
  -  <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 
  +</pre>
  +<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><p><img src="images/userguide/TestClient.jpg" width="951" height="132" alt=""></img></p></div><div class="subsection"><a name="PingClient"></a><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. 
  +.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>
  +<p><img src="images/userguide/TestClient.jpg" width="951" height="132" alt=""></img></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. 
   The client code will be as follows.</p>
  +
       <div class="source"><pre><pre> try {
          OMElement payload = ClientUtil.getPingOMElement();
   
  @@ -152,12 +175,18 @@
        } catch (AxisFault axisFault) {
               axisFault.printStackTrace();
        }
  -</pre></pre></div>
  -  <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 
  +</pre>
  + 
  +<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><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></div><div class="subsection"><a name="EchoNonBlockingClient"></a><h3>EchoNonBlockingClient</h3><p>In the EchoBlockingClient once the "call.invokeBlocking("echo", payload);" is called, the client is blocked till the operation is completed. This behavior is not 
  -desirable when there are many Web Service invocations to be done in a single client application. A solution, would be to use a Non-Blocking API to invoke web services. Axis2 provides a callback based non-blocking API for users. </p><p>A sample client for this can be found under "Axis2Home/samples/userguide/src/userguide/clients" with the name EchoNonBlockingClient. If we consider the changes that the user may have to do with respect to the "EchoBlockingClient" that we have already seen, it will be as follows.</p>
  +test this client using the "TestPingClient.bat" that is in "Axis2Home/samples/userguide/src/userguide/clients/bin".</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>
  +<p>In the EchoBlockingClient once the "call.invokeBlocking("echo", payload);" is called, the client is blocked till the operation is completed. This behavior is not 
  +desirable when there are many Web Service invocations to be done in a single client application. A solution, would be to use a Non-Blocking API to invoke web services. Axis2 provides a callback based non-blocking API for users. </p>
  +<p>A sample client for this can be found under "Axis2Home/samples/userguide/src/userguide/clients" with the name EchoNonBlockingClient. If we consider the changes that the user may have to do with respect to the "EchoBlockingClient" that we have already seen, it will be as follows.</p>
  +
       <div class="source"><pre><pre>call.invokeNonBlocking("echo", payload, callback);</pre>
   <p>The invocation  accepts a callback object as a parameter. Axis2 client API provides an 
   abstract Callback with the following methods.</p>
  @@ -267,6 +296,7 @@
   (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>
  +<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
   <a href="Axis2ArchitectureGuide.html">Architecture Guide</a> for more details 
  @@ -493,7 +523,7 @@
   the "Axis2Home/samples/userguide" directory.</p>
   
   
  -<h4>Step7 : Deploy the module in Axis2</h4>
  +<h4>Step7 : Deploy the Module in Axis2</h4>
   
   
   <p>Deploying a module in Axis2 require the user to create a directory with the 
  @@ -592,7 +622,7 @@
   <a href="CodegenToolReference.html">Service Archiver</a>.</p>
   <hr></hr>
   <p>�</p>
  -<h2>Configuring Transports</h2>
  +<h2><a name="#configTransport">Configuring Transports</a></h2>
   <h3>Configuring HTTP transports</h3>
   <p>The HTTP is configured by default, the server can be started by following </p>
   <code>Java org.apache.axis.transport.http.SimpleHTTPServer repository port</code>
  @@ -614,7 +644,7 @@
     
   <h4>Transport Sender</h4>
   </a><p><a>You need a mail account in a SMTP server, and Mail transport sender can be activated by adding following entry to the server.xml file or client.xml file or in both.
  -</a></p>
  +  </a></p>
     
     <code>
     </code><pre><code>   &lt;transportSender name="mail" class="org.apache.axis.transport.mail.MailTransportSender"&gt;
  @@ -682,9 +712,12 @@
     
     
   
  -
   </pre></div>
     </pre></div>
     </pre></div>
     </pre></div>
  +  </pre></div>
  +  </pre></div>
  +  </pre></div>
  +  </pre></div>
     </div></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">� 2004-2005, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
  \ No newline at end of file