You are viewing a plain text version of this content. The canonical link for it is here.
Posted to axis-cvs@ws.apache.org by sa...@apache.org on 2007/04/30 07:43:24 UTC

svn commit: r533595 [2/6] - in /webservices/axis2/site/c: ./ docs/ docs/hello/client/ docs/mod_log/

Modified: webservices/axis2/site/c/docs/axis2c_manual.html
URL: http://svn.apache.org/viewvc/webservices/axis2/site/c/docs/axis2c_manual.html?view=diff&rev=533595&r1=533594&r2=533595
==============================================================================
--- webservices/axis2/site/c/docs/axis2c_manual.html (original)
+++ webservices/axis2/site/c/docs/axis2c_manual.html Sun Apr 29 22:43:23 2007
@@ -1,62 +1,67 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><title>Axis2/C - Apache Axis2/C Manual</title><style type="text/css" media="all">
           @import url("../style/maven-base.css");
           
-			    @import url("../style/maven-classic.css");</style><link rel="stylesheet" href="../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://www.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://www.apache.org/images/asf-logo.gif"></img></a><a href="http://ws.apache.org/axis2/c" id="projectLogo"><img alt="Apache Axis2 C" src="http://ws.apache.org/axis2/images/axis.jpg"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
-                	Last published: 22 December 2006
-                  | Doc for 0.96</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis2_C"><h5>Axis2/C</h5><ul><li class="none"><a href="../index.html">Home</a></li><li class="expanded"><a href="../download.cgi">Download Axis2/C</a><ul><li class="none"><a href="../download.cgi">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/c/" class="externalLink" title="External Link">View Source Code Online</a></li><li class="none"><a href="../svn.html">Checkout Source Code</a></li></ul></li><li class="expanded"><a href="../docs/index.html">Documentation</a><ul><li class="none"><a href="../docs/installationguide.html">Installation Guide</a></li><li class="none"><a href="../docs/developerguide.html">Developer Guide</a></li><li class="none"><a href="../docs/userguide.html">User Guide</a></li><li class="none"><a href="../docs/axis2c_manual.html">Axis2/C manual</a>
 </li></ul></li><li class="expanded"><a href="../mail-lists.html">Get Involved</a><ul><li class="none"><a href="../mail-lists.html">Mailing Lists</a></li></ul></li><li class="expanded"><a href="../team-list.html">Project Information</a><ul><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"><p style="margin-bottom: 0in">This document is intended to be a reference
-manual on <a href="http://ws.apache.org/axis2/c" class="externalLink" title="External Link">Apache Axis2/C</a> and
-covers its features and how to use it to provide and consume Web Services.
-Please send your feedback to Apache Axis2/C developer mailing list (<a href="mailto:axis-c-dev@apache.org">axis-c-dev@apache.org</a>)</p></div><div class="section"><a name="Axis2_C_Manual"></a><h2>Axis2/C Manual</h2><ol>
+			    @import url("../style/maven-classic.css");</style><link rel="stylesheet" href="../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://www.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://www.apache.org/images/asf-logo.gif"></img></a><a href="http://ws.apache.org/axis2/c" id="projectLogo"><img alt="Apache Axis2/C" src="http://ws.apache.org/axis2/images/axis.jpg"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
+                	Last published: 30 April 2007
+                  | Doc for 1.0.0</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis2_C"><h5>Axis2/C</h5><ul><li class="none"><a href="../index.html">Home</a></li><li class="expanded"><a href="../download.cgi">Download Axis2/C</a><ul><li class="none"><a href="../download.cgi">Releases</a></li></ul></li><li class="expanded"><a href="../docs/index.html">Documentation</a><ul><li class="none"><a href="../docs/installationguide.html">Installation Guide</a></li><li class="none"><a href="../docs/axis2c_manual.html">Axis2/C manual</a></li></ul></li><li class="expanded"><a href="../list.html">Get Involved</a><ul><li class="none"><a href="../list.html">Mailing Lists</a></li><li class="none"><a href="../svn.html">Checkout Source Code</a></li></ul></li><li class="expanded"><a href="../">Developer Guideline</a><ul><li class="none"><a href="../coding_conventions.html">Coding Convension</a></li><li class="none">
 <a href="../version.html">Versionning</a></li></ul></li><li class="expanded"><a href="../team-list.html">Project Information</a><ul><li class="none"><a href="../team-list.html">Project Team</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/c/" class="externalLink" title="External Link">Source Code</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="Preamble"></a><h2>Preamble</h2><p style="margin-bottom: 0in">This document is intended to be a reference
+manual for <a href="http://ws.apache.org/axis2/c" class="externalLink" title="External Link">Apache Axis2/C</a>. This
+manual details how Axis2/C can be used to provide and consume Web
+services.</p><p style="margin-bottom: 0in">Please send your feedback to the Apache Axis2/C
+developer mailing list (<a href="mailto:axis-c-dev@apache.org">axis-c-dev@apache.org</a>). Subscription
+details are available on the <a href="http://ws.apache.org/axis2/c/mail-lists.html" class="externalLink" title="External Link">Axis2 site</a>.</p><p>This document uses the following conventions:</p><ul>
+  <li>The directory each package is installed in is given with an
+    "_INSTALL_DIR" suffix to the package name. For example, the path in which
+    Libxml2 is installed is referred to as LIBXML2_INSTALL_DIR</li>
+</ul></div><div class="section"><a name="Axis2_C_Manual_-_Contents"></a><h2>Axis2/C Manual - Contents</h2><ol>
   <li><a href="#quick_start">Quick Start Guide</a></li>
-  <li><a href="#repo_fold">Repository Folder</a></li>
+  <li><a href="#repo_folder">Repository Folder</a></li>
   <li><a href="#svc_api">Service API</a></li>
-  <li><a href="#cli_api">Client API</a></li>
+  <li><a href="#client_api">Client API</a></li>
   <li><a href="#rest">REST</a></li>
   <li><a href="#mtom">MTOM</a></li>
-  <li><a href="#eng_mod">Engaging a Module</a></li>
-  <li><a href="#ws_add">WS-Addressing</a></li>
-  <li><a href="#wrt_mod">Writing a Module</a></li>
-  <li><a href="#sim_ser">Simple Axis Server</a></li>
-  <li><a href="#apa_mod">Deploying in Apache2</a></li>
+  <li><a href="#engaging_module">Engaging a Module</a></li>
+  <li><a href="#ws_addressing">WS-Addressing</a></li>
+  <li><a href="#writing_module">Writing a Module</a></li>
+  <li><a href="#simple_axis_server">Simple Axis Server</a></li>
+  <li><a href="#mod_axis2">Deploying with Apache2 HTTP Web Server</a></li>
+  <li><a href="#IIS">Deploying with Microsoft IIS Server</a></li>
   <li><a href="#ssl_client">Using SSL Client</a></li>
-  <li><a href="#appA">Appendix A  - axis2.xml</a></li>
-  <li><a href="#appB">Appendix B  - services.xml</a></li>
-  <li><a href="#appC">Appendix C  - module.xml</a></li>
-  <li><a href="#appD">Appendix D  - service client options</a></li>
-</ol><p><a name="quick_start"></a></p></div><div class="section"><a name="1__Quick_Start_Guide"></a><h2>1. Quick Start Guide</h2><p>This sections is aimed to help you to get a Web service up in quick time
-using Axis2/C and consume that service using an Axis2/C client.</p><p>First download the latest binary release form Apache Axis2/C</p><p><a href="http://ws.apache.org/axis2/c/download.cgi" class="externalLink" title="External Link">download page</a>. Once
-you download the correct binary that suits your platform, all that you
-require to get it running is to extract the package to a folder of your
-choice, set AXIS2C_HOME environment variable to point to this extracted
-folder. On Linux, you may have to set the LD_LIBRARY_PATH environment
-variable to include the lib folder (e.g. add $AXIS2C_HOME/lib). On Windows,
-you would have to add the lib folder to your PATH variable to include the
-Axis2/C dlls to your path. Now you should be able to cd to bin folder of this
-extracted folder and run the simple axis server in one command shell and cd
-to bin/samples in another command shell and run any of the samples there (you
-may have to set the environment variables in this new shell as well). Please
-see the <a href="http://ws.apache.org/axis2/c/docs/installationguide.html" class="externalLink" title="External Link">installation
-guide</a> for more details.
-
-</p><p><br></br>
-<br></br>
-</p><p>Once you have Axis2/C up and running successfully, you can start writing
-your own services and clients. The following sections detail how to write
-your first service and client with Axis2/C.</p><div class="subsection"><a name="1_1_Hello_Service"></a><h3>1.1 Hello Service</h3><p>Lets see how you could write your first Web service with Axis2/C and then
-how to deploy it.</p><p>The first service that we are going to write is named "hello" and would
-have a single operation named "greet" in the service. This "greet" operation,
-when invoked by client, would expect the client to send a greeting in the
-request, and would in turn send a greeting in the response. Following are
-example XML payloads exchanged between the client and the service:</p><p>Request:</p>
-    <div class="source"><pre>&lt;greet&gt;
-    Hello Service!
-&lt;greet&gt;
+  <li><a href="#proxy">Using Proxy Support</a></li>
+  <li><a href="#wsdl2c">WSDL2C Tool</a></li>
+  <li><a href="#appA">Appendix A - axis2.xml</a></li>
+  <li><a href="#appB">Appendix B - services.xml</a></li>
+  <li><a href="#appC">Appendix C - module.xml</a></li>
+  <li><a href="#appD">Appendix D - service client options</a></li>
+</ol><p><a name="quick_start"></a></p></div><div class="section"><a name="1__Quick_Start_Guide"></a><h2>1. Quick Start Guide</h2><p>This section is aimed to help you get a Web service running in a short
+time using Axis2/C, and consume that service using an Axis2/C client.</p><p>First, <a href="http://ws.apache.org/axis2/c/download.cgi" class="externalLink" title="External Link">download</a>
+the latest binary release from Apache Axis2/C. Once you download the correct
+binary that suits your platform, all that you require to get it running is to
+extract the package to a folder of your choice, and set the AXIS2C_HOME
+environment variable to point to this extracted folder. For Linux, you may
+have to set the LD_LIBRARY_PATH environment variable to include the lib
+folder (e.g. add $AXIS2C_HOME/lib). For MS Windows, you will have to add the
+lib folder to your PATH variable to include the Axis2/C DLLs to your path.</p><p>Now you should be able to change the directory to the bin folder of the
+extracted folder, and run the simple axis server in one command shell. Then
+change the directory to bin/samples in another command shell and run any of
+the samples there (you may have to set the environment variables in this new
+shell as well). Please see the <a href="http://ws.apache.org/axis2/c/docs/installationguide.html" class="externalLink" title="External Link">installation
+guide</a> for more details.</p><p>Once you have Axis2/C up and running successfully, you can start writing
+your own services and clients. The following sections explain how to write
+your first service and client with Axis2/C.</p><div class="subsection"><a name="1_1_Hello_Service"></a><h3>1.1 Hello Service</h3><p>Let's see how you can write your first Web service with Axis2/C and how to
+deploy it.</p><p>The first service that we are going to write is named "hello" with a
+single operation named "greet" in the service. This "greet" operation, when
+invoked by the client, will expect the client to send a greeting in the
+request, and in turn send a greeting in the response. Following are examples
+of XML payloads exchanged between the client and the service:</p><p>Request:</p>
+    <div class="source"><pre>   &lt;greet&gt;
+        Hello Service!
+   &lt;greet&gt;
 
 </pre></div>
   <p>Response:</p>
-    <div class="source"><pre>&lt;greetResponse&gt;
-    Hello Client!
-&lt;greetResponse&gt;
+    <div class="source"><pre>   &lt;greetResponse&gt;
+        Hello Client!
+   &lt;greetResponse&gt;
 </pre></div>
   <br></br><p>The steps to be followed when implementing a service with Axis2/C
 include:</p><ol>
@@ -64,120 +69,61 @@
     service.</b> <br></br>
     In our sample, we will have one function that implements the "greet"
     operation. <br></br>
-    We would name that function "axis2_hello_greet".</li>
-  <li><b>Implement the functions defined by the axis2_svc_skeleton
-    interface</b><br></br>
-    axis2_svc_skeleton interface expects the functions free and invoke to be
-    implemented by our service.<br></br>
-    In our sample, we would implement those and name them as hello_free, and
-    hello_invoke respectively.<br></br>
+    We will name that function <code>axis2_hello_greet</code>.</li>
+  <li><b>Implement the functions defined by the
+    <code>axis2_svc_skeleton</code> interface</b><br></br>
+    <code>axis2_svc_skeleton</code> interface expects the functions
+    <code>init</code>, <code>invoke</code>, <code>on_fault</code> and
+    <code>free</code> to be implemented by our service.<br></br>
+    In our sample, we would implement those and name them as
+    <code>hello_init</code>, <code>hello_invoke</code>,
+    <code>hello_on_fault</code> and <code>hello_free</code> respectively.<br></br>
   </li>
-  <li><b>Implement the create function, that would create an instance of
+  <li><b>Implement the create function, that would create an instance of the
     service skeleton</b><br></br>
     The create function would create an axis2_svc_skeleton and assign the
     respective function pointers to map the axis2_svc_skeleton interface to
-    our interface implementation methods explained in above step<br></br>
+    our interface implementation methods explained in the above step.<br></br>
   </li>
   <li><b>Implement axis2_get_instance and axis2_remove_instance
     functions</b><br></br>
-    Those functions are used to create and destroy service instances by the
-    engine, and each service must define those functions.<br></br>
+    These functions are used to create and destroy service instances by the
+    engine, and each service must define these functions.<br></br>
   </li>
   <li><b>Write the services.xml file for the service</b><br></br>
-    services.xml file acts as the deployment descriptor file for the service.
-    As the bare minimum, we need to configure the service name, operations
-    and the shared library file name containing the service implementation in
-    this file.<br></br>
-    As we have already decided, we would name the service "hello", the
-    operation "greet" and the shared library libhello.so on Linux and
-    hello.dll on Windows.<br></br>
+    The services.xml file acts as the deployment descriptor file for the
+    service. As the bare minimum, we need to configure the service name,
+    operations, and the shared library file name containing the service
+    implementation in this file.<br></br>
+    As previously decided, we will name the service "hello", the operation
+    "greet" and the shared library libhello.so on Linux and hello.dll on MS
+    Windows.<br></br>
   </li>
-</ol></div><div class="subsection"><a name="1_1_1_Operation_Implementation"></a><h3>1.1.1 Operation Implementation</h3><p>Following is the implementation of the greet operation:</p>
-    <div class="source"><pre>axiom_node_t *
-axis2_hello_greet(const axis2_env_t *env, axiom_node_t *node)
-{
-    axiom_node_t *client_greeting_node = NULL;
-    axiom_node_t *return_node = NULL;
-
-    AXIS2_ENV_CHECK(env, NULL);
-
-    if (node)
-    {
-        client_greeting_node = AXIOM_NODE_GET_FIRST_CHILD(node, env);
-        if (client_greeting_node &amp;&amp; 
-        AXIOM_NODE_GET_NODE_TYPE(client_greeting_node, env) == AXIOM_TEXT)
-        {
-            axiom_text_t *greeting = 
-            (axiom_text_t *)AXIOM_NODE_GET_DATA_ELEMENT(client_greeting_node, env);
-            if (greeting &amp;&amp; AXIOM_TEXT_GET_VALUE(greeting , env))
-            {
-                axis2_char_t *greeting_str = AXIOM_TEXT_GET_VALUE(greeting, env);
-                printf("Client greeted saying \"%s\" \n", greeting_str);
-                return_node = build_greeting_response(env, "Hello Client!");
-            }
-        }
-    }
-    else
-    {
-        AXIS2_ERROR_SET(env-&gt;error, 
-        AXIS2_ERROR_SVC_SKEL_INVALID_XML_FORMAT_IN_REQUEST, AXIS2_FAILURE);
-        printf("ERROR: invalid XML in request\n");
-        return_node = build_greeting_response(env, "Client! Who are you?");
-    }
-
-    return return_node;
-}
-</pre></div>
-  <br></br><p>This function implements the business logic for the greet operation. We
-would be calling this function from our implementation of the invoke
-function. Basically this function receives the request payload as an
-axiom_node, process it to understand the request logic and prepares the
-response as an axiom_node and returns that.</p></div><div class="subsection"><a name="1_1_2_Skeleton_Create_Method"></a><h3>1.1.2 Skeleton Create Method</h3><p>Service skeleton creation could be implemented like the following:</p>
-    <div class="source"><pre>axis2_svc_skeleton_t *
-axis2_hello_create(const axis2_env_t *env)
-{
-    axis2_svc_skeleton_t *svc_skeleton = NULL;
-    svc_skeleton = AXIS2_MALLOC(env-&gt;allocator,
-            sizeof(axis2_svc_skeleton_t));
-
-    svc_skeleton-&gt;ops = AXIS2_MALLOC(
-                env-&gt;allocator, sizeof(axis2_svc_skeleton_ops_t));
-
-    svc_skeleton-&gt;func_array = NULL;
-    svc_skeleton-&gt;ops-&gt;free = hello_free;
-    svc_skeleton-&gt;ops-&gt;invoke = hello_invoke;
-
-    return svc_skeleton;
-}
-</pre></div>
-  <br></br><p>The create function creates and returns a new axis2_svc_skeleton instance.
-The most important aspect to notice about this function is the function
-pointer assignments to map the interface operations to the corresponding
-functions of our implementation.</p><br></br></div><div class="subsection"><a name="1_1_3_Invoking_Operation_Implementation"></a><h3>1.1.3 Invoking Operation Implementation</h3></div><div class="subsection"><p>The invoke method of the service skeleton is the point of entry for
+</ol></div><div class="subsection"><a name="1_1_1_Operation_Implementation"></a><h3>1.1.1 Operation Implementation</h3><p>Look for the <code>axis2_hello_greet</code> function in the <a href="hello/service/hello_svc.c.html">hello_svc.c</a> source file.</p><p>This function implements the business logic for the greet operation. We
+will be calling this function from our implementation of the invoke function.
+Basically, this function receives the request payload as an
+<code>axiom_node</code>, process it to understand the request logic, and
+prepares the response as an <code>axiom_node</code> and returns that.</p></div><div class="subsection"><a name="1_1_2_Skeleton_Create_Method"></a><h3>1.1.2 Skeleton Create Method</h3><p>Look for the <code>axis2_hello_create</code> function in the <a href="hello/service/hello_svc.c.html">hello_svc.c</a> source file.</p><p>The create function creates and returns a new
+<code>axis2_svc_skeleton</code> instance. The most important aspect to note
+about this function is the function pointer assignments. They are used to map
+the interface operations to the corresponding functions of the
+implementation. This is done by assigning the ops member of the service
+skeleton to the address of the ops struct variable.</p></div><div class="subsection"><a name="1_1_3_Invoking_Operation_Implementation"></a><h3>1.1.3 Invoking Operation Implementation</h3><p>The invoke method of the service skeleton is the point of entry for
 invoking the operations. Hence in our implementation of the invoke function,
-we have to define how the operations are to be called.</p>
-    <div class="source"><pre>axiom_node_t* AXIS2_CALL
-hello_invoke(axis2_svc_skeleton_t *svc_skeleton,
-        const axis2_env_t *env,
-        axiom_node_t *node,
-        axis2_msg_ctx_t *msg_ctx)
-{
-    return axis2_hello_greet(env, node);
-}
-</pre></div>
-  <br></br><p>In our implementation of the hello_invoke, we call the function
-implementing the greet operation. As we have only one operation, the task is
-simple here. If we had multiple operations, we would have to look into the
-information in message context to map to the exact operation. <br></br>
-Axis2/C engine would call the invoke method with an axiom_node, containing
-the request payload and axis2_msg_ctx instance containing the message context
-information, in addition to service skeleton and environment pointers. We
-could use the message context to extract whatever information we deem
-necessary related to the incoming message. The Axis2/C engine expects the
-invoke method to return a pointer to an axiom_node, representing the response
-payload.</p></div><div class="subsection"><a name="1_1_4_Full_Source"></a><h3>1.1.4 Full Source</h3><p>Here is the complete source code for the service : <a href="hello/service/hello.c.html">hello.c</a></p><br></br></div><div class="subsection"><a name="1_1_5_Service_Descriptor"></a><h3>1.1.5 Service Descriptor</h3><p>services.xml file contains details on the service that would be read by
-the Axis2/C deployment engine during deployment time. Following shows the
-contents for the services.xml file for hello service.</p>
+we have to define how the operations are to be called.</p><p>Look for the <code>hello_invoke</code> function in the <a href="hello/service/hello_svc.c.html">hello_svc.c</a> source file.</p><p>In our implementation of the <code>hello_invoke</code>, we call the
+function implementing the greet operation. As we have only one operation, the
+task is simple here. If we had multiple operations, we will have to look into
+the information in the message context to map it to the exact operation. <br></br>
+The Axis2/C engine will call the invoke method with an
+<code>axiom_node</code>, containing the request payload, and
+<code>axis2_msg_ctx</code> instance, containing the message context
+information, in addition to the service skeleton and the environment
+pointers. We can use the message context to extract whatever information we
+deem necessary that is related to the incoming message. The Axis2/C engine
+expects the invoke method to return a pointer to an <code>axiom_node</code>,
+representing the response payload.</p></div><div class="subsection"><a name="1_1_4_Full_Source"></a><h3>1.1.4 Full Source</h3><p>Here is the complete source code for the service : <a href="hello/service/hello_svc.c.html">hello_svc.c</a></p></div><div class="subsection"><a name="1_1_5_Service_Descriptor"></a><h3>1.1.5 Service Descriptor</h3><p>The services.xml file contains details on the service that would be read
+by the Axis2/C deployment engine during server start up time. The following
+shows the contents for the services.xml file for the hello service.</p>
     <div class="source"><pre>&lt;service name="hello"&gt;
    &lt;parameter name="ServiceClass" locked="xsd:false"&gt;hello&lt;/parameter&gt;
    &lt;description&gt;
@@ -189,453 +135,377 @@
 </pre></div>
   <p>The service configuration shown above specifies that the name of the
 service is hello. <br></br>
-The value of the "serviceclass" , "hello" in this case, will be mapped to the
+The value of the "ServiceClass", "hello" in this case, will be mapped to the
 service implementation by the deployment engine as libhello.so on Linux or
-hello.dll on windows.<br></br>
-description element contains a brief description of the service. <br></br>
+hello.dll on MS Windows. The description element contains a brief description
+of the service. <br></br>
 There can be one or more operation elements. For this sample, we only have
-one operation, with the name "greet"<br></br>
+one operation, with the name "greet".<br></br>
 </p></div><div class="subsection"><a name="1_1_6_Compiling_the_Service"></a><h3>1.1.6 Compiling the Service</h3><p>You can compile the service sample as shown below.</p><p>On Linux:</p>
-    <div class="source"><pre>gcc -shared -olibhello.so -I$AXIS2C_HOME/include -L$AXIS2C_HOME/lib -laxis2 hello.c
+    <div class="source"><pre>gcc -shared -olibhello.so -I$AXIS2C_HOME/include/axis2-1.0/ -L$AXIS2C_HOME/lib -laxis2 hello_svc.c 
+
+</pre></div>
+  <p>On MS Windows:</p><p>to compile,</p>
+    <div class="source"><pre>cl.exe /D "WIN32" /D "_WINDOWS" /D "_MBCS" /D "AXIS2_DECLARE_EXPORT" /D "AXIS2_SVR_MULTI_THREADED" /w /nologo /I  %AXIS2C_HOME%\include /c hello_svc.c
 
 </pre></div>
-  <p>On Windows</p><p>to compile,</p>
-    <div class="source"><pre>cl.exe /D "WIN32" /D "_WINDOWS" /D "_MBCS"/D"AXIS2_DECLARE_EXPORT" 
-/D "AXIS2_SVR_MULTI_THREADED" /w /nologo $(AXIS2_INCLUDE_PATH)
-$(APACHE_INCLUDE_PATH) /I hello.c
+  <p>to link,</p>
+    <div class="source"><pre>link.exe /nologo /LIBPATH:%AXIS2C_HOME%\lib axutil.lib axiom.lib axis2_parser.lib axis2_engine.lib /DLL /OUT:hello.dll *.obj
 
 </pre></div>
-  </div><div class="subsection"><a name="1_1_7_Deploying_the_Service"></a><h3>1.1.7 Deploying the Service</h3><p>In order to make the service available to be consumed by clients, we have
-to deploy the service. To deploy the service, you have to create a folder in
-AXIS2C_HOME/services folder named hello and copy the services.xml file and
-the shared library file (libhello.so on Linux or hello.dll on Windows) into
-that folder</p><p>To verify that your service has been correctly deployed, you can start the
+  </div><div class="subsection"><a name="1_1_7_Deploying_the_Service"></a><h3>1.1.7 Deploying the Service</h3><p>To make the service available to be consumed by the clients, we have to
+deploy the service. To deploy the service, you have to create a folder named
+'hello' in the AXIS2C_HOME/services folder, and copy the services.xml file
+and the shared library file (libhello.so on Linux or hello.dll on MS Windows)
+into that folder.</p><p>To verify that your service has been correctly deployed, you can start the
 simple axis server and then browse the list of deployed services using a Web
-browser. To start the simple axis server you can go to AXIS2C_HOME/bin folder
-and run the executable axis2_http_server. The default url that you can test
-the service list with is <a href="http://localhost:9090/axis2/services" class="externalLink" title="External Link">http://localhost:9090/axis2/services</a>.You
-should get an entry for the hello service on the page that you get.</p><p><br></br>
-<br></br>
-</p></div><div class="subsection"><a name="1_2_Hello_Client"></a><h3>1.2 Hello Client</h3><p>Now that you know how to write a service with Axis2/C, lets see how you
-could write a client to consume that service. The request payload that the
-client would be sending to the service was described in the previous section.
-The client has to prepare the payload, send it to the service and then
-receive and process the response.</p><p>The steps to be followed when implementing a client with Axis2/C
-include:</p><ol>
+browser. To start the simple axis server, you can go to the AXIS2C_HOME/bin
+folder and run the executable axis2_http_server. The default URL that you can
+test the service list with is <a href="http://localhost:9090/axis2/services" class="externalLink" title="External Link">http://localhost:9090/axis2/services</a>.
+You should get an entry for the hello service on the page that is
+displayed.</p></div><div class="subsection"><a name="1_2_Hello_Client"></a><h3>1.2 Hello Client</h3><p>Now that you know how to write a service with Axis2/C, let's see how to
+write a client to consume that service. The request payload that the client
+will be sending to the service was described in the previous section. The
+client has to prepare the payload, send it to the service, and then receive
+and process the response.</p><p>The steps to be followed when implementing a client with Axis2/C:</p><ol>
   <li><b>Create the environment to be used by the client.</b> <br></br>
     Each function in Axis2/C takes a pointer to the environment instance that
-    encapsulates memory allocators, error handler, logging and threading
-    mechanisms. axis2_env_create_all method can be used to create a default,
-    ready to use environment instance.<br></br>
+    encapsulates the memory allocator, error handler, and logging and
+    threading mechanisms. The <code>axutil_env_create_all</code> method can
+    be used to create a default, ready to use environment instance.<br></br>
   </li>
-  <li><b>Create an options instance, and set options</b><br></br>
-    axis2_options struct can be used to set the client side options. As an
-    example, we can use options to set the endpoint address of the service to
-    be consumed by the client.</li>
+  <li><b>Create an options instance, and set options</b>.<br></br>
+    The<code> axis2_options</code> struct can be used to set the client side
+    options. For example, we can use options to set the endpoint address of
+    the service to be consumed by the client.</li>
   <li><b>Create a service client instance, giving the client repository
     folder as a parameter.</b><br></br>
-    axis2_svc_client struct is meant to be used by users for consuming
-    services. It provides an easy to use API. Service client create method
-    takes the location of the repository as a parameter. For the purpose of
-    our sample, you can use the AXIS2C_HOME as the repository. The concept of
-    <a href="#repo_fold">repository</a> is explained in detail in a later
-    section.<br></br>
+    The<code> axis2_svc_client</code> struct is meant to be used by the users
+    to consume Web services. It provides an easy to use API. Service client
+    create method takes the location of the repository as a parameter. For
+    the purpose of our sample, you can use the AXIS2C_HOME as the repository.
+    The concept of <a href="#repo_folder">repository</a> is explained in
+    detail in a later section.<br></br>
   </li>
   <li><b>Set options to service client instance</b><br></br>
-    The options created in an earlier step needs to be set on the service
-    client, indicating that options are meant to be used by the service
+    The options created in an earlier step have to be set on the service
+    client, indicating the options that are meant to be used by the service
     client.<br></br>
   </li>
   <li><b>Send the request and receive the response</b><br></br>
-    Service client's AXIS2_SVC_CLIENT_SEND_RECEIVE macro could be used to
-    invoke the send receive operation on the service client instance.<br></br>
-    The send receive operation takes the request payload as an axiom_node and
-    returns the response payload as an axiom_node.</li>
+    The service client's <code>axis2_svc_client_send_receive</code> method
+    can be used to invoke the send receive operation on the service client
+    instance.<br></br>
+    The send receive operation takes the request payload as an
+    <code>axiom_node</code> and returns the response payload as an
+    <code>axiom_node</code>.</li>
   <li><b>Process the response</b><br></br>
     Process the response in line with the client business logic.</li>
 </ol></div><div class="subsection"><a name="1_2_1_Creating_and_Setting_Options"></a><h3>1.2.1 Creating and Setting Options</h3>
     <div class="source"><pre>    options = axis2_options_create(env);
     address = "http://localhost:9090/axis2/services/hello";
     endpoint_ref = axis2_endpoint_ref_create(env, address);
-    AXIS2_OPTIONS_SET_TO(options, env, endpoint_ref);
+    axis2_options_set_to(options, env, endpoint_ref);
 
 </pre></div>
-  <p>In the above shown section of code, an axis2_options instance is created
-first. Then an endpoint reference instance is created with the address of the
-location of the service. Finally, the created endpoint is set as the "to"
-address of the options. The "to" address indicates where the request should
-be sent to.</p><br></br></div><div class="subsection"><a name="1_2_2_Using_Service_Client"></a><h3>1.2.2 Using Service Client</h3>
+  <p>In the above section of code, an <code>axis2_options</code> instance is
+created first. Then an endpoint reference instance is created with the
+address of the location of the service. Finally, the created endpoint is set
+as the "to" address of the options. The "to" address indicates where the
+request should be sent to.</p></div><div class="subsection"><a name="1_2_2_Using_Service_Client"></a><h3>1.2.2 Using Service Client</h3>
     <div class="source"><pre>    svc_client = axis2_svc_client_create(env, client_home);
-    AXIS2_SVC_CLIENT_SET_OPTIONS(svc_client, env, options);
+    axis2_svc_client_set_options(svc_client, env, options);
     payload = build_om_request(env);
-    ret_node = AXIS2_SVC_CLIENT_SEND_RECEIVE(svc_client, env, payload);
+    ret_node = axis2_svc_client_send_receive(svc_client, env, payload);
 
 </pre></div>
   <p>After creating and preparing the options, the next step is to create a
 service client instance and use it to send the request and receive the
-response. The code fragment given above shows how options could be set on top
-of service client and how to invoke the send receive operation with request
-payload. Once the response is received, the response payload would be stored
-in the ret_node, which is a pointer to an axiom_node and that could be used
-to further process the response.</p><br></br></div><div class="subsection"><a name="1_2_3_Full_Source"></a><h3>1.2.3 Full Source</h3><p>Here is the complete source code for the client : <a href="hello/client/hello.c.html">hello.c</a></p><br></br></div><div class="subsection"><a name="1_2_4_Compiling_the_Client"></a><h3>1.2.4 Compiling the Client</h3><p>You can compile the client sample as shown below.</p><p>On Linux:</p>
+response. The code fragment given above shows how options can be set on top
+of the service client and how to invoke the send receive operation with a
+request payload. Once the response is received, the response payload will be
+stored in the <code>ret_node</code>, which is a pointer to an
+<code>axiom_node</code> that can be used to process the response further.</p></div><div class="subsection"><a name="1_2_3_Full_Source"></a><h3>1.2.3 Full Source</h3><p>Here is the complete source code for the client : <a href="hello/client/hello.c.html">hello.c</a></p></div><div class="subsection"><a name="1_2_4_Compiling_the_Client"></a><h3>1.2.4 Compiling the Client</h3><p>You can compile the client sample as shown below.</p><p>On Linux:</p>
     <div class="source"><pre>gcc -o hello -I$AXIS2C_HOME/include -L$AXIS2C_HOME/lib -laxis2 hello.c
 
 </pre></div>
-  <p>On Windows</p><p>to compile,</p>
-    <div class="source"><pre>cl.exe /nologo /D "WIN32" /D "_WINDOWS" /D "_MBCS" $(AXIS2_INCLUDE_PATH) hello.c /c 
+  <p>On MS Windows:</p><p>to compile,</p>
+    <div class="source"><pre>cl.exe /nologo /D "WIN32" /D "_WINDOWS" /D "_MBCS" /I %AXIS2C_HOME%\include /c hello.c
 
 </pre></div>
   <p>to link,</p>
-    <div class="source"><pre>link.exe /nologo /LIBPATH:$(AXIS2_LIBS)
-/LIBPATH:$(LIBXML2_INSTALL_DIR)\lib
-/LIBPATH:$(APACHE_INSTALL_DIR)\lib 
-/LIBPATH:$(ZLIB_INSTALL_DIR)\lib *.obj $(AXIS2_UTIL).lib $(AXIOM).lib
-$(AXIS2_PARSER).lib $(LIBS) $(AXIS2_ENGINE).lib  /OUT:hello.exe
+    <div class="source"><pre>link.exe /LIBPATH:%AXIS2C_HOME%\lib axutil.lib axiom.lib axis2_parser.lib axis2_engine.lib /OUT:hello.exe *.obj
 
 </pre></div>
-  </div><div class="subsection"><a name="1_2_5_Running_the_Client"></a><h3>1.2.5 Running the Client</h3><p>To run the client, make sure you have started the simple axis server and
-run the hello executable.</p><p style="margin-bottom: 0in"><br></br>
-</p><p><a name="repo_fold"></a></p></div></div><div class="section"><a name="2__Repository_Folder"></a><h2>2. Repository Folder</h2><p>Repository is a folder where all Axis2/C related configuration as well as
+  </div><div class="subsection"><a name="1_2_5_Running_the_Client"></a><h3>1.2.5 Running the Client</h3><p>To run the client, make sure you start the simple axis server and then run
+the hello executable.</p><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="repo_folder"></a></p></div></div><div class="section"><a name="2__Repository_Folder"></a><h2>2. Repository Folder</h2><p>Repository is a folder where all Axis2/C related configurations as well as
 services and modules are located. The following shows the folder structure of
-the repository:</p><img src="images/axis2c_repo.gif" alt=""></img><p>Here the name of the repository folder is axis2c_repo. On your system, you
-can choose this to be any folder name of your choice. There are three sub
-folders possible in the repository. In addition to that, the axis2.xml
-configuration file is also located in the repository. Following table
-describes the purpose of repository contents.</p><table class="bodyTable"><caption>Axis2/C Repository Subfolders</caption><tbody>
+the repository:</p><img src="images/axis2c_repo.gif" alt=""></img><p>Here the name of the repository folder is axis2c_repo. In your system, you
+can specify any folder name of your choice. There are three sub folders
+available in the repository. In addition to that, the axis2.xml configuration
+file is also located in the repository. The following table describes the
+purpose of the repository contents.</p><table class="bodyTable"><caption>Axis2/C Repository Sub-folders</caption><tbody>
     <tr class="a"><th>Folder Name</th><th>Description</th></tr>
     <tr class="b"><td><p>lib</p>
-      </td><td><p>lib folder contains the libraries required to run Axis2/C
-        engine. While you can afford to have the shared libs of Axis2/C in a
-        location of your choice, the dynamically loaded shared libs, parser,
-        transport receiver and transport sender has to be there in the
-        repository lib folder. <br></br>
+      </td><td><p>The lib folder contains the libraries required to run the
+        Axis2/C engine. While you can afford to have the shared libs of
+        Axis2/C in a location of your choice, the dynamically loaded shared
+        libs, parser, transport receiver and transport sender has to be in
+        the repository lib folder. <br></br>
         It is mandatory that the lib folder is there in the repository.</p>
       </td></tr>
     <tr class="a"><td><p>modules</p>
-      </td><td><p>modules folder contains the modules deployed with Axis2/C. Each
-        module deployed would have its own sub folder inside modules folder.
-        As an example, if addressing module is deployed, then there would be
-        a sub folder named addressing inside the modules folder of the
-        repository.<br></br>
-        In deployment time, Axis2/C deployment engine would traverse this
+      </td><td><p>The modules folder contains the modules deployed with Axis2/C.
+        Each module deployed will have its own sub folder inside the modules
+        folder. For example, if the addressing module is deployed, then there
+        will be a sub folder named addressing inside the modules folder of
+        the repository.<br></br>
+        At deployment, the Axis2/C deployment engine would traverse the
         modules folders to find out what modules are available.<br></br>
-        modules folder is optional. If it is empty or non-existent, that
+        The modules folder is optional. If it is empty or non-existent, that
         means that there are no deployed modules.</p>
       </td></tr>
     <tr class="b"><td><p>services</p>
-      </td><td><p>services folder contains the services deployed with Axis2/C.
-        Each service deployed would have its own sub folder inside services
-        folder, or would live inside one of the sub folders.<br></br>
-        In deployment time, Axis2/C deployment engine would traverse this
+      </td><td><p>The services folder contains the services deployed with Axis2/C.
+        Each service deployed will have its own sub folder inside the
+        services folder, or live inside one of the sub folders.<br></br>
+        At deployment, the Axis2/C deployment engine will traverse the
         services folders to find out what services are available.<br></br>
-        services folder is optional. If it is empty or non-existent, that
+        The services folder is optional. If it is empty or non-existent, that
         means that there are no deployed services.</p>
       </td></tr>
     <tr class="a"><td><p>axis2.xml</p>
-      </td><td><p>axis2.xml file is the configuration file of Axis2/C.<br></br>
+      </td><td><p>The axis2.xml file is the configuration file of Axis2/C.<br></br>
         The configuration file is mandatory and must have the name axis2.xml.
-        It is safe to consider your Axis2/C repository to be the folder where
-        you have the axis2.xml file.</p>
+        It is safe to consider your Axis2/C repository to be the folder in
+        which you have the axis2.xml file.</p>
       </td></tr>
-  </tbody></table><p>Both clients as well as services written using Axis2/C could use the same
-repository. However one can use one repository for the server side and
-another one for the client side. The services folder makes sense, only when
-the repository is used by the server side. When the repository is used by the
-client, services folder, if present, would not be useful.</p><p>The Axis2/C binary distribution, when extracted, could be considered ready
-to be used as your repository folder. If you are building Axis2/C from source
-distribution, when you build the source, including the samples, the
-installation destination would be ready to be used as your repository
-folder.</p><p>The simple axis server (that is axis2_http_server binary), the client
-samples as well as the httpd module (Axis2 Apache2 module) requires the
-repository folder to be specified in order to run correctly.</p><p></p><div class="subsection"><a name="2_1_Module_Folders"></a><h3>2.1 Module Folders</h3><p>As described earlier, all modules are placed inside modules folder of the
-repository and each module would have its own sub folder within modules
-folder.<br></br>
+  </tbody></table><p>Both clients as well as the services written using Axis2/C can use the
+same repository. However you can use one repository for the server side and
+another one for the client side. The services folder is used only when the
+repository is used by the server side. When the repository is used by the
+client, the services folder, if present, will not be used.</p><p>The Axis2/C binary distribution, when extracted, can be considered as
+ready for use as your repository folder. If you are building Axis2/C from the
+source distribution, when you build the source, including the samples, the
+installation destination will be ready for use as your repository folder.</p><p>The simple axis server (that is axis2_http_server binary), the client
+samples, and the HTTPD module (Axis2 Apache2 module) require the repository
+folder to be specified in order to run correctly.</p><p></p><div class="subsection"><a name="2_1_Module_Folders"></a><h3>2.1 Module Folders</h3><p>As described earlier, all the modules are placed inside the modules folder
+of the repository, and each module will have its own sub folder within the
+modules folder.<br></br>
 The folder in which a module is placed must have the same name as the module
-name. As an example, the addressing module would be placed in a sub folder
-named addressing.<br></br>
+name. For example, the addressing module will be placed in a sub folder named
+addressing.<br></br>
 </p><p>Inside the folder corresponding to a module, the shared library
-implementing the module and the module configuration file, module.xml, would
-be placed. It is a must that inside each folder representing a module that
-these two files are present. module.xml file would be processed by the
-deployment engine to find out module specific information such as module
-name, set of handlers and the flows into which those handlers are to be added
-etc.</p></div><div class="subsection"><a name="2_1_Service_Folders"></a><h3>2.1 Service Folders</h3><p>All services are placed inside services folder of the repository and each
-service would be in one of the sub folders within services folder. Axis2/C
-has a concept called service groups, where there could be one or more
-services inside a service group. A single stand alone service would be
+implementing the module and the module configuration file, module.xml, is
+placed. It is a must that these two files are present inside each folder
+representing a module. The module.xml file will be processed by the
+deployment engine to find out module specific information such as the module
+name, set of handlers, the flows into which those handlers are to be added,
+etc.</p></div><div class="subsection"><a name="2_1_Service_Folders"></a><h3>2.1 Service Folders</h3><p>All the services are placed inside the services folder of the repository,
+and each service will be in one of the sub folders within the services
+folder. Axis2/C has a concept called service groups, where there can be one
+or more services inside a service group. A single stand alone service is
 assigned a service group with the same name as that of the service by the
-Axis2/C engine for the purpose of easy handling. For this reason, sub folders
-in services folder correspond to service groups.</p><p>A service, if deployed as a stand alone service, would live inside a
-folder with the same name as that of the service. As an example, the echo
-service would be placed in a sub folder named echo. Inside the folder
-corresponding to a service, the shared library implementing the service and
-the service configuration file, services.xml, would be placed. It is because
-of the fact that the engine treats the folders to represent service groups
+Axis2/C engine for the purpose of easy handling. Therefore the sub folders in
+the services folder correspond to the service groups.</p><p>A service, if deployed as a stand alone service, will reside inside a
+folder with the same name as that of the service. For example, the echo
+service will be placed in a sub folder named echo. The shared library
+implementing the service and the service configuration file, the
+services.xml, will be placed inside the folder corresponding to a service.
+Given the fact that the engine treats the folders to represent service groups
 and not a single service, the configuration file is called services.xml.
-However, it is alway possible to place a single service inside a single
-folder, as that is the most common use case.</p><p>Each sub folder within the services folder should have at least one shared
+However, you can always place a single service inside a single folder, which
+is the most common use case.</p><p>Each sub folder within the services folder should have at least one shared
 lib implementing a service and a services.xml file. If it is a real service
-group, there could be multiple shared libs, yet only one services.xml file
-configuring all those services. services.xml file would be processed by the
-deployment engine to find out service group and service specific information
-such as service group name, service name, set of operations for each service
-etc.</p><p><a name="svc_api"></a></p></div></div><div class="section"><a name="3__Service_API"></a><h2>3. Service API</h2><p>We have already seen how to write a service in quick start guide section
-of this manual. This section would cover the service API of Axis2/C in a bit
-more detail.</p><p>The axis2_svc_skeleton is an interface. Axis2/C does not provide any
-concrete implementation of this interface. It is the responsibility of the
-service implementer to implement this interface. To implement the interface,
-one should implement functions adhering to the function pointer signatures of
-the members of axis2_svc_skeleton_ops struct. Then, a create function should
-be written, to create an axis2_svc_skeleton instance, and assign the
-implementing functions to members of the ops member of service skeleton.</p><p>The following table details the function signatures to be implemented by a
-service.</p><table class="bodyTable"><caption></caption><tbody>
+group, there will be multiple shared libs, yet there is only one services.xml
+file configuring all those services. The services.xml file is processed by
+the deployment engine to find out the service group and the service specific
+information such as the service group name, service name, the set of
+operations for each service, etc.</p><p><a name="svc_api"></a></p></div></div><div class="section"><a name="3__Service_API"></a><h2>3. Service API</h2><p>We have already seen how to write a service in the Quick Start Guide
+section of this manual. This section covers the service API of Axis2/C in
+more detail.</p><p><code>axis2_svc_skeleton</code> is an interface. Axis2/C does not provide
+any concrete implementation of this interface. It is the responsibility of
+the service implementer to implement this interface. To implement the
+interface, you should implement the functions adhering to the function
+pointer signatures of the members of the <code>axis2_svc_skeleton_ops</code>
+struct. Then, a create function should be written to create an
+<code>axis2_svc_skeleton</code> instance, and assign the implementing
+functions to the members of the ops member of service skeleton.</p><p>The following table details the signatures of the function pointer members
+of the <code>axis2_svc_skeleton</code> struct implemented by a service.</p><table class="bodyTable"><caption></caption><tbody>
     <tr class="b"><th>Function Signature</th><th>Description</th></tr>
-    <tr class="a"><td><pre>axis2_status_t (AXIS2_CALL *
-    free )( axis2_svc_skeleton_t *svc_skeli,
-        const axis2_env_t *env);</pre>
-      </td><td>Frees the service implementation instance.</td></tr>
-    <tr class="b"><td><pre>axiom_node_t *(AXIS2_CALL*
+    <tr class="a"><td><pre>int (AXIS2_CALL *
+    init)(axis2_svc_skeleton_t *svc_skeleton,
+        const axutil_env_t *env);</pre>
+      </td><td>Initializes the service skeleton object instance. The Axis2/C
+        engine initializes a service skeleton instance once per deployed
+        service, during the first request made to the service.</td></tr>
+    <tr class="b"><td width="410"><pre>axiom_node_t *(AXIS2_CALL*
     invoke )( axis2_svc_skeleton_t *svc_skeli,
-        const axis2_env_t *env,
+        const axutil_env_t *env,
         axiom_node_t *node,
         axis2_msg_ctx_t *msg_ctx);</pre>
       </td><td>Invokes the service implementation. You have to implement the logic
         to call the correct functions in this method based on the name of the
         operation being invoked.</td></tr>
-  </tbody></table><br></br>
-    <div class="source"><pre>int AXIS2_CALL
-math_free (axis2_svc_skeleton_t *svc_skeleton, const axis2_env_t *env
-{
-    if (svc_skeleton-&gt;ops)
-    {
-        AXIS2_FREE(env-&gt;allocator, svc_skeleton-&gt;ops);
-        svc_skeleton-&gt; ops = NULL;
-    }
-    if(svc_skeleton)
-    {
-      AXIS2_FREE (env-&gt;allocator, svc_skeleton -&gt;ops);
-      svc_skeleton -&gt; NULL;
-    }
-    return AXIS2_SUCCESS;
-}
-
-
-</pre></div>
-  <p>The above code shows the free method implementation of the math sample.</p>
-    <div class="source"><pre>axiom_node_t* AXIS2_CALL
-math_invoke(axis2_svc_skeleton_t *svc_skeleton,
-        const axis2_env_t *env,
-        axiom_node_t *node,
-        axis2_msg_ctx_t *msg_ctx)
-{
-    if(node)
-    {
-        if(AXIOM_NODE_GET_NODE_TYPE(node, env) == AXIOM_ELEMENT)
-        {
-            axiom_element_t *element = NULL;
-            element = (axiom_element_t *)AXIOM_NODE_GET_DATA_ELEMENT(node, env);
-            if(element)
-            {
-                axis2_char_t *op_name = AXIOM_ELEMENT_GET_LOCALNAME(element, env);
-                if(op_name)
-                {
-                    if(AXIS2_STRCMP(op_name, "add") == 0)
-                        return axis2_math_add(env, node);
-                    if(AXIS2_STRCMP(op_name, "sub") == 0)
-                        return axis2_math_sub(env, node);
-                    if(AXIS2_STRCMP(op_name, "mul") == 0)
-                        return axis2_math_mul(env, node);
-                    if(AXIS2_STRCMP(op_name, "div") == 0)
-                        return axis2_math_div(env, node);
-           vice ERROR: invalid operation invoked\n");
-    return node;
-}
-
-</pre></div>
-  <p>The above code fragment from math sample shows how the correct method to
-be invoked could be picked from the operation name that comes in the message
-context.</p><p>There are two more methods that a service should implement. Once a service
-is deployed, the message receiver of the Axis2/C engine would need to create
-a service instance at runtime for the purpose of invoking it. For this, it
-looks for a method named axis2_create_instance and calls it on the service
-shared library. The engine also looks for a function named
-axis2_remove_instance in the shared library for clean up purposes.</p>
-    <div class="source"><pre>AXIS2_EXPORT int axis2_get_instance(struct axis2_svc_skeleton **inst,
-        const axis2_env_t *env)
-{
-    *inst = axis2_math_create(env);
-    if(!(*inst))
-    {
-        return AXIS2_FAILURE;
-    }
-
-    return AXIS2_SUCCESS;
-}
-
-AXIS2_EXPORT int axis2_remove_instance(axis2_svc_skeleton_t *inst,
-        const axis2_env_t *env)
-{
-    axis2_status_t status = AXIS2_FAILURE;
-    if (inst)
-    {
-        status = AXIS2_SVC_SKELETON_FREE(inst, env);
-    }
-    return status;
-}
-
-
-</pre></div>
-  <p>Note that service instantiation happens per request. That means for each
-request, the create method would be called and a new axis2_svc_skeleton
-instance would be created.</p><p><a name="cli_api"></a></p></div><div class="section"><a name="4__Client_API"></a><h2>4. Client API</h2><p>The primary client API to be used with Axis2/C is axis2_svc_client, the
-service client API. This is meant to be an easy to use API for consuming
-services. If you want to do more complex tasks, such as invoking a client
-inside a module, or wrap the client API with another interface, you may need
-to use the axis2_op_client, operation client, API. However for general
-purposes, service client is sufficient.</p><p>Behaviour of the service client could be fine tuned with the options
-passed to service client. You can set the options by creating an
-axis2_options instance. The bare minimum that you need to set is the endpoint
-URI where the request is to be sent to. An example of this was given in the
-<a href="#quick_start">quick start guide section</a>.</p><p>The service client interface serves as the primary client interface for
+    <tr class="a"><td><pre>axiom_node_t *(AXIS2_CALL*
+    on_fault)(
+        axis2_svc_skeleton_t *svc_skeli,
+        const axutil_env_t *env,
+        axiom_node_t *node); </pre>
+      </td><td>This method is called by the engine if a fault is detected.</td></tr>
+    <tr class="b"><td><pre>axis2_status_t (AXIS2_CALL *
+    free )( axis2_svc_skeleton_t *svc_skeli,
+        const axutil_env_t *env);</pre>
+      </td><td>Frees the service implementation instance.</td></tr>
+  </tbody></table><br></br><p>There are two more methods that a service should implement. Once a service
+is deployed, the message receiver of the Axis2/C engine has to create a
+service instance at run time for the purpose of invoking it. For this, it
+looks for a method named <code>axis2_create_instance</code> and calls it on
+the service shared library. The engine also looks for a function named
+<code>axis2_remove_instance</code> in the shared library for clean up
+purposes.</p><p>Note that service object instantiation happens once per service. When the
+first request is received by the service, a service skeleton instance is
+created and initialized. The same object instance will be re-used by the
+subsequent requests.</p><p>You can find an example on how to implement the service skeleton interface
+in the <a href="hello/service/hello_svc.c.html">hello_svc.c</a> source file,
+which is the example used in the <a href="#quick_start">Quick Start
+Guide</a>. More advanced samples can be found in the samples folder of the
+Axis2/C distribution.</p><p><a name="client_api"></a></p></div><div class="section"><a name="4__Client_API"></a><h2>4. Client API</h2><p>The primary client API to be used with Axis2/C is
+<code>axis2_svc_client</code>, the service client API. This is meant to be an
+easy to use API for consuming services. If you want to do more complex tasks,
+such as invoking a client inside a module, or wrap the client API with
+another interface, you may need to use <code>axis2_op_client</code>, the
+operation client API. For most of the use cases, the service client API is
+sufficient.</p><p>The behavior of the service client can be fine tuned with the options
+passed to the service client. You can set the options by creating an
+<code>axis2_options</code> instance. The bare minimum that you need to set is
+the endpoint URI to which the request is to be sent. An example of this was
+given in the <a href="#quick_start">Quick Start Guide section</a>.</p><p>The service client interface serves as the primary client interface for
 consuming services. You can set the options to be used by the service client
 and then invoke an operation on a given service. There are several ways of
-invoking a service operation. The way of invoking an operation depends on 3
-things. Those are,</p><ol>
+invoking a service operation. The method of invoking an operation depends on
+3 things. They are,</p><ol>
   <li>The Message Exchange Pattern (MEP)</li>
-  <li>Synchronous/Asynchronous behaviour (Blocking/Non-Blocking)</li>
+  <li>Synchronous/Asynchronous behavior (Blocking/Non-Blocking)</li>
   <li>Two-way or one-way transport</li>
-</ol><p>Many ways of service operation invocation scenarios can be obtained by
-combining above three factors. Service client interface provides the
-necessary API calls to achieve this .</p><p></p><p>Deciding the Message Exchange Pattern (MEP)</p><p>There are 2 message exchange patterns.</p><ol>
+</ol><p>Many service operation invocation scenarios can be obtained by combining
+the above three factors. The service client interface provides the necessary
+API calls to achieve this.</p><p>Deciding the Message Exchange Pattern (MEP)</p><p>There are 2 message exchange patterns.</p><ol>
   <li>Out-Only</li>
   <li>Out-In</li>
-</ol><p>In Out-Only MEP the client doesn't expect a reply from the server. Service
-client provides two methods for invoking Out-Only operations.</p><p></p><div class="subsection"><a name="axis2_svc_client_fire_and_forget"></a><h3>axis2_svc_client_fire_and_forget</h3><p>Sends a message and forget about it. This method is used to interact with
-a service operation whose MEP is In-Only. That is, there is no opportunity to
-get an error from the service via this method; one may still get client-side
-errors, such as host unknown etc.</p><table class="bodyTable"><caption></caption><tbody>
-    <tr class="a"><th>Parameter</th><th>Description</th></tr>
-    <tr class="b"><td>axis2_svc_client_t *svc_client</td><td>pointer to service client struct</td></tr>
-    <tr class="a"><td>const axis2_env_t *env</td><td>pointer to environment struct</td></tr>
-    <tr class="b"><td>const axis2_qname_t *op_qname</td><td>qname of the service operation which is going to be invoked.</td></tr>
-    <tr class="a"><td>const axiom_node_t *payload</td><td>pointer to OM node representing the XML payload to be sent</td></tr>
-  </tbody></table><p>return type :- void</p><p></p></div><div class="subsection"><a name="axis2_svc_client_send_robust"></a><h3>axis2_svc_client_send_robust</h3><p>If a fault triggers on server side, this method would report an error back
-to the caller.</p><table class="bodyTable"><caption></caption><tbody>
-    <tr class="b"><th>Parameter</th><th>Description</th></tr>
-    <tr class="a"><td>axis2_svc_client_t *svc_client</td><td>pointer to service client struct</td></tr>
-    <tr class="b"><td>const axis2_env_t *env</td><td>pointer to environment struct</td></tr>
-    <tr class="a"><td>const axis2_qname_t *op_qname</td><td>qname of the service operation which is going to be invoked.</td></tr>
-    <tr class="b"><td>const axiom_node_t *payload</td><td>pointer to OM node representing the XML payload to be sent</td></tr>
-  </tbody></table><p>return type:- axis2_status_t</p><p>return AXIS2_SUCCESS on success, else AXIS2_FAILURE.</p><p></p><p>In In-Out MEP, the client expect a reply from the server. The
-axis2_svc_client_send_recieve and axis2_send_receive_non_blocking supports
-this MEP.</p><p></p></div><div class="subsection"><a name="axis2_svc_client_send_receive"></a><h3>axis2_svc_client_send_receive</h3><p>Sends XML request and receives XML response.</p><table class="bodyTable"><caption></caption><tbody>
-    <tr class="a"><th>Parameter</th><th>Description</th></tr>
-    <tr class="b"><td>axis2_svc_client_t *svc_client</td><td>pointer to service client struct</td></tr>
-    <tr class="a"><td>const axis2_env_t *env</td><td>pointer to environment struct</td></tr>
-    <tr class="b"><td>const axis2_qname_t *op_qname</td><td>qname of the service operation which is going to be invoked.</td></tr>
-    <tr class="a"><td>const axiom_node_t *payload</td><td>pointer to OM node representing the XML payload to be sent</td></tr>
-  </tbody></table><p>Returns pointer to the OM node representing the XML response. This method
-blocks until the response arrives.</p><p></p></div><div class="subsection"><a name="axis2_send_receive_non_blocking"></a><h3>axis2_send_receive_non_blocking</h3><p>Sends XML request and receives XML response, but does not block for
-response.</p><table class="bodyTable"><caption></caption><tbody>
-    <tr class="b"><th>Parameter</th><th>Description</th></tr>
-    <tr class="a"><td>axis2_svc_client_t *svc_client</td><td>pointer to service client struct</td></tr>
-    <tr class="b"><td>const axis2_env_t *env</td><td>pointer to environment struct</td></tr>
-    <tr class="a"><td>const axis2_qname_t *op_qname</td><td>qname of the service operation which is going to be execute</td></tr>
-    <tr class="b"><td>const axiom_node_t *payload</td><td>pointer to OM node representing the XML payload to be sent</td></tr>
-    <tr class="a"><td>axis2_callback_t *callback</td><td>pointer to callback struct used to capture response</td></tr>
-  </tbody></table><p></p><p>Return type :- void<br></br>
-This method will not block for the response. Instead it sets a call back to
-capture the response.<br></br>
-</p><p><strong>Synchronous/Asynchronous Behaviour
-(Blocking/Non-Blocking)</strong></p><p>This will determine whether the client would block (Sysnchronous) or
-return immediately (Asynchronous) for the response in a in-out MEP
+</ol><p>In the Out-Only MEP, the client doesn't expect a reply from the server.
+The service client provides two methods of using the Out-Only MEP.</p><p></p><div class="subsection"><a name="axis2_svc_client_fire_and_forget"></a><h3>axis2_svc_client_fire_and_forget</h3><p>Sends a message and forgets about it. This method is used to interact with
+a service operation whose MEP is In-Only. There is no way of getting an error
+from the service using this method. However, you may still get client-side
+errors, such as host unknown.</p></div><div class="subsection"><a name="axis2_svc_client_send_robust"></a><h3>axis2_svc_client_send_robust</h3><p>This method too is used to interact with a service operation whose MEP is
+In-Only. However, unlike <code>axis2_svc_client_fire_and_forget</code>, this
+function reports an error back to the caller if a fault triggers on the
+server side.</p><p>When using Out-In MEP, the client expects a reply from the server.
+<code>axis2_svc_client_send_receive</code> and
+<code>axis2_svc_client_send_receive_non_blocking<code>
+</code></code>functions support this MEP<code><code>.</code></code></p></div><div class="subsection"><a name="axis2_svc_client_send_receive"></a><h3>axis2_svc_client_send_receive</h3><p>This method is used to interact with a service operation whose MEP is
+In-Out. It sends an XML request and receives an XML response.</p><p>Returns a pointer to the AXIOM node representing the XML response. This
+method blocks the client until the response arrives.</p></div><div class="subsection"><a name="axis2_send_receive_non_blocking"></a><h3>axis2_send_receive_non_blocking</h3><p>This method too, is used to interact with a service operation whose MEP is
+In-Out. It sends an XML request and receives an XML response, but the client
+does not block for the response.</p><p>In this method, the client does not block for the response, but instead it
+expects the user to set a call back to capture the response.<br></br>
+</p><p>Please have a look at the <code>axis2_svc_client.h</code> header file for
+more information on function signatures of the above mentioned functions.</p></div><div class="subsection"><a name="Synchronous_vs__Asynchronous_Behavior__Blocking_Non-Blocking_"></a><h3>Synchronous vs. Asynchronous Behavior (Blocking/Non-Blocking)</h3><p>This will determine whether the client would block for the response
+(synchronous) or return immediately expecting the response to be handled by a
+callback (asynchronous, in other words non-blocking) in an Out-In MEP
 scenario.<br></br>
-<em>AXIS2_SVC_CLIENT_SEND_RECEIVE</em> or
-<em>AXIS2_SVC_CLIENT_SEND_RECEIVE_NON_BLOCKING</em> methods.<br></br>
-</p><p></p><p><strong>Two-way or One-way transport</strong></p><p>If the transport is Two-way then only one channel is used .If the
-Transport is One-way then the response would have to come on a seperate
-chanel.<br></br>
-If we want to use a seperate channel for the response
-<em>SET_USE_SEPERATE_LISTENER</em> option has to be set.</p><p>See <a href="#appD">ApendixD</a> for further details on setting
-options.</p><p><a name="rest"></a></p></div></div><div class="section"><a name="5__REST"></a><h2>5. REST</h2><p>If you want to consume Web services using REST style calls you can use
-either the HTTP POST method or HTTP GET method.</p><p>The following example code fragments shows how to enable a REST style
-invocation using different HTTP methods.</p>
-    <div class="source"><pre>AXIS2_OPTIONS_SET_PROPERTY(options, env, AXIS2_ENABLE_REST, AXIS2_VALUE_TRUE);
-
-</pre></div>
-  <p>Default HTTP method used with REST is HTTP POST Method. If someone need
-tochange it to HTTP GET method following needs to be done.</p><p>REST with HTTP GET</p>
-    <div class="source"><pre>AXIS2_OPTIONS_SET_PROPERTY(options, env, AXIS2_HTTP_METHOD, AXIS2_HTTP_HEADER_GET);&gt;
-
-</pre></div>
-  <p>Apart from setting the above options one do not have to do anything
-special to get REST to work You can use the same code that you would use with
-a SOAP call and do rest style invocation.</p><p><a name="mtom"></a></p></div><div class="section"><a name="6__MTOM"></a><h2>6. MTOM</h2><p>Axis2/C allows you to send and receive binary data with SOAP messages
-using MTOM/XOP conventions. When sending attachments, you have to use service
-client (svc_client) to perform the send and receive operation, and give the
-binary data as an array.</p><p>In order to send the attachment you need to build AXIOM payload and attach
-the data handler with binary content to the payload.</p>
+<code>axis2_svc_client_send_receive</code> operates in synchronous mode,
+whereas <code>axis2_svc_client_send_receive_non_blocking</code> operates in
+asynchronous mode.<br></br>
+</p></div><div class="subsection"><a name="Two-Way_or_One-Way_Transport"></a><h3>Two-Way or One-Way Transport</h3><p>If the transport is two-way, then only one channel is used, which means
+the request is sent and the response is received on the same channel. If the
+transport is one-way, then the request is sent on one channel and the
+response is received on a separate channel.<br></br>
+If we want to use a separate channel for the response, a separate listener
+has to be started to receive the response, This can be done by setting the
+separate listener option to True using the
+<code>axis2_options_set_use_separate_listener</code> function above the
+options.</p><p>Please have a look at the <code>echo_blocking_dual</code> sample to see
+how to set the separate channel option.</p><p>Please see <a href="#appD">Appendix D</a> for further details on setting
+options.</p><p><a name="rest"></a></p></div></div><div class="section"><a name="5__REST"></a><h2>5. REST</h2><p>Axis2/C comes with plain old XML (POX) like REST support. A given service
+can be exposed both as a SOAP service as well as a REST service. If you want
+to consume Web services using REST style calls, you can use either the HTTP
+POST method or the HTTP GET method.</p><p>The following example code fragment shows how to enable a REST style
+invocation.</p>
+    <div class="source"><pre>axis2_options_set_enable_rest(options, env, AXIS2_TRUE);
+
+</pre></div>
+  <p>You can use the same code that you use with a SOAP call, and do REST style
+invocation by just enabling REST using the option setting shown above.</p><p>The default HTTP method used with REST is HTTP POST. If you need to change
+it to the HTTP GET method, the following needs to be done.</p>
+    <div class="source"><pre>axis2_options_set_http_method(options, env, AXIS2_HTTP_GET);
+
+</pre></div>
+  <p>Please have a look at the <code>echo_rest</code> sample for a complete
+source code on how to use REST.</p><p><a name="mtom"></a></p></div><div class="section"><a name="6__MTOM"></a><h2>6. MTOM</h2><p>Axis2/C allows you to send and receive binary data with SOAP messages
+using MTOM/XOP conventions. When sending and receiving attachments, you have
+to use the service client (<code>axis2_svc_client</code>) API to perform the
+send and receive operations, and provide or consume binary data in relation
+to the AXIOM payloads.</p><p>In order to send a binary attachment, you need to build the AXIOM payload
+and attach the data handler with binary content to the payload.</p>
     <div class="source"><pre>&lt;soapenv:Body&gt;
-&lt;ns1:mtomSample xmlns:ns1="http://ws.apache.org/axis2/c/samples/mtom"&gt;
-&lt;ns1:fileName&gt;test.jpg&lt;/ns1:fileName&gt;
-&lt;ns1:image&gt;
-&lt;xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:1.f399248e-8b39-1db1-3124-0015c53de2e5@apache.org"&gt;&lt;/xop:Include&gt;
-&lt;/ns1:image&gt;
-&lt;/ns1:mtomSample&gt;
+    &lt;ns1:mtomSample xmlns:ns1="http://ws.apache.org/axis2/c/samples/mtom"&gt;
+        &lt;ns1:fileName&gt;test.jpg&lt;/ns1:fileName&gt;
+        &lt;ns1:image&gt;
+            &lt;xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" 
+                href="cid:1.f399248e-8b39-1db1-3124-0015c53de2e5@apache.org"&gt;&lt;/xop:Include&gt;
+        &lt;/ns1:image&gt;
+    &lt;/ns1:mtomSample&gt;
 &lt;/soapenv:Body&gt;
 
 </pre></div>
   <p>In the above sample payload shown, we place our image file as text within
 an image element</p>
-    <div class="source"><pre>image_om_ele = axiom_element_create(env,mtom_om_node, "image", ns1,&amp;image_om_node);
+    <div class="source"><pre>image_om_ele = axiom_element_create(env, mtom_om_node, "image", ns1, &amp;image_om_node);
 data_handler = axiom_data_handler_create(env, image_name, "image/jpeg");
-data_text = axiom_text_create_with_data_handler(env, image_om_node,data_handler, &amp;data_om_node);
+data_text = axiom_text_create_with_data_handler(env, image_om_node, data_handler, &amp;data_om_node);
 
 </pre></div>
   <p>When sending attachments, you can configure the client either to send the
-attachment in the optimised format or in non optimised format. By setting an
-option</p>
-    <div class="source"><pre>AXIS2_OPTIONS_SET_ENABLE_MTOM(options,env,AXIS2_TRUE);</pre></div>
-  <p>
-or setting</p><br></br>
-    <div class="source"><pre>&lt;enableMtom&gt;true&lt;/enableMtom&gt;</pre></div>
-  <p>
-in axis2.xml
-
-</p><p>If enableMTOM is set to true the attachment would be sent as it is, out of
-the SOAP body, using MIME headers and the payload would have an XOP:Include
-element, referring to the MIME part that contains the binary attachment. In
-case of binary non optimised format,where enable mtom is false the attachment
-content would be sent in the payload itself, as a base64 encoded string.</p><p><a name="eng_mod"></a></p></div><div class="section"><a name="7__Engaging_a_Module"></a><h2>7. Engaging a Module</h2><p>A module is a set of handlers that helps to extend the message processing
-behaviours of Axis2/C SOAP engine. Modules have the concept of being
-available and engaged. Available means modules are deployed in the system but
-not activated. They will be activated only after being engaged. Every module
-should come with its own module.xml file . This module.xml file specifies the
-module specific handlers and to what phases they are to be deployed in the
-handler chain. Some of the module specific handlers may be put in to system
-predefined phases.In that case, module.xml file should specify where to put
-the handlers relative to the others in that phase. Sometimes a module may
-define its own phase. In that case some of the module specie handlers may be
-put in to that phase. The handlers which are added to the system predefined
-phases (global handlers) are invoked for every message which comes to or goes
-out from the system. The handlers in the module specific phase are invoked
-only for the messages invoking the operations that engage that module.
-Engaging a module means correctly adding the handlers of a particular module
-to one or more phases. A service, operations or the system may engage a
-module. Once the module is engaged the handlers and the operations defined in
-the module are added to the entity that engaged them.</p><p></p><p>Before engaging a module following steps has to be followed.</p><ol>
-  <li>Writing the module.xml file</li>
-  <li>Packaging the module libraries and the module.xml in to a folder which
-    has the name of the module.</li>
+attachment in the optimized format or non-optimized format.</p><p>To do this, set the option <code>axis2_options_set_enable_mtom(options,
+env, AXIS2_TRUE);</code>or the setting
+<code>&lt;enableMtom&gt;true&lt;/enableMtom&gt; </code>in axis2.xml</p><p>If enableMTOM is set to True, the attachment is sent as it is, out of the
+SOAP body, using MIME headers. Also the payload will have an XOP:Include
+element, referring to the MIME part that contains the binary attachment.
+Sending the attachment as it is, in pure binary format, is called binary
+optimized format. In the case of binary non-optimized format, where
+enableMTOM is False, the attachment content is sent in the payload itself, as
+a base64 encoded string.</p><p>Please have a look at the <code>mtom</code> sample for a complete example
+on how to use MTOM.</p><p><a name="engaging_module"></a></p></div><div class="section"><a name="7__Engaging_a_Module"></a><h2>7. Engaging a Module</h2><p>A module is a set of handlers that helps to extend the message processing
+behavior of the Axis2/C engine. Modules have the concepts of being Available
+and Engaged associated with them. Available means modules are deployed in the
+system but not activated. They will be activated only after being engaged.
+Every module comes with its own module.xml file . This module.xml file
+specifies the module specific handlers and the phases into which the handlers
+are to be placed in the handler chain. Some of the module specific handlers
+may be put into system predefined phases. In that case, the module.xml file
+should specify where to put the handlers relative to the others in that
+phase. Sometimes a module may define its own phase. In that case, some of the
+module specific handlers may be put into that phase. The handlers added to
+the system predefined phases (global handlers) are invoked for every message
+that comes to or goes out from the system. The handlers in the module
+specific phase are invoked only for the messages invoking the operations that
+engage that module. Engaging a module means correctly adding the handlers of
+a particular module to one or more phases. Once the module is engaged, the
+handlers and the operations defined in the module are added to the entity
+that engaged them.</p><p>Before engaging a module, the following steps have to be followed.</p><ol>
+  <li>Write the module.xml file</li>
+  <li>Package the module libraries and the module.xml into a folder which has
+    the same name as the module</li>
   <li>Deploy the folder in AXIS2C_INSTALL_DIR/modules</li>
-  <li>Adding the module specific phases in the axis2.xml file.</li>
-</ol><p>The following is an example of engaging a sample module called logging
-module with Axis2/C.</p><p></p><div class="subsection"><a name="Writing_the_module_xml_File"></a><h3>Writing the module.xml File</h3><p>In the module.xml file, the handlers of the module and the phases to which
-they are to be added has to be specified. Below is the module.xml file of the
-sample logging module.</p>
-    <div class="source"><pre>
-        &lt;module name="logging" class="axis2_mod_log"&gt;
-	   &lt;inflow&gt;
+  <li>Add the module specific phases in the axis2.xml file</li>
+</ol><p>The following is an example of engaging a sample module called the logging
+module with Axis2/C:</p><div class="subsection"><a name="Writing_the_module_xml_File"></a><h3>Writing the module.xml File</h3><p>In the module.xml file, the handlers of the module and the phases to which
+they are to be added have to be specified. Below is the module.xml file of
+the sample logging module.</p>
+    <div class="source"><pre>        &lt;module name="logging" class="axis2_mod_log"&gt;
+           &lt;inflow&gt;
               &lt;handler name="LoggingInHandler" class="axis2_mod_log"&gt;
                  &lt;order phase="PreDispatch"/&gt;
               &lt;/handler&gt;
@@ -652,565 +522,552 @@
            &lt;/Outfaultflow&gt;
         &lt;/module&gt;
 
-
 </pre></div>
-  </div><div class="subsection"><a name="Adding_the_Module_Specific_Phases_in_the_axis2_xml_File"></a><h3>Adding the Module Specific Phases in the axis2.xml File</h3><p>The module specific phase has to de added after the system predefined
-phases. The following example shows where to add the module specific
-phases.</p>
-    <div class="source"><pre>&lt;phaseOrder type="inflow"&gt;
-        &lt;!-- System pre defined phases --&gt;
-        &lt;phase name="TransportIn"/&gt;
-        &lt;phase name="PreDispatch"/&gt;
-        &lt;phase name="Dispatch"
-        class="org.apache.axis2.engine.DispatchPhase"&gt;
-        &lt;handler name="AddressingBasedDispatcher"
-        class="axis2_engine"&gt;
-        &lt;order phase="Dispatch"/&gt;
-        &lt;/handler&gt;
-        &lt;handler name="RequestURIBasedDispatcher"
-        class="axis2_engine"&gt;
-        &lt;order phase="Dispatch"/&gt;
-        &lt;/handler&gt;
-        &lt;handler name="SOAPActionBasedDispatcher"
-        class="axis2_engine"&gt;
-        &lt;order phase="Dispatch"/&gt;
-        &lt;/handler&gt;
-        &lt;handler name="SOAPMessageBodyBasedDispatcher"
-        class="axis2_engine"&gt;
-        &lt;order phase="Dispatch"/&gt;
-        &lt;/handler&gt;
-        &lt;handler name="InstanceDispatcher"
-        class="org.apache.axis2.engine.InstanceDispatcher"&gt;
-        &lt;order phase="PostDispatch"/&gt;
-        &lt;/handler&gt;
-        &lt;/phase&gt;
-        &lt;!-- System pre defined phases --&gt;
-        &lt;!-- After Postdispatch phase
-        module author or or service author can add any phase he want  --&gt;
-        &lt;phase name="OperationInPhase"/&gt;
-        &lt;phase name=""/&gt;
-        &lt;/phaseOrder&gt;
-        &lt;phaseOrder type="outflow"&gt;
-        &lt;!-- user can add his own phases  to this area --&gt;
-        &lt;phase name="OperationOutPhase"/&gt;
-        &lt;phase name=""/&gt;
-        &lt;!--system predefined phase--&gt;
-        &lt;!--these phase will run irrespective of the service--&gt;
-        &lt;phase name="MessageOut"/&gt;
-        &lt;/phaseOrder/&gt;
-        &lt;phaseOrder type="INfaultflow"&gt;
-        &lt;!-- user can add his own phases  to this area --&gt;
-        &lt;phase name="OperationInFaultPhase"/&gt;
-        &lt;phase name=""/&gt;
-        &lt;/phaseOrder&gt;
-        &lt;phaseOrder type="Outfaultflow"&gt;
-        &lt;!-- user can add his own phases to this area --&gt;
-        &lt;phase name="OperationOutFaultPhase"/&gt;
-        &lt;phase name=""/&gt;
-        &lt;phase name="PolicyDetermination"/&gt;
-        &lt;phase name="MessageOut"/&gt;
-&lt;/phaseOrder&gt;
-
-</pre></div>
-  <p>As mentioned in the above example, the user or module author can handle
-his own phases after system predefined phases.In the above example there are
-no specific phases for the logging module. That is all the module specific
-handlers are added to the system predefined phases as mentioned in the
-module.xml file.</p><p></p></div><div class="subsection"><a name="Engaging_the_Module_for_Services"></a><h3>Engaging the Module for Services</h3><p>Following is an example of engaging the logging module to the echo
-service.This can be done by simply adding &lt;module ref ="logging"/&gt; in
-the services.xml file. This informs the Axis2 engine that the module
-"logging" should be engaged for this service. The handler inside the module
-will be executed in their respective phases as described by the
-"module.xml".</p>
-    <div class="source"><pre>
-     &lt;service name="echo"&gt;
-          &lt;module ref ="logging"/&gt;
-                &lt;parameter name="ServiceClass" locked="xsd:false"&gt;echo&lt;/parameter&gt;
-                   &lt;description&gt;
-                      This is a testing service , to test the system is working or  not
-                  &lt;/description&gt;
-                &lt;operation name="echoString"&gt;
-                &lt;!--messageReceiver class="axis2_receivers" /--&gt;
-                    &lt;parameter name="wsamapping" &gt;
-		        http://ws.apache.org/axis2/c/samples/echoString
-                    &lt;/parameter&gt;
-                &lt;/operation&gt;
-      &lt;/service&gt;
-
-
-</pre></div>
-  </div><div class="subsection"><a name="Engaging_the_Module_Globally"></a><h3>Engaging the Module Globally</h3><p>If we want to engage the module for every service deployed in the Axis2/C
-system, we can add the above entry in the axis2.xml file. This will inform
-the Axis2/C engine to invoke the handler inside the module specific phases
-for every message coming to any service deployed within the engine.</p></div><div class="subsection"><a name="Engaging_the_Module_on_the_Client_Side"></a><h3>Engaging the Module on the Client Side</h3><p>On the client side, if the above &lt;module ref ="logging"/&gt; is added
-in the axis2.xml the module specific handlers will be invoked for every
-request the client sends.If only a particular client wants to engage the
-module it can be done by engaging the module programmatically. This can be
-done by adding the following line in the client code after setting the
-options.</p><p>AXIS2_SVC_CLIENT_SET_OPTIONS(svc_client, env, options);</p><p><em>AXIS2_SVC_CLIENT_ENGAGE_MODULE(svc_client, env, "module
-name");</em></p><p>Remember to replace "module-name" with the name of the module you want to
-engage.</p><p><a name="ws_add"></a></p></div></div><div class="section"><a name="8__WS-Addressing"></a><h2>8. WS-Addressing</h2><p><a href="http://www.w3.org/2002/ws/addr/" class="externalLink" title="External Link">WS-Addressing</a> provides
+  <p>In the above shown module configuration file, the name of the module is
+logging. There are two handlers in this module, the LoggingInHandler and the
+LoggingOutHandler. The LoggingInHandler is placed into the PreDispatch phase
+of the in flow. The LoggingOutHandler is placed into the MessageOut phase of
+both the out flow and the fault out flow.</p></div><div class="subsection"><a name="Packaging_and_Deploying_the_Module"></a><h3>Packaging and Deploying the Module</h3><p>The above module.xml file should be copied to a folder named "logging"
+(because the module name is "logging") inside the AXIS2C_INSTALL_DIR/modules
+folder. The module libraries containing the handler implementation should
+also be copied to the same folder. According to the module.xml file shown
+above, the name of the shared library file should be libaxis2_mod_log.so on
+Linux and axis2_mod_log.dll on MS Windows.</p></div><div class="subsection"><a name="Adding_Module_Specific_Phases_to_the_axis2_xml_File"></a><h3>Adding Module Specific Phases to the axis2.xml File</h3><p>Module specific phases have to be added after the system predefined
+phases. The following example shows where to add the module specific phases.
+Look for the <code>phaseOrder</code> elements in the axis2.xml file. Note the
+comment lines:</p>
+    <div class="source"><pre>        &lt;!-- User defined phases could be added here --&gt;</pre></div>
+  <p>
+You can add user defined phases after the above comment line into any of the
+flows. The <code>type</code> attribute of the <code>phaseOrder</code> element
+indicates the flow.
+
+</p><p>For the logging module example, user defined phases are not required. All
+the module specific handlers are added to system predefined phases as
+specified in the module.xml file.</p></div><div class="subsection"><a name="Engaging_a_Module_to_a_Services"></a><h3>Engaging a Module to a Services</h3><p>The following is an example of engaging the logging module to the echo
+service. This can be done by simply adding <code>&lt;module ref
+="logging"/&gt;</code> in the services.xml file of the echo service. This
+informs the Axis2/C engine that the module "logging" should be engaged for
+this service. The handlers inside the module will be executed in their
+respective phases as described by the module.xml.</p>
+    <div class="source"><pre>   &lt;service name="echo"&gt;
+        &lt;module ref ="logging"/&gt;
+        &lt;parameter name="ServiceClass" locked="xsd:false"&gt;echo&lt;/parameter&gt;
+        &lt;description&gt;
+           This is a testing service, to test if the system is working or not.
+        &lt;/description&gt;
+        &lt;operation name="echoString"&gt;
+            &lt;!--messageReceiver class="axis2_receivers" /--&gt;
+            &lt;parameter name="wsamapping" &gt;
+                http://ws.apache.org/axis2/c/samples/echoString
+            &lt;/parameter&gt;
+        &lt;/operation&gt;
+    &lt;/service&gt;
+
+</pre></div>
+  <p>One important thing to note here is that because the logging module's
+handlers are placed into the global phases, even though the logging module is
+engaged only to the echo service, the module will be engaged globally. This
+is a feature of the Axis2 architecture, not a bug. When invoked, the handlers
+in a module can check whether the module has been engaged to a particular
+service, and act accordingly.</p></div><div class="subsection"><a name="Engaging_a_Module_Globally"></a><h3>Engaging a Module Globally</h3><p>If we want to engage a module for every service deployed in the Axis2/C
+system, we can add the <code>&lt;module ref ="logging"/&gt;</code> entry in
+the axis2.xml file. This will inform the Axis2/C engine to invoke the
+handlers associated with the module for every message coming in or going out
+for all the services deployed.</p></div><div class="subsection"><a name="Engaging_a_Module_on_the_Client_Side"></a><h3>Engaging a Module on the Client Side</h3><p>On the client side, if <code>&lt;module ref ="logging"/&gt;</code> is
+added in the axis2.xml, the handlers specific to the logging module will be
+invoked for every request the client sends and every response the client
+receives. If only a particular client wants to engage the module, it can be
+done by engaging the module programmatically. This can be done by adding the
+following line in the client code after setting the options.</p>

[... 1572 lines stripped ...]


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-cvs-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-cvs-help@ws.apache.org