svn commit: r358491 - in /webservices/axis2/trunk/java/xdocs: images/servicegroups.jpg webadminguide.html

[ch...@apache.org]

Author: chinthaka
Date: Wed Dec 21 20:45:58 2005
New Revision: 358491

URL: http://svn.apache.org/viewcvs?rev=358491&view=rev
Log:
Applying Chatra's patch for web admin guide

Added:
    webservices/axis2/trunk/java/xdocs/images/servicegroups.jpg   (with props)
Modified:
    webservices/axis2/trunk/java/xdocs/webadminguide.html

Added: webservices/axis2/trunk/java/xdocs/images/servicegroups.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/images/servicegroups.jpg?rev=358491&view=auto
==============================================================================
Binary file - no diff available.

Propchange: webservices/axis2/trunk/java/xdocs/images/servicegroups.jpg
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Modified: webservices/axis2/trunk/java/xdocs/webadminguide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/webadminguide.html?rev=358491&r1=358490&r2=358491&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/webadminguide.html (original)
+++ webservices/axis2/trunk/java/xdocs/webadminguide.html Wed Dec 21 20:45:58 2005
@@ -12,7 +12,7 @@
 <h3>Introduction</h3>
 
 <p>Axis2 Web Administration Module provides a way to configure Axis2
-dynamically. Its important to note that this dynamic configuration will NOT
+dynamically. It's important to note that this dynamic configuration will NOT
 be persistent, i.e. if the servlet container is restarted then all the
 dynamic configuration changes will be lost.</p>
 
@@ -29,11 +29,11 @@
 <p align="left"><strong><img src="images/adminlogin.jpg"></strong></p>
 
 <p>You can change the username &amp; password values by changing following
-two parameters in server.xml as required.</p>
+two parameters in axis2.xml as required.</p>
 
 <p align="left"><strong><img src="images/parameters.jpg"></strong></p>
 
-<p>If the login is succeessful you will see the screenbelow. This is where
+<p>If the login is succeessful you will see the screen below. This is where
 you can view the configuration and the state of the running system and
 dynamically configure it.</p>
 
@@ -77,11 +77,11 @@
 
 <h3><a name="upservice">Upload Services</a></h3>
 
-<p>You can upload packaged Axis 2 axisService jar files using this page. This
-can be done in two simple steps:</p>
+<p>You can upload packaged Axis2<em> </em>service archive files using this
+page. This can be done in two simple steps:</p>
 <ul>
   <li>Browse to the location and select the axisService archive file you wish
-    toupload</li>
+    to upload</li>
   <li>then click Upload</li>
 </ul>
 
@@ -101,7 +101,7 @@
 
 <p>Service group is a logical collection of set of services and 'Available
 Service Groups' link will list all the available service groups in the system
-. </p>
+.</p>
 
 <p align="left"><strong><img src="images/servicegroups.jpg"></strong></p>
 
@@ -133,21 +133,21 @@
 </ul>
 
 <p>The main difference between these two levels is that system predefined
-phases will be invoked irrespective of the services. while user defined
+phases will be invoked irrespective of the services, while user defined
 phases will be invoked when the dispatcher finds the operation. Note that it
-is essential that module developers and service writers have a good
+is essential for module developers and service writers to have a good
 understanding of phases and phase ordering.</p>
 <img src="images/viewphases.jpg"> <br>
 
 
 <h3><a name="globalchains"></a>Global Chains</h3>
 
-<p>'Global Chains' link will display all the Global Execution Chains. 'The
+<p>'Global Chains' link will display all the Global Execution Chains. The
 most interesting feature of Axis2 Web Administratin Module is that it
 provides a very basic way of viewing the global phase list and handlers
 inside the phases depending on both phase and handler orders. This kind of
 information is extremely useful in debugging the system, as there is no other
-way to list out handlers in the global chains. And if you engage a new module
+way to list out handlers in the global chains. If you engage a new module,
 the new handlers will be added to the global chains and displayed on this
 page.</p>
 
@@ -167,14 +167,11 @@
 
 <h3><a name="engaginmodule"></a>Engaging Modules</h3>
 
-<p>'Engaging Modules' link allows to engage modules on all services across
-the system</p>
-
-<p>Modules can be engaged either globally, to a service or to an operation
-depending on the module implementation. If the module was designed to engage
-the handlers globally then handlers in the module can be included in any
-phase in the system. It can be either system predefined or user defined
-phase.</p>
+<p>'Engaging Modules' link allows to engage modules either globally (to all
+services), to a service group, to a service or to an operation depending on
+the module implementation. If the module was designed to engage the handlers
+globally then handlers in the module can be included in any phase in the
+system. It can be either system predefined or user defined phase.</p>
 
 <p>On the other hand, if the module was implemented in such a way that it is
 going to be deployed to a service or to an operation, then the module canNOT
@@ -209,7 +206,7 @@
 <h3><a name="viewhierarchy"></a>View Hierarchy</h3>
 
 <p>By listing current context hierarchy 'View Hierarchy' link provides a
-means to look at the run time system. Thiswill list out all the available
+means to look at the run time system. This will list out all the available
 service group contexts , service contexts , operation context and etc.</p>
 
 <p></p>