ws-axis-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chinth...@apache.org
Subject svn commit: r370414 - in /webservices/axis2/trunk/java/xdocs/0_94: Axis2ArchitectureGuide.html installationguide.html
Date Thu, 19 Jan 2006 08:04:17 GMT
Author: chinthaka
Date: Thu Jan 19 00:04:12 2006
New Revision: 370414

URL: http://svn.apache.org/viewcvs?rev=370414&view=rev
Log:
Commiting Azeez's changes to fix internal links.thanks azeez

Modified:
    webservices/axis2/trunk/java/xdocs/0_94/Axis2ArchitectureGuide.html
    webservices/axis2/trunk/java/xdocs/0_94/installationguide.html

Modified: webservices/axis2/trunk/java/xdocs/0_94/Axis2ArchitectureGuide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/Axis2ArchitectureGuide.html?rev=370414&r1=370413&r2=370414&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/Axis2ArchitectureGuide.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/Axis2ArchitectureGuide.html Thu Jan 19 00:04:12 2006
@@ -9,7 +9,7 @@
 </head>
 
 <body lang="en-US" dir="ltr">
-<h1 align="center">Axis2 Architecture Guide</h1>
+<h1 align="center">Axis2 Architecture Guid</h1>
 
 <p><i>Version 0.94</i></p>
 <i>Feedback: <a
@@ -65,7 +65,7 @@
       </li>
       <li><a href="#bmDB">Data Binding</a>
         <ul>
-          <li><a href="#inegration">Integration with the code generation
+          <li><a href="#integration">Integration with the code generation
             engine</a></li>
           <li><p><a href="#serial">Serialization and De-Serialization</a></p>
           </li>
@@ -75,14 +75,16 @@
   </li>
 </ul>
 
-<h2><a name="bmBP"></a>The Big Picture</h2>
+<a name="bmBP"/>
+<h2>The Big Picture</h2>
 
 <p>Any architecture is a result of what that architecture should yield. The
 success of an architecture should be evaluated based on the requirements
 expected to be met by that architecture. Let us start our journey into Axis2
 by looking at the requirements.</p>
 
-<h2><a name="requirements">Requirement of Axis2</a></h2>
+<a name="requirements"/>
+<h2>Requirement of Axis2</h2>
 
 <p>In the SOAP terminology, a participant who is taking part in a Web Service
 interaction is known as a SOAP Node. Delivery of a single SOAP Message is
@@ -95,8 +97,8 @@
 is possible because on the wire each Web Service interaction is done via
 SOAP, which is common to every SOAP Node.</p>
 
-<p><img src="images/archi-guide/soap.gif" name="Graphic1" align="bottom"
-width="691" height="319" border="0"></p>
+<p><img alt="" src="images/archi-guide/soap.gif" name="Graphic1" align="bottom"
+        width="691" height="319" border="0"/></p>
 
 <p>Web Service middleware handles the complexity in SOAP messaging and lets
 the users work with the programming language they are accustomed to. Axis2
@@ -107,7 +109,7 @@
 the life of the Web Service developer a whole lot easier. Following are the
 identified requirements:</p>
 <ol>
-  <li><style="margin-bottom: 0in">Provide a framework to process the SOAP
+  <li>Provide a framework to process the SOAP
     messages. The framework should be extensible and the users should be able
     to extend the SOAP processing per service or per operation basis.
     Furthermore it should be able to model different Message Exchange
@@ -127,12 +129,12 @@
 speed is a major consideration for Axis2. Axis2 Core Architecture is built on
 three specifications- WSDL, SOAP and WS-Addressing. Other specifications like
 JAX-RP, SAAJ &amp; WS-Policy are layered on top of the Core Architecture.</p>
-
-<h2><a name="thearchi">Axis2, The Architecture</a></h2>
+<a name="thearchi"/>
+<h2>Axis2, The Architecture</h2>
 Axis2 architecture lays out some principals to preserve the uniformity. They
 are as follows:
 <ul>
-  <li><p><style="margin-bottom: 0in">Axis2 architecture separates the logic
+  <li><p>Axis2 architecture separates the logic
     and the states. Code that does the processing is stateless inside Axis2.
     This allows code to be executed freely by parallel threads.</p>
   </li>
@@ -147,7 +149,7 @@
 
 <p>Core Modules:</p>
 <ul>
-  <li><style="margin-bottom: 0in"><a href="#bmInfoMod">Information Model</a>-
+  <li><a href="#bmInfoMod">Information Model</a>-
     Axis2 defines a model to handle information and all states are kept in
     this model. The model has a hierarchy for the information. The system
     manages the life cycle of the objects in this hierarchy.</li>
@@ -190,25 +192,26 @@
     layer and providing a programming language specific interface.</p>
   </li>
 </ul>
-<map name="Graphic2Map">
-  <area shape="rect" coords="123,31,222,97" href="#bmInfoMod">
-  <area shape="rect" coords="239,62,319,134" href="#bmXML">
-  <area shape="rect" coords="127,112,218,177" href="#bmSOAPPM">
-  <area shape="rect" coords="12,39,89,95" href="#bmDeployment">
-  <area shape="rect" coords="0,108,94,156" href="#bmWSDL">
-  <area shape="rect" coords="350,31,426,86" href="#bmClientAPI">
-  <area shape="rect" coords="350,114,421,164" href="#bmTransports">
+<map name="Graphic2Map" id="g2m">
+  <area shape="rect" coords="123,31,222,97" href="#bmInfoMod" alt="">
+  <area shape="rect" coords="239,62,319,134" href="#bmXML" alt="">
+  <area shape="rect" coords="127,112,218,177" href="#bmSOAPPM" alt="">
+  <area shape="rect" coords="12,39,89,95" href="#bmDeployment" alt="">
+  <area shape="rect" coords="0,108,94,156" href="#bmWSDL" alt="">
+  <area shape="rect" coords="350,31,426,86" href="#bmClientAPI" alt="">
+  <area shape="rect" coords="350,114,421,164" href="#bmTransports" alt="">
 </map>
 
-<p><img src="images/archi-guide/all.png" name="Graphic2" width="426"
-height="189" border="0" align="bottom" usemap="#Graphic2Map"></p>
+<p><img src="images/archi-guide/all.png" name="Graphic2" width="426"  alt=""
+height="189" border="0" align="bottom" usemap="#Graphic2Map"/></p>
 
-<h2><a name="bmInfoMod"></a>Information Model</h2>
+<a name="bmInfoMod"/>
+<h2>Information Model</h2>
 
 <p>Information Model has two main hierarchies-Contexts and Descriptions. This
 model is described in UML notations below.</p>
 
-<p><img src="images/archi-guide/contexts.png" name="Graphic3" align="bottom"
+<p><img src="images/archi-guide/contexts.png" name="Graphic3" align="bottom" alt=""
 width="400" height="443" border="0"></p>
 
 <p>( A ----&lt;&gt; B says, B has 1 or more objects of A. A------&gt;B says,
@@ -290,7 +293,8 @@
       </td>
     </tr>
     <tr>
-      <td width="112"><p><a name="messageContext"></a>Message Context</p>
+        <a name="messageContext"/>
+      <td width="112"><p>Message Context</p>
       </td>
       <td width="371"><p>Holds all the information about the Message
         currently being executed.</p>
@@ -303,15 +307,15 @@
     </tr>
   </tbody>
 </table>
-
-<h2><a name="bmXML"></a>XML Processing Model</h2>
+<a name="bmXML"/>
+<h2>XML Processing Model</h2>
 
 <p>Please refer to the <a href="OMTutorial.html">OM Tutorial</a></p>
+<a name="bmSOAPPM"/>
+<h2>SOAP Processing Model</h2>
 
-<h2><a name="bmSOAPPM"></a>SOAP Processing Model</h2>
-
-<p><img src="images/archi-guide/soap-processing.gif" name="Graphic4"
-align="bottom" width="755" height="348" border="0"></p>
+<p><img src="images/archi-guide/soap-processing.gif" name="Graphic4"  alt=""
+align="bottom" width="755" height="348" border="0"/></p>
 
 <p>The architecture identified two basic actions a SOAP processor should
 perform, sending and receiving SOAP messages. The architecture provides two
@@ -356,32 +360,33 @@
 <p>Following figure shows the two pipes with their pre-defined phases &amp;
 user-defined phases. User-defined phases fit in to the User Phases.</p>
 
-<p><img src="images/archi-guide/phases.png" name="Graphic5" align="bottom"
-width="525" height="226" border="0"></p>
-
-<h3><a name="default">Axis2 Default Processing Model</a></h3>
+<p><img src="images/archi-guide/phases.png" name="Graphic5" align="bottom" alt=""
+width="525" height="226" border="0"/></p>
+<a name="default"/>
+<h3>Axis2 Default Processing Model</h3>
 
 <p>Axis2 has some inbuilt handlers that run in inbuilt phases and they create
 the default configuration for the Axis2. We will be looking more in to how to
 extend the default processing Model in the next section.</p>
 There are four special handlers defined in Axis2.
 <ol>
-  <li><style="margin-bottom: 0in">Dispatchers - Finds the service and the
+  <li>Dispatchers - Finds the service and the
     operation the SOAP message is directed to. Dispatchers always run on the
     <em>In-Pipe</em> and inside the Dispatch phase. The in-built dispatchers
     dispatch to a particular operation depending on various conditions like
     WS-Addressing information, URI information, SOAP action information,
   etc.,</li>
-  <li><p style="margin-bottom: 0in"><a name="mr"></a>Message Receiver -
+  <a name="mr"/>
+  <li>Message Receiver -
     Consume the SOAP Message and run on the Message Processing phase in the
-    inflow</p>
+    inflow
   </li>
   <li><p>Transport Sender - Send the SOAP message to the SOAP endpoint the
     message is destined to. Always runs on the</p>
   </li>
 </ol>
-
-<h3><a name="incomingsoap">Processing an Incoming SOAP Message</a></h3>
+<a name="incomingsoap"/>
+<h3>Processing an Incoming SOAP Message</h3>
 
 <p>Incoming SOAP Message is always received by a Transport Receiver waiting
 for the SOAP Messages. Once the SOAP Message arrives the transport Headers
@@ -394,28 +399,26 @@
 using the Two-Way transport where the first four phases of the In-Phase most
 likely does nothing.</p>
 <ol>
-  <li><p style="margin-bottom: 0in">Transport Phase - The handlers in the
+  <li>Transport Phase - The handlers in the
     transport phase are taken from the transport configuration associated and
-    executed according to the phase rules.</p>
+    executed according to the phase rules.
   </li>
-  <li><p style="margin-bottom: 0in">Pre-Dispatch Phase- handlers in this
+  <li>Pre-Dispatch Phase- handlers in this
     phase will be engaged globally since the service is not found yet. 
-   </p>
   </li>
-  <li><p style="margin-bottom: 0in">Dispatch Phase - The Dispatchers run in
+  <li>Dispatch Phase - The Dispatchers run in
     this phase and find the Service if the service is not found already.
-    <br> The post condition of the dispatch phase work as follows;
+    <br/> The post condition of the dispatch phase work as follows;
        That checks weather the service is found or not. If the service has not been found by
     this point the execution will halt and send a "service not found
-    error".</p>
-    </p>
+    error".
   </li>
-  <li><p style="margin-bottom: 0in">User Defined Phases - Users are allowed
-    to engage their custom handlers here.</p>
+  <li>User Defined Phases - Users are allowed
+    to engage their custom handlers here.
   </li>
-  <li><p style="margin-bottom: 0in">Message Validation Phase - Once the user
+  <li>Message Validation Phase - Once the user
     level execution has taken place this phase validates whether SOAP Message
-    Processing has taken place correctly.</p>
+    Processing has taken place correctly.
   </li>
   <li><p>Message Processing Phase - The Business logic of the SOAP message is
     executed here. A <a href="#mr">Message Receiver</a> is registered with
@@ -428,7 +431,8 @@
 custom handlers to override the mechanics in each of these phases.
 </p>
 
-<h3><a name="outgoing">Processing of the Outgoing Message</a></h3>
+<a name="outgoing"/>
+<h3>Processing of the Outgoing Message</h3>
 
 <p><em>Out Pipe</em> is simpler because the service and operation to dispatch
 is known by the time the pipe is executed. The <em>Out Pipe</em> may be
@@ -436,20 +440,20 @@
 implementation.</p>
 Phases of the <em>Out Pipe</em> are described below:
 <ol>
-  <li><p style="margin-bottom: 0in">Message Initialize Phase - Fist phase of
+  <li>Message Initialize Phase - Fist phase of
     the <em>Out Pipe</em>. Serves as the placeholder for the custom
-    handlers</p>
+    handlers
   </li>
-  <li><p style="margin-bottom: 0in">User Phases - This executes handlers in
-    user defined phases</p>
+  <li>User Phases - This executes handlers in
+    user defined phases
   </li>
   <li><p>Transports Phase - Execute any transport handlers taken from the
     associated transport configuration. The last handler would be a transport
     Sender which would send the SOAP message to the target end point.</p>
   </li>
 </ol>
-
-<h3><a name="extending">Extending SOAP Processing Model</a></h3>
+<a name="extending"/>
+<h3>Extending SOAP Processing Model</h3>
 
 <p>Above we discussed the default processing model of Axis2. Now lets discuss
 the extension mechanism for the SOAP processing model. After all, the whole
@@ -462,23 +466,24 @@
 other handlers enabling this modification on the default processing behavior.
 SOAP Processing Model can be extended with handler or Modules.</p>
 
-<h4><a name="extendingwithhandlers">Extending the SOAP Processing Model with
-Handlers</a></h4>
+<a name="extendingwithhandlers"/>
+<h4>Extending the SOAP Processing Model with
+Handlers</h4>
 The handlers can specify the phase they need to be placed in. Furthermore
 they can specify their location inside a phase by providing phase rules.
 Phase rules will place a handler
 <ol>
-  <li><style="margin-bottom: 0in">as the first handler in a phase.</li>
-  <li><p style="margin-bottom: 0in">or as the last handler in a phase.</p>
+  <li>as the first handler in a phase.</li>
+  <li>or as the last handler in a phase.
   </li>
-  <li><p style="margin-bottom: 0in">or before a given handler</p>
+  <li>or before a given handler
   </li>
-  <li><p style="margin-bottom: 0in">or after a given handler</p>
+  <li>or after a given handler
   </li>
 </ol>
-
-<h4><a name="extendingwithmodules">Extending the SOAP Processing Model with
-Modules</a></h4>
+<a name="extendingwithmodules"/>
+<h4>Extending the SOAP Processing Model with
+Modules</h4>
 
 <p>Axis2 defines an entity called a 'module' that can introduce handlers and
 web service operations. A Module in terms of Axis2 usually acts as a
@@ -507,39 +512,42 @@
 <p>Modules can not be added while the Axis2 engine is running, but they will
 be available once the system is restarted.</p>
 
-<h2><a name="bmDeployment"></a>Deployment</h2>
+<a name="bmDeployment"/>
+<h2>Deployment</h2>
 
 <p>The Deployment Model provides a concrete mechanism to configure Axis2.
 This model has three entities that provide the configuration.</p>
 
-<h3><a name="xmlfile">The <em>axis2.xml</em> file</a></h3>
+<a name="xmlfile"/>
+<h3>The <em>axis2.xml</em> file</h3>
 
 <p>This file holds the global configuration for the client and server, and
 provide following information:</p>
 <ol>
-  <li><p style="margin-bottom: 0in">The global parameters</p>
+  <li>The global parameters
   </li>
-  <li><p style="margin-bottom: 0in">Registered transports in and transport
-    outs</p>
+  <li>Registered transports in and transport
+    outs
   </li>
-  <li><p style="margin-bottom: 0in">User defined phase names</p>
+  <li>User defined phase names
   </li>
-  <li><p style="margin-bottom: 0in">Modules that are engaged globally (to all
-    services)</p>
+  <li>Modules that are engaged globally (to all
+    services)
   </li>
   <li><p>Globally defined <a href="#mr">Message Receivers</a></p>
   </li>
 </ol>
 
-<h3><a name="servicearchive">Service Archive</a></h3>
+<a name="servicearchive"/>
+<h3>Service Archive</h3>
 
 <p>Service archive must have a <em>META-INF/services.xml</em> file and may
 contain the dependent classes. The <em>services.xml</em> file has following
 information.</p>
 <ol>
-  <li><p style="margin-bottom: 0in">Service level parameters</p>
+  <li>Service level parameters
   </li>
-  <li><p style="margin-bottom: 0in">Modules that are engaged Service level</p>
+  <li>Modules that are engaged Service level
   </li>
   <li><p>Service Specific <a href="#mr">Message Receivers</a></p>
   </li>
@@ -547,7 +555,8 @@
   </li>
 </ol>
 
-<h3><a name="modulearchive">Module Archive</a></h3>
+<a name="modulearchive"/>
+<h3>Module Archive</h3>
 
 <p>Module archive must have a <em>META-INF/module.xml</em> file and dependent
 classes. The <em>module.xml</em> file has Module parameters and the
@@ -563,18 +572,19 @@
 thread will check the repository repeatedly, and then add the service
 corresponding to the new found service archives to the repository.</p>
 
-<h2><a name="bmClientAPI"></a>Client API</h2>
+<a name="bmClientAPI"/>
+<h2>Client API</h2>
 
 <p>There are three parameters that decide the nature of the Web Service
 interaction.</p>
 <ol>
-  <li><p style="margin-bottom: 0in">Message Exchange Pattern (MEP)</p>
+  <li>Message Exchange Pattern (MEP)
   </li>
-  <li><p style="margin-bottom: 0in">The Behavior of the transport, whether
-    it's One-Way or Two-Way</p>
+  <li>The Behavior of the transport, whether
+    it's One-Way or Two-Way
   </li>
-  <li><p style="margin-bottom: 0in">Synchronous/ Asynchronous behavior of the
-    Client API</p>
+  <li>Synchronous/ Asynchronous behavior of the
+    Client API
   </li>
 </ol>
 
@@ -588,28 +598,30 @@
 <code>ServiceClient</code> and there are extensions for each MEP that Axis2
 Client API supports.</p>
 
-<h3><a name="oneway">One Way Messaging Support</a></h3>
+<a name="oneway"/>
+<h3>One Way Messaging Support</h3>
 
 <p>The One-Way support is provided by the <code>fireAndForget</code> which provide by
  <code>ServiceClient</code> that provides a much simpler interface for the user. 
 The Axis2 supports HTTP/SMTP and TCP transports. In the case of the HTTP transport
  the return channel is not used and the HTTP 202 OK is returned in the return Channel.</p>
 
-<h3><a name="requestresponse">Request Response Messaging Support</a></h3>
+<a name="requestresponse"/>
+<h3>Request Response Messaging Support</h3>
 
 <p>The Request-Response support is provided by the
 <code>sendReceive()</code> method in ServiceClient ,that provides a much simpler interface for the user. The
 Client API has four ways to configure a given Message Exchange</p>
 <ol>
-  <li><p style="margin-bottom: 0in">Blocking or Non-Blocking nature - this
+  <li>Blocking or Non-Blocking nature - this
     can be decided by using <code>sendReceive()</code> or
-    <code>sendReceiveNonBlocking()</code> methods</p>
+    <code>sendReceiveNonBlocking()</code> methods
   </li>
-  <li><p style="margin-bottom: 0in">Sender transport - transport used to send
-    the SOAP Message</p>
+  <li>Sender transport - transport used to send
+    the SOAP Message
   </li>
-  <li><p style="margin-bottom: 0in">Listener transport - transport the
-    Response is received</p>
+  <li>Listener transport - transport the
+    Response is received
   </li>
   <li><p>Use Separate Channel - determines whether the response is send over
     a separate transport connection or not. This can be false only when
@@ -620,7 +632,8 @@
 <p>Depending on the values of the above four parameter, Axis2 behave
 differently.</p>
 
-<h2><a name="bmTransports"><em></em></a>Transports</h2>
+<a name="bmTransports"/>
+<h2>Transports</h2>
 
 <p>Axis2 has two basic constructs for transports, transport In Configuration
 and transport Out Configuration. These are accessed via the messages
@@ -638,11 +651,11 @@
 <p>Transport In Configuration and the transport Out Configuration contains
 following information.</p>
 <ol>
-  <li><style="margin-bottom: 0in">Transport Sender for Out Configuration</li>
-  <li><p style="margin-bottom: 0in">Transport Listener for In
-    Configuration</p>
+  <li>Transport Sender for Out Configuration</li>
+  <li>Transport Listener for In
+    Configuration
   </li>
-  <li><p style="margin-bottom: 0in">Parameters of the transport</p>
+  <li>Parameters of the transport
   </li>
   <li><p>Transport handlers</p>
   </li>
@@ -656,20 +669,21 @@
 
 <p>Axis2 Presently support the following transports:</p>
 <ol>
-  <li><style="margin-bottom: 0in">HTTP - In HTTP transport the transport
+  <li>HTTP - In HTTP transport the transport
     listener is a servlet or org.apache.axis2.transport.http.SimpleHTTPServer
     provided by Axis2. The transport sender uses commons-httpclient to
     connect and send the SOAP Message.</li>
-  <li><p style="margin-bottom: 0in">TCP - This is the most simplest
-    transport, but needs the WS - Addressing support to be functional.</p>
+  <li>TCP - This is the most simplest
+    transport, but needs the WS - Addressing support to be functional.
   </li>
-  <li><p style="margin-bottom: 0in">SMTP - This works off a single email
+  <li>SMTP - This works off a single email
     account. Transport receiver is a thread that checks for emails in fixed
-    time intervals.</p>
+    time intervals.
   </li>
 </ol>
 
-<h2><a name="bmWSDL" id="bmWSDL"></a>Code generation</h2>
+<a name="bmWSDL" id="bmWSDL"/>
+<h2>Code generation</h2>
 
 <p>Although the basic objective of the code generation tool has not changed,
 the code generation module of Axis2 has taken a different approach to
@@ -681,8 +695,8 @@
 parse it with a template to generate the code file. The following figure
 describes how this shows up in the architecture of the tool.</p>
 
-<p><img src="images/archi-guide/CodegenArchitecture.jpg" name="Graphic6"
-align="bottom" width="478" height="218" border="0"></p>
+<p><img src="images/archi-guide/CodegenArchitecture.jpg" name="Graphic6" alt=""
+align="bottom" width="478" height="218" border="0"/></p>
 
 <p>The fact here is that it is the same information that is extracted from
 the WSDL no matter what code is generated. Code generator uses the WOM (WSDL
@@ -691,9 +705,11 @@
 XSL to generate the code. No matter what the language, the process is the
 same except for the template that is being used</p>
 
-<h2><a name="bmDB" id="bmDB"></a>Data Binding</h2>
+<a name="bmDB" id="bmDB"/>
+<h2>Data Binding</h2>
 
-<h3><a name="inegration">Integration with the code generation engine</a></h3>
+<a name="integration"/>
+<h3>Integration with the code generation engine</h3>
 
 <p>Axis2 M2 was released with code generation support but without data
 binding. The version 0.9 was shipped with data binding support with complete
@@ -705,10 +721,11 @@
 generation engine. Axis2 version 0.91 does not support SOAP encoding. It only
 supports RPC literal or document literal massages.</p>
 
-<p><img src="images/codegen.gif" name="Graphic7" align="bottom" width="406"
-height="467" border="0"></p>
+<p><img src="images/codegen.gif" name="Graphic7" align="bottom" width="406" alt=""
+height="467" border="0"/></p>
 
-<h3><a name="serial">Serialization and De-Serialization</a></h3>
+<a name="serial"/>
+<h3>Serialization and De-Serialization</h3>
 
 <p>AXIOM is based on a StAX (Streaming API for XML) API. Xml-beans supports
 StAX API. Data binding in Axis2 is achieved through interfacing the AXIOM

Modified: webservices/axis2/trunk/java/xdocs/0_94/installationguide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/installationguide.html?rev=370414&r1=370413&r2=370414&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/installationguide.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/installationguide.html Thu Jan 19 00:04:12 2006
@@ -1,3 +1,4 @@
+<<<<<<< .mine
 <!-- saved from url=(0022)http://internet.e-mail -->
 <html>
 <head>
@@ -6,14 +7,11 @@
   <style type="text/css">
 <!--
 .style1 {
-font-family: "Courier New", Courier, mono;
-font-size: 14px;
-font-style: italic;
+	font-family: "Courier New", Courier, mono;
+	font-size: 14px;
+	font-style: italic;
 }
-.style2 {font-family: Arial, Helvetica, sans-serif}
 -->
-
-
   </style>
 </head>
 
@@ -26,7 +24,7 @@
 
 <h3>Contents</h3>
 <ul>
-  <li><a href="#Download_Axis2">Download Axis2</a></li>
+  <li><a href="#Download">Download Axis2</a></li>
   <li><p><a href="#requirements">System Requirements</a></p>
   </li>
   <li><a href="#_Toc96698083">Setting up the Environment and tools</a>
@@ -44,112 +42,399 @@
   </li>
 </ul>
 
-<h3><a name="Download_Axis2">Download Axis2</a></h3>
-
-<p>Axis2 is distributed in several convenient distribution packages and can
-be installed either as a standalone server or as part of a J2EE compliant
-servlet container. Axis2 is distributed under the Apache License, version
-2.0. You can download Axis2 <a
-href="http://ws.apache.org/axis2/download.cgi">here</a>. Latest release of
-Axis2 is version 0.94.</p>
+<a name="Download"/>
+<h3>Download Axis2</h3>
 
+<p>Axis2 is distributed in several convenient distribution packages and can be installed either as a
+standalone server or as part of a J2EE compliant servlet container. Axis2 is
+distributed under the Apache License, version 2.0. You can download Axis2 <a href="http://ws.apache.org/axis2/download.cgi">here</a>. Latest release of Axis2 is version 0.94. </p>
 <table width="940" border="1" cellpadding="1">
+  <tr>
+    <th width="83" scope="col">Distribution Name</th>
+    <th width="633" scope="col">Description</th>
+    <th width="202" scope="col">Items</th>
+  </tr>
+  <tr>
+    <td>Minimal Distribution - Binary </td>
+    <td>This distribution is aimed at advanced users who will be embedding Axis2. It will contain the minimal runtime required to act as a Web Service client and/or a server (axis2-core-0.94.jar will contain compiled versions of common, xml, wsdl and core modules.) </td>
+    <td><ul>
+      <li>axis2-core-0.94.jar, axis2-adb-0.94.jar</li>
+      <li>third party distributable libraries</li>
+      <li>README.TXT and release-notes.html </li>
+    </ul></td>
+  </tr>
+  <tr>
+    <td>Minimal Distribution - Source </td>
+    <td background="#_Toc96698083"><p>This will contain the sources of Axis2 minimal distribution. One can generate a binary distribution from this by typing  <span class="style1">$maven dist-min-bin. </span>(<a href="#_Toc96698083">Set up Axis2 environment</a> before running this command) </p></td>
+    <td><ul>
+      <li>sources of Axis2 common, xml, wsdl, adb and core modules </li>
+      <li>README.TXT and release-notes.html</li>
+    </ul></td>
+  </tr>
+  <tr>
+    <td>Standard Distribution - Binary </td>
+    <td>This is the complete version of Axis2 and will contain useful samples as well. Useful for some one to get familiar with Axis2. (Since WS-Addressing implementation module is engaged in to Axis2, by default, this distribution will contain addressing.mar. But  the other modules that are being developed within Axis2 will not be included here and are available to be downloaded separately from <a href="http://ws.apache.org/axis2/modules/index.html">here</a>.)</td>
+    <td><ul>
+      <li>all the content of minimal-binary distribution</li>
+      <li>Contents of codegen and DOOM modules</li>
+      <li>Samples</li>
+      <li>addressing.mar</li>
+    </ul></td>
+  </tr>
+  <tr>
+    <td>Standard Distribution - Source </td>
+    <td>This will contain the sources of Axis2 standard distribution. One can generate a binary distribution from this by typing <span class="style1">$maven dist-standard-bin. </span>(<a href="#_Toc96698083">Set up Axis2 environment</a> before running this command) </td>
+    <td><ul>
+      <li>all the content of minimal-source distribution</li>
+      <li>Contents of codegen and DOOM modules</li>
+      <li>Samples</li>
+      </ul></td>
+  </tr>
+  <tr>
+    <td>WAR (Web Archive) Distribution </td>
+    <td>This will be the web application of Axis2 which can be deployed in most of the servlet containers. </td>
+    <td><ul>
+      <li>
+        all the contents of the minimal distribution
+      </li>
+      <li>
+        Admin web app
+      </li>
+    </ul></td>
+  </tr>
+  <tr>
+    <td>Documents Distribution </td>
+    <td>This will contain all the documentation in one package.</td>
+    <td><ul>
+      <li>xdocs</li>
+      <li>javadocs </li>
+    </ul></td>
+  </tr>
+  <tr>
+    <td>Plugin Distribution </td>
+    <td>This will contain the plugins that are created for Eclipse and IDEA.</td>
+    <td><ul>
+      <li>Intellij IDEA plugins</li>
+      <li>Eclipse plugins</li>
+    </ul></td>
+  </tr>
+</table>
+<a name="requirements"/>
+<h3>System Requirements</h3>
+
+<table border="2">
+  <caption></caption>
   <tbody>
     <tr>
-      <th width="83" scope="col">Distribution Name</th>
-      <th width="633" scope="col">Description</th>
-      <th width="202" scope="col">Items</th>
-    </tr>
-    <tr>
-      <td>Minimal Distribution - Binary</td>
-      <td>This distribution is aimed at advanced users who will be embedding
-        Axis2. It will contain the minimal runtime required to act as a Web
-        Service client and/or a server (axis2-core-0.94.jar will contain
-        compiled versions of common, xml, wsdl and core modules.)</td>
-      <td><ul>
-          <li>axis2-core-0.94.jar, axis2-adb-0.94.jar</li>
-          <li>third party distributable libraries</li>
-          <li>README.TXT and release-notes.html</li>
-        </ul>
-      </td>
-    </tr>
-    <tr>
-      <td>Minimal Distribution - Source</td>
-      <td background="#_Toc96698083"><p>This will contain the sources of
-        Axis2 minimal distribution. One can generate a binary distribution
-        from this by typing  <span class="style1">$maven dist-min-bin.
-        </span>(<a href="#_Toc96698083">Set up Axis2 environment</a> before
-        running this command)</p>
-      </td>
-      <td><ul>
-          <li>sources of Axis2 common, xml, wsdl, adb and core modules</li>
-          <li>README.TXT and release-notes.html</li>
-        </ul>
+      <td>Java Runtime
+
+        <p>Environment</p>
       </td>
-    </tr>
-    <tr>
-      <td>Standard Distribution - Binary</td>
-      <td>This is the complete version of Axis2 and will contain useful
-        samples as well. Useful for some one to get familiar with Axis2.
-        (Since WS-Addressing implementation module is engaged in to Axis2, by
-        default, this distribution will contain addressing.mar. But  the
-        other modules that are being developed within Axis2 will not be
-        included here and are available to be downloaded separately from <a
-        href="http://ws.apache.org/axis2/modules/index.html">here</a>.)</td>
-      <td><ul>
-          <li>all the content of minimal-binary distribution</li>
-          <li>Contents of codegen and DOOM modules</li>
-          <li>Samples</li>
-          <li>addressing.mar</li>
-        </ul>
+      <td>1.4 (It has not been fully tested on the latest JRE 1.5)
+
+        <p>For instructions on setting up the JRE in different operating
+        systems, visit <a
+        href="http://java.sun.com/">http://java.sun.com</a></p>
       </td>
     </tr>
     <tr>
-      <td>Standard Distribution - Source</td>
-      <td>This will contain the sources of Axis2 standard distribution. One
-        can generate a binary distribution from this by typing <span
-        class="style1">$maven dist-standard-bin. </span>(<a
-        href="#_Toc96698083">Set up Axis2 environment</a> before running this
-        command)</td>
-      <td><ul>
-          <li>all the content of minimal-source distribution</li>
-          <li>Contents of codegen and DOOM modules</li>
-          <li>Samples</li>
-        </ul>
+      <td>Maven</td>
+      <td>1.0.2 or higher (<a href="http://maven.apache.org/">download</a>)
+
+        <p>Required only for building Axis2 from source distribution</p>
       </td>
     </tr>
     <tr>
-      <td>WAR (Web Archive) Distribution</td>
-      <td>This will be the web application of Axis2 which can be deployed in
-        most of the servlet containers.</td>
-      <td><ul>
-          <li>all the contents of the minimal distribution</li>
-          <li>Admin web app</li>
-        </ul>
-      </td>
+      <td>Memory</td>
+      <td>No minimum requirement</td>
     </tr>
     <tr>
-      <td>Documents Distribution</td>
-      <td>This will contain all the documentation in one package.</td>
-      <td><ul>
-          <li>xdocs</li>
-          <li>javadocs</li>
-        </ul>
+      <td>Disk</td>
+      <td>No minimum requirement.
+
+        <p>Approximately 20 MB will be used for war distribution</p>
       </td>
     </tr>
     <tr>
-      <td>Plugin Distribution</td>
-      <td>This will contain the plugins that are created for Eclipse and
-      IDEA.</td>
-      <td><ul>
-          <li>Intellij IDEA plugins</li>
-          <li>Eclipse plugins</li>
-        </ul>
-      </td>
+      <td>Operating system</td>
+      <td>Tested on Windows XP, Mac OS X, Fedora core, Ubuntu, Gentoo</td>
     </tr>
   </tbody>
 </table>
 
+<p></p>
+
+<p>All the required jars are shipped with the binary distribution.</p>
+
+<p>Running the Maven build will automatically download the required jars when
+using source distribution.</p>
+
+<a name="_Toc96698083"/>
+<h3>Setting up the Environment and Tools</h3>
+
+<a name="_Toc96698084" id="_Toc96698084"/>
+<h4>Maven</h4>
+
+<p>The Axis2 build is based on <a href="http://maven.apache.org/">Maven </a>.
+Hence the only prerequisite to build Axis2 from source distribution is to
+have Maven installed. Extensive instruction guides are available at the Maven
+site.This guide however contains the easiest path for quick environment
+setting. Advanced users who wish to know more about Maven can visit <a
+href="http://maven.apache.org/start/index.html">here </a>.</p>
+<ul>
+<li>Windows</li>
+<ol>
+  <li>Download and run the Windows installer package</li>
+  <li>Set the 'Environment Variables' ( create system variable MAVEN_HOME and
+    edit path. eg: "C:\Program Files\Apache Software Foundation\maven-2.0.1";
+    path %MAVEN_HOME%\bin)</li>
+  <li>Make sure that system variable JAVA_HOME is set to the location of your
+    JDK, eg. C:\Program Files\Java\jdk1.5.0_02</li>
+  <li>Run maven --version to verify that it is correctly installed.</li>
+</ol>
+
+
+<p align="center"><img alt="clip_image002 (15K)"
+src="images/clip_image002.jpg" height="211" width="477"></p>
+
+<li>Unix based OS (Linux etc)</li>
+
+<p>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">here </a>.</p>
+
+</ul>
+<p>Once maven is properly installed you can start building Axis2.</p>
+
+<a name="_Toc96698085"/>
+<h4>The Axis2 source distribution</h4>
+
+<p>The <a href="http://ws.apache.org/axis2/download.cgi">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 running maven command will build the
+Axis2 jar file.</p>
+
+<p align="center"><img alt="clip_image004 (43K)" src="images/maven.jpg"
+height="248" width="668"></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 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>
+
+<a name="_Toc96698086"/>
+<h3>Installing Axis2 in a Servlet container</h3>
+<ol>
+  <li>Download Axis2 war file</li>
+  <li>Drop the war in the webapps folder. Most servlet containers will
+    automatically install war. (some servlet containers may require a restart
+    in order to capture the new web application. Refer your servlet container
+    documentation for more information about this.)</li>
+  <li>Once the WAR is successfully installed, test it by pointing the web
+    browser to the <strong>http:// &lt;host :port&gt;/ axis2. </strong>It
+    should produce the following page.</li>
+
+  <p align="center"><strong><img src="images/clip_image006.jpg" alt=""/></strong></p>
+
+  <p></p>
+  <li>Use validate link to ensure that everything is fine and smooth. If the
+    validation fails then the war has failed to 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 Axis2
+    libraries are present.
+    <p></p>
+  </li>
+
+  <p align="center"><strong><img src="images/happyaxis.jpg" alt=""/></strong></p>
+</ol>
+
+<p></p>
+
+<a name="upload"/>
+<h4>Uploading services</h4>
+<ol>
+  <p>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 alt="" src="images/clip_image010.jpg"
+          ></strong></p>
+
+  <p>The uploaded jar files will be stored in the default service directory.
+  For Axis2 this will be the &lt;webapps&gt;/axis2/WEB-INF/services
+  directory. Once a service is uploaded it will be installed instantly.</p>
+
+  <p>Since Axis2 supports hot deployment one can drop the service jar
+  directly through the file system to the above mentioned services
+  directory.It will also cause the service to be automatically installed
+  without the container being restarted.</p>
+
+  <p>Use the <i>available services link</i> to check the successful
+  installation of a service. The services and the operations of successfully
+  installed services will be displayed in the available services page.</p>
+
+  <p align="center"><img alt="" src="images/clip_image012.jpg"
+          ></p>
+
+  <p></p>
+
+  <p>If the service has deployment time error it will list those services
+  as faulty services. If you click on the link you can see the your deployment
+  fault error message(s).</p>
+
+  <p align="center"><img src="images/faultservice.jpg"
+  alt=""></p>
+
+  <p>Deployment time error message</p>
+
+  <p align="center"><strong><img alt="" src="images/faultmsg.jpg"
+          ></strong></p>
+
+  <p></p>
+
+  <p>Axis2 Administration is all about configuring Axis2 at the run time and
+  the configuration will be transient. More descriptions are available in <a
+  href="webadminguide.html">Axis2 Web Administration Guide</a></p>
+</ol>
+</body>
+</html>
+=======
+<!-- saved from url=(0022)http://internet.e-mail -->
+<html>
+<head>
+  <meta http-equiv="content-type" content="">
+  <title>Axis2 Installation Guide</title>
+  <style type="text/css">
+<!--
+.style1 {
+	font-family: "Courier New", Courier, mono;
+	font-size: 14px;
+	font-style: italic;
+}
+.style2 {font-family: Arial, Helvetica, sans-serif}
+-->
+  </style>
+</head>
+
+<body lang="en">
+<h1 align="center">Axis2 Installation Guide</h1>
+
+<p><i>Version 0.94</i></p>
+<i>Feedback: <a
+href="mailto:axis-dev@ws.apache.org">axis-dev@ws.apache.org</a></i>
+
+<h3>Contents</h3>
+<ul>
+  <li><a href="#Download_Axis2">Download Axis2</a></li>
+  <li><p><a href="#requirements">System Requirements</a></p>
+  </li>
+  <li><a href="#_Toc96698083">Setting up the Environment and tools</a>
+    <ul>
+      <li><p><a href="#_Toc96698084">Maven</a></p>
+      </li>
+      <li><a href="#_Toc96698085">The Axis2 source distribution</a></li>
+    </ul>
+  </li>
+  <li><p><a href="#_Toc96698086">Installing Axis2 in a Servlet
+    container</a></p>
+    <ul>
+      <li><a href="#upload">Uploading services</a></li>
+    </ul>
+  </li>
+</ul>
+
+<h3><a name="Download_Axis2">Download Axis2</a></h3>
+
+<p>Axis2 is distributed in several convenient distribution packages and can be installed either as a
+standalone server or as part of a J2EE compliant servlet container. Axis2 is
+distributed under the Apache License, version 2.0. You can download Axis2 <a href="http://ws.apache.org/axis2/download.cgi">here</a>. Latest release of Axis2 is version 0.94. </p>
+<table width="940" border="1" cellpadding="1">
+  <tr>
+    <th width="83" scope="col">Distribution Name</th>
+    <th width="633" scope="col">Description</th>
+    <th width="202" scope="col">Items</th>
+  </tr>
+  <tr>
+    <td>Minimal Distribution - Binary </td>
+    <td>This distribution is aimed at advanced users who will be embedding Axis2. It will contain the minimal runtime required to act as a Web Service client and/or a server (axis2-core-0.94.jar will contain compiled versions of common, xml, wsdl and core modules.) </td>
+    <td><ul>
+      <li>axis2-core-0.94.jar, axis2-adb-0.94.jar</li>
+      <li>third party distributable libraries</li>
+      <li>README.TXT and release-notes.html </li>
+    </ul></td>
+  </tr>
+  <tr>
+    <td>Minimal Distribution - Source </td>
+    <td background="#_Toc96698083"><p>This will contain the sources of Axis2 minimal distribution. One can generate a binary distribution from this by typing  <span class="style1">$maven dist-min-bin. </span>(<a href="#_Toc96698083">Set up Axis2 environment</a> before running this command) </p></td>
+    <td><ul>
+      <li>sources of Axis2 common, xml, wsdl, adb and core modules </li>
+      <li>README.TXT and release-notes.html</li>
+    </ul></td>
+  </tr>
+  <tr>
+    <td>Standard Distribution - Binary </td>
+    <td>This is the complete version of Axis2 and will contain useful samples as well. Useful for some one to get familiar with Axis2. (Since WS-Addressing implementation module is engaged in to Axis2, by default, this distribution will contain addressing.mar. But  the other modules that are being developed within Axis2 will not be included here and are available to be downloaded separately from <a href="http://ws.apache.org/axis2/modules/index.html">here</a>.)</td>
+    <td><ul>
+      <li>all the content of minimal-binary distribution</li>
+      <li>Contents of codegen and DOOM modules</li>
+      <li>Samples</li>
+      <li>addressing.mar</li>
+    </ul></td>
+  </tr>
+  <tr>
+    <td>Standard Distribution - Source </td>
+    <td>This will contain the sources of Axis2 standard distribution. One can generate a binary distribution from this by typing <span class="style1">$maven dist-standard-bin. </span>(<a href="#_Toc96698083">Set up Axis2 environment</a> before running this command) </td>
+    <td><ul>
+      <li>all the content of minimal-source distribution</li>
+      <li>Contents of codegen and DOOM modules</li>
+      <li>Samples</li>
+      </ul></td>
+  </tr>
+  <tr>
+    <td>WAR (Web Archive) Distribution </td>
+    <td>This will be the web application of Axis2 which can be deployed in most of the servlet containers. </td>
+    <td><ul>
+      <li>
+        all the contents of the minimal distribution
+      </li>
+      <li>
+        Admin web app
+      </li>
+    </ul></td>
+  </tr>
+  <tr>
+    <td>Documents Distribution </td>
+    <td>This will contain all the documentation in one package.</td>
+    <td><ul>
+      <li>xdocs</li>
+      <li>javadocs </li>
+    </ul></td>
+  </tr>
+  <tr>
+    <td>Plugin Distribution </td>
+    <td>This will contain the plugins that are created for Eclipse and IDEA.</td>
+    <td><ul>
+      <li>Intellij IDEA plugins</li>
+      <li>Eclipse plugins</li>
+    </ul></td>
+  </tr>
+</table>
 <h3><a name="requirements">System Requirements</a></h3>
 
 <table border="2">
@@ -169,10 +454,7 @@
     </tr>
     <tr>
       <td>Maven</td>
-      <td>1.0.2 or higher in 1.x series (<a
-        href="http://www.apache.org/dyn/closer.cgi/maven/binaries/">download</a>
-        ). <strong>Please download maven 1.x version. Axis2 is not compatible
-        with maven2 yet)</strong>
+      <td>1.0.2 or higher (<a href="http://maven.apache.org/">download</a>)
 
         <p>Required only for building Axis2 from source distribution</p>
       </td>
@@ -206,31 +488,29 @@
 
 <h4><a name="_Toc96698084" id="_Toc96698084"></a>Maven</h4>
 
-<p>The Axis2 build is based on <a
-href="http://maven.apache.org/maven-1.x/">Maven </a>. Hence the only
-prerequisite to build Axis2 from source distribution is to have Maven
-installed. Extensive instruction guides are available at the Maven site.This
-guide however contains the easiest path for quick environment setting.
-Advanced users who wish to know more about Maven can visit <a
+<p>The Axis2 build is based on <a href="http://maven.apache.org/">Maven </a>.
+Hence the only prerequisite to build Axis2 from source distribution is to
+have Maven installed. Extensive instruction guides are available at the Maven
+site.This guide however contains the easiest path for quick environment
+setting. Advanced users who wish to know more about Maven can visit <a
 href="http://maven.apache.org/start/index.html">here </a>.</p>
 <ul>
-  <li>Windows</li>
-</ul>
+<li>Windows</li>
 <ol>
   <li>Download and run the Windows installer package</li>
   <li>Set the 'Environment Variables' ( create system variable MAVEN_HOME and
-    edit path. eg: "C:\Program Files\Apache Software Foundation\maven-1.0.2";
+    edit path. eg: "C:\Program Files\Apache Software Foundation\maven-2.0.1";
     path %MAVEN_HOME%\bin)</li>
   <li>Make sure that system variable JAVA_HOME is set to the location of your
     JDK, eg. C:\Program Files\Java\jdk1.5.0_02</li>
   <li>Run maven --version to verify that it is correctly installed.</li>
 </ol>
 
+
 <p align="center"><img alt="clip_image002 (15K)"
 src="images/clip_image002.jpg" height="211" width="477"></p>
-<ul>
-  <li>Unix based OS (Linux etc)</li>
-</ul>
+
+<li>Unix based OS (Linux etc)</li>
 
 <p>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
@@ -238,15 +518,16 @@
 instructions for installing Maven in Unix based operating systems can be
 found <a href="http://maven.apache.org/start/install.html">here </a>.</p>
 
+</ul>
 <p>Once maven is properly installed you can start building Axis2.</p>
 
 <h4><a name="_Toc96698085"></a>The Axis2 source distribution</h4>
 
-<p>The <a href="http://ws.apache.org/axis2/download.cgi">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 running
-maven command will build the Axis2 jar file.</p>
+<p>The <a href="http://ws.apache.org/axis2/download.cgi">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 running maven command will build the
+Axis2 jar file.</p>
 
 <p align="center"><img alt="clip_image004 (43K)" src="images/maven.jpg"
 height="248" width="668"></p>
@@ -318,22 +599,24 @@
   installation of a service. The services and the operations of successfully
   installed services will be displayed in the available services page.</p>
 
-  <p align="center"><img src="images/clip_image012.jpg" alt=""></p>
+  <p align="center"><img src="images/clip_image012.jpg"
+  alt=""></p>
 
   <p></p>
 
-  <p>If the service has deployment time error it will list those services as
-  faulty services. If you click on the link you can see the your deployment
+  <p>If the service has deployment time error it will list those services
+  as faulty services. If you click on the link you can see the your deployment
   fault error message(s).</p>
 
-  <p align="center"><img src="images/faultservice.jpg" alt=""></p>
+  <p align="center"><img src="images/faultservice.jpg"
+  alt=""></p>
 
   <p>Deployment time error message</p>
 
   <p align="center"><strong><img src="images/faultmsg.jpg"
   alt=""></strong></p>
 
-  <p>  </p>
+  <p> </p>
 
   <p>Axis2 Administration is all about configuring Axis2 at the run time and
   the configuration will be transient. More descriptions are available in <a
@@ -341,3 +624,4 @@
 </ol>
 </body>
 </html>
+>>>>>>> .r370149



Mime
View raw message