You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by da...@apache.org on 2008/01/16 11:59:29 UTC
svn commit: r612416 [2/3] - in /webservices/axis2/site/c: ./ api/ 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?rev=612416&r1=612415&r2=612416&view=diff
==============================================================================
--- webservices/axis2/site/c/docs/axis2c_manual.html (original)
+++ webservices/axis2/site/c/docs/axis2c_manual.html Wed Jan 16 02:59:27 2008
@@ -2,8 +2,8 @@
@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: 30 September 2007
- | Doc for 1.1.0</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuApache_Axis2_C"><h5>Apache Axis2/C</h5><ul><li class="none"><a href="../index.html">Apache Axis2/C 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="../lists_issues.html">Get Involved</a><ul><li class="none"><a href="../lists_issues.html">Mailing Lists & Issue Tracking</a></li><li class="none"><a href="../svn.html">Checkout Source Code</a></li></ul></li><li class="expanded"><a href="../coding_conventions.html">Developer Guidelines</a><ul><li cla
ss="none"><a href="../coding_conventions.html">Coding Convention</a></li><li class="none"><a href="../versioning.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
+ Last published: 14 January 2008
+ | Doc for 1.2.0</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuApache_Axis2_C"><h5>Apache Axis2/C</h5><ul><li class="none"><a href="../index.html">Apache Axis2/C 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="../lists_issues.html">Get Involved</a><ul><li class="none"><a href="../lists_issues.html">Mailing Lists & Issue Tracking</a></li><li class="none"><a href="../svn.html">Checkout Source Code</a></li></ul></li><li class="expanded"><a href="../coding_conventions.html">Developer Guidelines</a><ul><li cla
ss="none"><a href="../coding_conventions.html">Coding Convention</a></li><li class="none"><a href="../versioning.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
@@ -12,7 +12,8 @@
<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>
+</ul><p style="margin-bottom: 0in"><br></br>
+</p></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_folder">Repository Folder</a></li>
<li><a href="#svc_api">Service API</a></li>
@@ -27,12 +28,16 @@
<li><a href="#IIS">Deploying with Microsoft IIS Server</a></li>
<li><a href="#ssl_client">Using SSL Client</a></li>
<li><a href="#proxy">Using Proxy Support</a></li>
+ <li><a href="#proxy_auth">Using Proxy Authentication Support</a></li>
+ <li><a href="#http_auth">Using HTTP Authentication Support</a></li>
<li><a href="#wsdl2c">WSDL2C Tool</a></li>
+ <li><a href="#tcptrans">TCP Transport</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
+</ol><p style="margin-bottom: 0in"><br></br>
+</p><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
@@ -142,7 +147,7 @@
There can be one or more operation elements. For this sample, we only have
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/axis2-1.0/ -L$AXIS2C_HOME/lib -laxis2 hello_svc.c
+ <div class="source"><pre>gcc -shared -olibhello.so -I$AXIS2C_HOME/include/axis2-1.2/ -L$AXIS2C_HOME/lib -laxutil -laxis2_axiom -laxis2_parser -laxis2_engine -lpthread -laxis2_http_sender -laxis2_http_receiver hello_svc.c
</pre></div>
<p>On MS Windows:</p><p>to compile,</p>
@@ -226,7 +231,7 @@
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
+ <div class="source"><pre>gcc -o hello -I$AXIS2C_HOME/include/axis2-1.2/ -L$AXIS2C_HOME/lib -laxutil -laxis2_axiom -laxis2_parser -laxis2_engine -lpthread -laxis2_http_sender -laxis2_http_receiver hello.c -ldl -Wl,--rpath -Wl,$AXIS2C_HOME/lib
</pre></div>
<p>On MS Windows:</p><p>to compile,</p>
@@ -245,8 +250,8 @@
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="b"><th>Folder Name</th><th>Description</th></tr>
+purpose of the repository contents.</p><table class="bodyTable"><caption>Axis2/C Repository Contents</caption><tbody>
+ <tr class="b"><th>Folder/File Name</th><th>Description</th></tr>
<tr class="a"><td><p>lib</p>
</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
@@ -255,7 +260,7 @@
the repository lib folder. <br></br>
It is mandatory that the lib folder is there in the repository.</p>
</td></tr>
- <tr class="b"><td><p>modules</p>
+ <tr class="b"><td><p>modules [optional]</p>
</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
@@ -266,7 +271,7 @@
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="a"><td><p>services</p>
+ <tr class="a"><td><p>services [optional]</p>
</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>
@@ -302,7 +307,7 @@
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,
+etc.</p></div><div class="subsection"><a name="2_2_Service_Folders"></a><h3>2.2 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
@@ -322,7 +327,8 @@
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
+operations for each service, etc.</p><p style="margin-bottom: 0in"><br></br>
+</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
@@ -352,7 +358,7 @@
on_fault)(
axis2_svc_skeleton_t *svc_skeli,
const axutil_env_t *env,
- axiom_node_t *node); </pre>
+ axiom_node_t *node);</pre>
</td><td>This method is called by the engine if a fault is detected.</td></tr>
<tr class="a"><td><pre>axis2_status_t (AXIS2_CALL *
free )( axis2_svc_skeleton_t *svc_skeli,
@@ -364,14 +370,29 @@
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
+purposes.</p><table class="bodyTable"><caption></caption><tbody>
+ <tr class="b"><th>Function Signature</th><th>Description</th></tr>
+ <tr class="a"><td><pre>AXIS2_EXPORT int
+axis2_get_instance(
+ axis2_svc_skeleton_t ** inst,
+ const axutil_env_t * env);</pre>
+ </td><td>Creates an instance of the service. You have to implement the logic
+ of creating the service object, allocating memory etc. in this method.</td></tr>
+ <tr class="b"><td width="410"><pre>AXIS2_EXPORT int
+axis2_remove_instance(
+ axis2_svc_skeleton_t * inst,
+ const axutil_env_t * env);</pre>
+ </td><td>Removes the instance of the service. Do any cleaning-up and
+ deallocations here.</td></tr>
+ </tbody></table><br></br><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
+Axis2/C distribution.</p><p style="margin-bottom: 0in"><br></br>
+</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
@@ -395,30 +416,59 @@
<li>Out-Only</li>
<li>Out-In</li>
</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
+The service client provides two methods of using the Out-Only MEP.</p><p></p><table class="bodyTable"><caption></caption><tbody>
+ <tr class="a"><th>Function Signature</th><th>Description</th></tr>
+ <tr class="b"><td><pre>AXIS2_EXTERN void AXIS2_CALL
+ axis2_svc_client_fire_and_forget(
+ axis2_svc_client_t * svc_client,
+ const axutil_env_t * env,
+ const axiom_node_t * payload);</pre>
+ </td><td>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.</td></tr>
+ <tr class="a"><td width="410"><pre>AXIS2_EXTERN axis2_status_t AXIS2_CALL
+ axis2_svc_client_send_robust(
+ axis2_svc_client_t * svc_client,
+ const axutil_env_t * env,
+ const axiom_node_t * payload);</pre>
+ </td><td>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.<br></br>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>functions support this
+ MEP</td></tr>
+ <tr class="b"><td><pre> AXIS2_EXTERN axiom_node_t *AXIS2_CALL
+ axis2_svc_client_send_receive(
+ axis2_svc_client_t * svc_client,
+ const axutil_env_t * env,
+ const axiom_node_t * payload);</pre>
+ </td><td>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.<br></br>Returns
+ a pointer to the AXIOM node representing the XML response. This method
+ blocks the client until the response arrives.</td></tr>
+ <tr class="a"><td><pre>AXIS2_EXTERN void AXIS2_CALL
+ axis2_svc_client_send_receive_non_blocking(
+ axis2_svc_client_t * svc_client,
+ const axutil_env_t * env,
+ const axiom_node_t * payload,
+ axis2_callback_t * callback);</pre>
+ </td><td>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.<br></br>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.</td></tr>
+ </tbody></table><br></br><p>Please have a look at the <code>axis2_svc_client.h</code> header file for
+more information on the above mentioned functions, as well as their synonyms
+that accept an operation's qualified name.</p><div class="subsection"><a name="4_1_Synchronous_vs__Asynchronous_Behavior__Blocking_Non-Blocking_"></a><h3>4.1 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>
<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
+</p></div><div class="subsection"><a name="4_2_Two-Way_or_One-Way_Transport"></a><h3>4.2 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>
@@ -428,7 +478,8 @@
<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
+options.</p><p style="margin-bottom: 0in"><br></br>
+</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
@@ -443,7 +494,8 @@
</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
+source code on how to use REST.</p><p style="margin-bottom: 0in"><br></br>
+</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
@@ -477,7 +529,8 @@
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
+on how to use MTOM.</p><p style="margin-bottom: 0in"><br></br>
+</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.
@@ -501,7 +554,7 @@
<li>Deploy the folder in AXIS2C_INSTALL_DIR/modules</li>
<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
+module with Axis2/C:</p><div class="subsection"><a name="7_1_Writing_the_module_xml_File"></a><h3>7.1 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> <module name="logging" class="axis2_mod_log">
@@ -527,12 +580,12 @@
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"
+both the out flow and the fault out flow.</p></div><div class="subsection"><a name="7_2_Packaging_and_Deploying_the_Module"></a><h3>7.2 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
+Linux and axis2_mod_log.dll on MS Windows.</p></div><div class="subsection"><a name="7_3_Adding_Module_Specific_Phases_to_the_axis2_xml_File"></a><h3>7.3 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>
@@ -544,7 +597,7 @@
</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
+specified in the module.xml file.</p></div><div class="subsection"><a name="7_4_Engaging_a_Module_to_a_Services"></a><h3>7.4 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><module ref
="logging"/></code> in the services.xml file of the echo service. This
informs the Axis2/C engine that the module "logging" should be engaged for
@@ -570,11 +623,11 @@
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
+service, and act accordingly.</p></div><div class="subsection"><a name="7_4_1_Engaging_a_Module_Globally"></a><h3>7.4.1 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><module ref ="logging"/></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><module ref ="logging"/></code> is
+for all the services deployed.</p></div><div class="subsection"><a name="7_5_Engaging_a_Module_on_the_Client_Side"></a><h3>7.5 Engaging a Module on the Client Side</h3><p>On the client side, if <code><module ref ="logging"/></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
@@ -586,8 +639,10 @@
<p>Remember to replace "module-name" with the name of the module you want to
engage. For example to engage the logging module you can use:</p>
<div class="source"><pre>axis2_svc_client_engage_module(svc_client, env, "logging");
+
</pre></div>
- <p><a name="ws_addressing"></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 style="margin-bottom: 0in"><br></br>
+</p><p><a name="ws_addressing"></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
mechanisms to address Web services and messages. With Axis2/C, you can use
both WS-Addressing <a href="http://www.w3.org/TR/ws-addr-core/" class="externalLink" title="External Link">version
1.0</a> as well as the <a href="http://www.w3.org/Submission/ws-addressing/" class="externalLink" title="External Link">submission version</a>.</p><p>WS-Addressing is implemented as a module in Axis2/C. Hence as explained in
@@ -635,7 +690,8 @@
</pre></div>
<p>Sets the <code>wsa:RelatesTo</code> header. This header contains a unique
ID which is the message ID of a previously exchanged message. It helps to
-identify a previous message that relates to the current message.</p><p><a name="writing_module"></a></p></div><div class="section"><a name="9__Writing_a_Module"></a><h2>9. Writing a Module</h2><p>A module is an extension point in the Axis2/C engine. Modules are
+identify a previous message that relates to the current message.</p><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="writing_module"></a></p></div><div class="section"><a name="9__Writing_a_Module"></a><h2>9. Writing a Module</h2><p>A module is an extension point in the Axis2/C engine. Modules are
primarily used to WS-* specifications. In other words, quality of service
aspects such as security and reliable messaging can be implemented as modules
and deployed with the Axis2/C engine. <br></br>
@@ -647,26 +703,24 @@
when writing a module. They are <code>axis2_module</code> and
<code>axis2_handler<code>.</code></code></p><p>Every module should have three basic functions that are defined as
function pointer members of the <code>axis2_module_ops</code> struct. This
-struct is defined in the <code>axis2_module.h</code> header file.</p><ol>
- <li><pre>axis2_status_t (AXIS2_CALL *
+struct is defined in the <code>axis2_module.h</code> header file.</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 *
init)(axis2_module_t *module, const
axutil_env_t *env,
axis2_conf_ctx_t *conf_ctx,
- axis2_module_desc_t *module_desc)</pre>
- <p>This function takes care of the module initialization.</p>
- </li>
- <li><pre>axis2_status_t (AXIS2_CALL *
+ axis2_module_desc_t *module_desc);</pre>
+ </td><td>This function takes care of the module initialization.</td></tr>
+ <tr class="b"><td width="410"><pre>axis2_status_t (AXIS2_CALL *
shutdown)(axis2_module_t *module,
- const axutil_env_t *env )</pre>
- <p>Shuts down and cleans up the module.</p>
- </li>
- <li><pre>axis2_status_t (AXIS2_CALL *
+ const axutil_env_t *env );</pre>
+ </td><td>Shuts down and cleans up the module.</td></tr>
+ <tr class="a"><td><pre>axis2_status_t (AXIS2_CALL *
fill_handler_create_func_map)(axis2_module_t *module,
- const axutil_env_t *env )</pre>
- <p>This function fills the hash map of the handler create functions for
- the module.</p>
- </li>
-</ol><p>The module developer has to implement functions with the above signatures
+ const axutil_env_t *env );</pre>
+ </td><td>This function fills the hash map of the handler create functions for
+ the module.</td></tr>
+ </tbody></table><p>The module developer has to implement functions with the above signatures
and assign them to the members of an <code>axis2_module_ops</code> struct
instance. Then that struct instance has to be assigned to the ops member of
an <code>axis2_module</code> struct instance.</p><p><a href="mod_log/mod_log.c.html">mod_log.c</a> has the source for the
@@ -676,7 +730,7 @@
the handler create functions to the module's hash map, which stores the
handler create functions. In the <a href="mod_log/mod_log.c.html">mod_log.c</a> example, the logging module adds
two handlers. The in handler and the out handler that deals with logging
-along with the in-flow and out-flow respectively.</p><div class="subsection"><a name="Writing_Handlers"></a><h3>Writing Handlers</h3><p>A handler is the smallest unit of execution in the Axis2/C engine's
+along with the in-flow and out-flow respectively.</p><div class="subsection"><a name="9_1_Writing_Handlers"></a><h3>9.1 Writing Handlers</h3><p>A handler is the smallest unit of execution in the Axis2/C engine's
execution flow. The engine can have two flows, the in-flow and the out-flow.
A flow is a collection of phases, and a phase in turn is a collection of
handlers. A handler is invoked when the phase within which it lives is
@@ -691,32 +745,58 @@
is responsible for calling the invoke function of the handler.</p><p><a href="mod_log/log_out_handler.c.html">log_out_handler.c</a> contains
the source code of the out handler of the logging module. The implementation
is similar to the in handler, except that it is placed along the out-flow
-when deployed.</p></div><div class="subsection"><a name="Writing_the_module_xml_File"></a><h3>Writing the module.xml File</h3><p>After writing the module, the module.xml file should be written. The
+when deployed.</p></div><div class="subsection"><a name="9_2_Writing_the_module_xml_File"></a><h3>9.2 Writing the module.xml File</h3><p>After writing the module, the module.xml file should be written. The
module.xml file contains all the configuration details for a particular
module. Please see the sample <a href="mod_log/module.xml">module.xml</a>
file for the logging module.</p><p>Please see the <a href="#engaging_module">Engaging a Module</a> section
-for more details on how to package and deploy the module.</p><p><a name="simple_axis_server"></a></p></div></div><div class="section"><a name="10__Simple_Axis_Server"></a><h2>10. Simple Axis Server</h2><p>Simple axis server is the inbuilt HTTP server of Axis2/C.<br></br>
-</p><p>Synopsis :</p>
- <div class="source"><pre> axis2_http_server [-p PORT] [-t TIMEOUT] [-r REPO_PATH][-l LOG_LEVEL] [-f LOG_FILE]
+for more details on how to package and deploy the module.</p><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="simple_axis_server"></a></p></div></div><div class="section"><a name="10__Simple_Axis2_HTTP__Server"></a><h2>10. Simple Axis2 HTTP Server</h2><p>Simple Axis2 HTTP Server is the inbuilt HTTP server of Axis2/C.<br></br>
+</p><div class="subsection"><a name="10_1_Linux_Based_Systems"></a><h3>10.1 Linux Based Systems</h3><p>Synopsis :</p>
+ <div class="source"><pre> axis2_http_server [-p PORT] [-t TIMEOUT] [-r REPO_PATH] [-l LOG_LEVEL] [-f LOG_FILE] [-s LOG_FILE_SIZE]
</pre></div>
- <p>You can use the following options with simple axis server.</p>
+ <p>You can use the following options with simple axis HTTP server.</p>
<div class="source"><pre> -p PORT port number to use, default port is 9090
-r REPO_PATH repository path, default is ../
-t TIMEOUT socket read timeout, default is 30 seconds
-l LOG_LEVEL log level, available log levels:
0 - critical 1 - errors 2 - warnings
- 3 - information 4 - debug 5- trace
+ 3 - information 4 - debug 5- user 6 - trace
Default log level is 4(debug).
-f LOG_FILE log file, default is $AXIS2C_HOME/logs/axis2.log
or axis2.log in current folder if AXIS2C_HOME not set
- -h display this help screen.
+ -s LOG_FILE_SIZE Maximum log file size in mega bytes, default maximum size is 1MB.
+ -h display the help screen.
</pre></div>
<p>Example :</p>
- <div class="source"><pre> axis2_http_server -l 3 -p 8080 -r $AXIS2C_HOME -f /dev/stderr
+ <div class="source"><pre> axis2_http_server -l 3 -p 8080 -r $AXIS2C_HOME -f /dev/stderr
+
</pre></div>
- <p><a name="mod_axis2"></a></p></div><div class="section"><a name="11__Deploying_with_Apache_HTTP_Server_Version_2_x"></a><h2>11. Deploying with Apache HTTP Server Version 2.x</h2><div class="subsection"><a name="Linux_Platform"></a><h3>Linux Platform</h3><p>To build Axis2/C with the Apache HTTP server module, also called
+ </div><div class="subsection"><a name="10_2_MS_Windows_Based_Systems"></a><h3>10.2 MS Windows Based Systems</h3><p>Synopsis :</p>
+ <div class="source"><pre> axis2_http_server.exe [-p PORT] [-t TIMEOUT] [-r REPO_PATH] [-l LOG_LEVEL] [-f LOG_FILE] [-s LOG_FILE_SIZE]
+
+</pre></div>
+ <p>You can use the following options with simple axis HTTP server.</p>
+ <div class="source"><pre> -p PORT port number to use, default port is 9090
+ -r REPO_PATH repository path, default is ../
+ -t TIMEOUT socket read timeout, default is 30 seconds
+ -l LOG_LEVEL log level, available log levels:
+ 0 - critical 1 - errors 2 - warnings
+ 3 - information 4 - debug 5- user 6 - trace
+ Default log level is 4(debug).
+ -f LOG_FILE log file, default is %AXIS2C_HOME%\logs\axis2.log
+ or axis2.log in current folder if AXIS2C_HOME not set
+ -s LOG_FILE_SIZE Maximum log file size in mega bytes, default maximum size is 1MB.
+ -h display the help screen.
+
+</pre></div>
+ <p>Example :</p>
+ <div class="source"><pre> axis2_http_server.exe -l 3 -p 8080 -r %AXIS2C_HOME% -f C:\logs\error.log
+
+</pre></div>
+ <p style="margin-bottom: 0in"><br></br>
+</p><p><a name="mod_axis2"></a></p></div></div><div class="section"><a name="11__Deploying_with_Apache_HTTP_Server_Version_2_x"></a><h2>11. Deploying with Apache HTTP Server Version 2.x</h2><div class="subsection"><a name="11_1_Linux_Platform"></a><h3>11.1 Linux Platform</h3><p>To build Axis2/C with the Apache HTTP server module, also called
mod_axis2, you need to provide the following configuration options on the
Linux platform:</p>
<div class="source"><pre>./configure --with-apache2=[path to Apache2 include directory] [other configure options]
@@ -734,7 +814,7 @@
make install
</pre></div>
- <p>This will install mod_axis2.so into your AXIS2C_INSTALL_DIR/lib folder.</p></div><div class="subsection"><a name="MS_Windows_Platform"></a><h3>MS Windows Platform</h3><p>On the MS Windows platform, you have to provide the Apache2 install
+ <p>This will install mod_axis2.so into your AXIS2C_INSTALL_DIR/lib folder.</p></div><div class="subsection"><a name="11_2_MS_Windows_Platform"></a><h3>11.2 MS Windows Platform</h3><p>On the MS Windows platform, you have to provide the Apache2 install
location in the configure.in file with the setting APACHE_BIN_DIR.
Example:</p>
<div class="source"><pre>APACHE_BIN_DIR = "C:\Program Files\Apache Software Foundation\Apache2.2"
@@ -752,23 +832,23 @@
<p>
This will build mod_axis2.dll and copy it to AXIS2C_INSTALL_DIR\lib directory.
-</p></div><div class="subsection"><a name="Deploying_mod_axis2"></a><h3>Deploying mod_axis2</h3><p><font color="#666666">NOTE: To execute some of the commands given below,
+</p></div><div class="subsection"><a name="11_3_Deploying_mod_axis2"></a><h3>11.3 Deploying mod_axis2</h3><p><font color="#666666">NOTE: To execute some of the commands given below,
you might require super user privileges on your machine.</font></p><p>Copy the mod_axis2 shared library <font color="#4169E1">(libmod_axis2.so.0.0.0 on Linux and mod_axis2.dll on MS
Windows)</font> to the Apache2 modules directory as mod_axis2.so</p><p>On Linux</p>
- <div class="source"><pre> cp $AXIS2C_HOME/lib/libmod_axis2.so.0.0.0
- /usr/lib/apache2/modules/mod_axis2.so copy C:\axis2c\build\deploy\lib\mod_axis2.dll
- C:\Apache2\modules\mod_axis2.so</pre></div>
- <p>
-On MS Windows
-
+ <div class="source"><pre> cp $AXIS2C_HOME/lib/libmod_axis2.so.0.0.0 /usr/lib/apache2/modules/mod_axis2.so
+</pre></div>
+ <p>On MS Windows</p>
+ <div class="source"><pre> copy /Y "%AXIS2C_HOME%\lib\mod_axis2.dll" C:\Apache2\modules\
-</p><p>Edit the Apache2's configuration file (generally httpd.conf) and add the
+</pre></div>
+ <p>Edit the Apache2's configuration file (generally httpd.conf) and add the
following directives at the end of the file.</p>
<div class="source"><pre>LoadModule axis2_module MOD_AXIS2_INSTALL_DIR
Axis2RepoPath AXIS2C_INSTALL_DIR
Axis2LogFile PATH_TO_LOG_FILE
Axis2LogLevel LOG_LEVEL
Axis2ServiceURLPrefix PREFIX
+Axis2MaxLogFileSize SIZE_IN_MB
<Location /axis2>
SetHandler axis2_module
</Location>
@@ -799,14 +879,23 @@
<li>debug - log debug information and above, this is the default log level
used</li>
<li>trace - log trace messages and above</li>
-</ul><p>PREFIX has to be replaced with the prefix to be used with the
+</ul><p>SIZE_IN_MB must be replaced by the size of the particular resource in MB, rounded to
+the nearest whole value.<br></br>
+<br></br>PREFIX has to be replaced with the prefix to be used with the
service endpoints. This is optional and defaults to "services".
As an example, if you have "web_services" as the prefix, then all the
services hosted would have the endpoint prefix of : <br></br>
http://localhost/axis2/web_services <br></br>
If you wish, you can also change the location as well by replacing "/axis2" in
<Location /axis2> setting with whatever you wish.
-</p><p>To ensure that everything works fine, start Apache2 (restart if it is
+</p><p><font color="#666666">NOTE: If you want to use a Shared Global Pool with Apache
+you have to give another entry called Axis2GlobalPoolSize.You have to give the
+size of the shared global pool in MB.If you doesn't set the value or if you set a
+negative value Apache module doesn't create shared global pool.</font></p>
+ <div class="source"><pre>Axis2GlobalPoolSize SIZE_IN_MB
+
+</pre></div>
+ <p>To ensure that everything works fine, start Apache2 (restart if it is
already running) and test whether the mod_axis2 module is loaded correctly by
accessing the URL: <a href="http://localhost/axis2/services" class="externalLink" title="External Link">http://localhost/axis2/services</a>.<br></br>
</p><p>This should show the list of services deployed with Axis2/C. Then you
@@ -826,12 +915,13 @@
chance that mod_axis2 is crashing. You can have a look at the error.log
file of Apache2 to get an idea on what is going wrong. This file is
usually placed in the AXIS2C_INSTALL_DIR/logs folder.</li>
-</ul><p><a name="IIS"></a></p></div></div><div class="section"><a name="12__Deploying_with_Microsoft_IIS_Server"></a><h2>12. Deploying with Microsoft IIS Server</h2><p>Use the Axis2/C VC project or makefile to buid the
+</ul><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="IIS"></a></p></div></div><div class="section"><a name="12__Deploying_with_Microsoft_IIS_Server"></a><h2>12. Deploying with Microsoft IIS Server</h2><p>Use the Axis2/C VC project or makefile to buid the
component.</p><p>In this document I assume that the mod_axis2_IIS.dll
-is in the directory <code>c:\axis2c\lib\mod_axis2_IIS.dll</code> and axis2c_home
+is in the directory <code>c:\axis2c\lib\mod_axis2_IIS.dll</code> and AXIS2C_HOME
is <code>c:\axis2c</code></p><p>Add the following key to the
registery.</p><p>HKEY_LOCAL_MACHINE\SOFTWARE\Apache Axis2c\IIS ISAPI
-Redirector</p><p>Add a string value with the name axis2c_home and a
+Redirector</p><p>Add a string value with the name AXIS2C_HOME and a
value of c:\axis2c</p><p>Add a string value with the name log_file and a value
of c:\axis2c\logs\axis2.log</p><p>Add a string value with the name log_level. The value
can be either trace, error, info, critical, debug, or warning.</p><p>Using the IIS management console, add a new virtual
@@ -839,7 +929,8 @@
physical path should be the directory in which you placed mod_axis2_IIS.dll (in our example it is
c:\axis2c\lib). When creating this new virtual directory, assign execute access to it.</p><p>By using the IIS management console, add
mod_axis2_IIS.dll as a filter in your IIS/PWS web site and restart the IIS
-admin service.</p><p><a name="ssl_client"></a></p></div><div class="section"><a name="13__Using_SSL_Client"></a><h2>13. Using SSL Client</h2><div class="subsection"><a name="Building_and_Configuring_the_Client"></a><h3>Building and Configuring the Client</h3><p>In order to allow an Axis2/C client to communicate with an SSL enabled
+admin service.</p><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="ssl_client"></a></p></div><div class="section"><a name="13__Using_SSL_Client"></a><h2>13. Using SSL Client</h2><div class="subsection"><a name="13_1_Building_and_Configuring_the_Client"></a><h3>13.1 Building and Configuring the Client</h3><p>In order to allow an Axis2/C client to communicate with an SSL enabled
server, we need to compile Axis2/C with SSL support enabled.</p><p>To build with SSL client support, first of all, make sure you have
installed <a href="http://www.openssl.org/" class="externalLink" title="External Link">OpenSSL</a> on your machine. Then
you can start building with SSL client support. This can be achieved on Linux
@@ -848,7 +939,7 @@
%make<br></br>
%make install<br></br>
</code></p><p>On MS Windows, set <code>ENABLE_SSL=1</code> in the
-<code>configure.in</code> file and run the 'nmake all' command.</p><p><a name="client_chain"></a></p></div><div class="subsection"><a name="Creating_the_Client_Certificate_Chain_File"></a><h3>Creating the Client Certificate Chain File</h3><p>If you need SSL client authentication, Axis2/C requires you to provide the
+<code>configure.in</code> file and run the 'nmake all' command.</p><p><a name="client_chain"></a></p></div><div class="subsection"><a name="13_1_1_Creating_the_Client_Certificate_Chain_File"></a><h3>13.1.1 Creating the Client Certificate Chain File</h3><p>If you need SSL client authentication, Axis2/C requires you to provide the
client certificate and the private key file in a single file. Such a file
which contains both the certificate and relevant private key is called a
certificate chain file. Creating such a file is very easy. Assume that the
@@ -858,7 +949,7 @@
and the private key file in that order, in to another file, say
<code>client.pem</code>.</p><p>On Linux you can do this as follows: <code>%cat client.crt client.key >
client.pem</code></p><p>On MS Windows, you can do this by copying the contents of client.crt and
-client.key files and saving them in a file named client.pem using Notepad.</p></div><div class="subsection"><a name="Configuration"></a><h3>Configuration</h3><p>Uncomment the following in the <code>axis2.xml</code> file. This will
+client.key files and saving them in a file named client.pem using Notepad.</p></div><div class="subsection"><a name="13_1_2_Configuration"></a><h3>13.1.2 Configuration</h3><p>Uncomment the following in the <code>axis2.xml</code> file. This will
enable the SSL transport for Axis2/C, by recognizing "https" in an end point
reference (EPR).</p>
<div class="source"><pre><transportSender name="https" class="axis2_http_sender">
@@ -894,9 +985,9 @@
sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > cert.pem
</pre></div>
- <p>NOTE: Instead of setting these parameters in the <code>axis2.xml</code>
+ <p><font color="#666666">NOTE: Instead of setting these parameters in the <code>axis2.xml</code>
file, you can also set these parameters programmatically in your client
-code.</p></div><div class="subsection"><a name="Configuring_the_Server"></a><h3>Configuring the Server</h3><p>Here we will only look at the configuration of the Apache HTTP Web server.
+code.</font></p></div><div class="subsection"><a name="13_2_Configuring_the_Server"></a><h3>13.2 Configuring the Server</h3><p>Here we will only look at the configuration of the Apache HTTP Web server.
Refer to the '<a href="#mod_axis2">Deploying with Apache HTTP Server Version2.x</a>' section for information on deploying Axis2/C as an Apache
module.</p><p>For more detailed information on SSL configuration, please refer to <a href="http://httpd.apache.org/docs/2.0/ssl/#documentation" class="externalLink" title="External Link">Apache2 SSL/TLS
documentation</a>.</p><p>In the <code>httpd.conf</code> file, add the following configuration
@@ -905,33 +996,91 @@
SSLCertificateKeyFile /path/to/private/key/file<br></br>
SSLCACertificateFile /path/to/CA/certificate/file<br></br>
SSLVerifyClient require<br></br>
-SSLVerifyDepth 1</code></p><p>NOTE: The last two lines, <code>SSLVerifyClient</code> and
+SSLVerifyDepth 1</code></p><p><font color="#666666">NOTE: The last two lines, <code>SSLVerifyClient</code> and
<code>SSLVerifyDepth</code> are only needed when you need client
-authentication.</p><p><a name="proxy"></a></p></div></div><div class="section"><a name="14__Using_Proxy_Support"></a><h2>14. Using Proxy Support</h2><p>When using a proxy, there are two methods for specifying proxy
+authentication.</font></p><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="proxy"></a></p></div></div><div class="section"><a name="14__Using_Proxy_Support"></a><h2>14. Using Proxy Support</h2><p>When using a proxy, there are two methods for specifying proxy
settings:</p><ol>
<li>Specify proxy settings in axis2.xml</li>
<li>Provide proxy settings using service client API</li>
-</ol><div class="subsection"><a name="Specifying_Proxy_Settings_in_axis2_xml"></a><h3>Specifying Proxy Settings in axis2.xml</h3>
+</ol><div class="subsection"><a name="14_1_Specifying_Proxy_Settings_in_axis2_xml"></a><h3>14.1 Specifying Proxy Settings in axis2.xml</h3>
<div class="source"><pre><transportSender name="http" class="axis2_http_sender">
<parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>
- <parameter name="PROXY" proxy_host="127.0.0.1" proxy_port="8080" locked="true"/>
+ <parameter name="PROXY" proxy_host="127.0.0.1" proxy_port="8080" proxy_username="" proxy_password="" locked="true"/>
</transportSender>
</pre></div>
- </div><div class="subsection"><a name="Providing_Proxy_Settings_Using_Service_Client_API"></a><h3>Providing Proxy Settings Using Service Client API</h3><p>You can specify proxy settings using the following function with the
+ </div><div class="subsection"><a name="14_2_Providing_Proxy_Settings_Using_Service_Client_API"></a><h3>14.2 Providing Proxy Settings Using Service Client API</h3><p>You can specify proxy settings using the following function with the
service client:</p>
<div class="source"><pre>axis2_svc_client_set_proxy(axis2_svc_client_t *svc_client,
const axutil_env_t *env,
axis2_char_t *proxy_host,
axis2_char_t *proxy_port);
+
+</pre></div>
+ <p style="margin-bottom: 0in"><br></br>
+</p><p><a name="proxy_auth"></a></p></div></div><div class="section"><a name="15__Using_Proxy_Authentication_Support"></a><h2>15. Using Proxy Authentication Support</h2><p>When using proxy authentication, there are three methods for specifying proxy
+authentication settings:</p><ol>
+ <li>Specify proxy settings with authentication in axis2.xml</li>
+ <li>Provide proxy settings with authentication using service client API</li>
+ <li>Provide proxy authentication settings using service client options</li>
+</ol><div class="subsection"><a name="15_1_Specifying_Proxy_Settings_with_Authentication_in_axis2_xml"></a><h3>15.1 Specifying Proxy Settings with Authentication in axis2.xml</h3>
+ <div class="source"><pre><transportSender name="http" class="axis2_http_sender">
+ <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>
+ <parameter name="PROXY" proxy_host="127.0.0.1" proxy_port="8080" locked="true"/>
+</transportSender>
+
+</pre></div>
+ </div><div class="subsection"><a name="15_2_Providing_Proxy_Settings_with_Authentication_Using_Service_Client_API"></a><h3>15.2 Providing Proxy Settings with Authentication Using Service Client API</h3><p>You can specify proxy authentication settings using the following function with the
+service client:</p>
+ <div class="source"><pre>axis2_svc_client_set_proxy_with_auth(axis2_svc_client_t *svc_client,
+ const axutil_env_t *env,
+ axis2_char_t *proxy_host,
+ axis2_char_t *proxy_port,
+ axis2_char_t *username,
+ axis2_char_t *password);
+
+</pre></div>
+ </div><div class="subsection"><a name="15_3_Providing_Proxy_Authentication_Settings_Using_Service_Client_Options"></a><h3>15.3 Providing Proxy Authentication Settings Using Service Client Options</h3><p>You can specify proxy authentication settings using the following function with the
+service client options:</p>
+ <div class="source"><pre>axis2_options_set_proxy_auth_info(
+ axis2_options_t * options,
+ const axutil_env_t * env,
+ const axis2_char_t * username,
+ const axis2_char_t * password,
+ const axis2_char_t * auth_type);
+</pre></div>
+ <p>In <code>auth_type</code>, use <b>Basic</b> to force Basic Authentication or <b>Digest</b> to force Digest
+Authentication. Leave this field NULL if you are not forcing authentication.</p><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="http_auth"></a></p></div></div><div class="section"><a name="16__Using_HTTP_Authentication_Support"></a><h2>16. Using HTTP Authentication Support</h2><p>When using HTTP authentication, there are two methods for specifying proxy
+authentication settings:</p><ol>
+ <li>Specify HTTP authentication settings in axis2.xml</li>
+ <li>Provide HTTP authentication settings using service client options</li>
+</ol><div class="subsection"><a name="16_1_Specifying_HTTP_Authentication_Settings_in_axis2_xml"></a><h3>16.1 Specifying HTTP Authentication Settings in axis2.xml</h3>
+ <div class="source"><pre><transportSender name="http" class="axis2_http_sender">
+ <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>
+ <parameter name="HTTP-Authentication" username="your username" password="your password" locked="true"/>
+</transportSender>
+
</pre></div>
- <p><a name="wsdl2c"></a></p></div></div><div class="section"><a name="15__WSDL2C_Tool"></a><h2>15. WSDL2C Tool</h2><p>WSDL2C tool that comes with Axis2/Java supports the generation of Axis2/C
+ </div><div class="subsection"><a name="16_2_Providing_HTTP_Authentication_Settings_Using_Service_Client_Options"></a><h3>16.2 Providing HTTP Authentication Settings Using Service Client Options</h3><p>You can specify HTTP authentication settings using the following function with the
+service client options:</p>
+ <div class="source"><pre>axis2_options_set_http_auth_info(
+ axis2_options_t * options,
+ const axutil_env_t * env,
+ const axis2_char_t * username,
+ const axis2_char_t * password,
+ const axis2_char_t * auth_type);
+</pre></div>
+ <p>In <code>auth_type</code>, use <b>Basic</b> to force HTTP Basic Authentication or <b>Digest</b> to force HTTP Digest
+Authentication. Leave this field NULL if you are not forcing authentication.</p><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="wsdl2c"></a></p></div></div><div class="section"><a name="17__WSDL2C_Tool"></a><h2>17. WSDL2C Tool</h2><p>WSDL2C tool that comes with Axis2/Java supports the generation of Axis2/C
stubs and skeletons for WSDL files. This is a Java tool that can be used to
generate C code that works with Axis2/C API. You should use <a href="http://svn.apache.org/viewvc/webservices/axis2/trunk/java" class="externalLink" title="External Link">Axis2/Java
SVN</a> revision 529533 or later revisions. You can download the <a href="http://people.apache.org/dist/axis2/nightly/" class="externalLink" title="External Link">Axis2/Java nightly
build</a> and use those binaries to generate code. Check out a <a href="http://ws.apache.org/axis2/1_2/reference.html#wsdl2java" class="externalLink" title="External Link">basic
guide</a> on the Java tool.</p><p>Before you run the tool, make sure that all the .jar library files that
-come with Axis2/Java are added to the CLASSPATH environment variable.</p><div class="subsection"><a name="Generating_Service_Skeletons"></a><h3>Generating Service Skeletons</h3><p>The tool can be run with the following parameters and generate the service
+come with Axis2/Java are added to the CLASSPATH environment variable.</p><div class="subsection"><a name="17_1_Generating_Service_Skeletons"></a><h3>17.1 Generating Service Skeletons</h3><p>The tool can be run with the following parameters and generate the service
skeleton and other required files with ADB (Axis Data Binding) support.</p>
<div class="source"><pre>java org.apache.axis2.wsdl.WSDL2C -uri interoptestdoclitparameters.wsdl -ss -sd -d adb -u
@@ -957,7 +1106,7 @@
You can also go through the generated header files and understand the API in
line with the WSDL file that you used to generate the code.
-</p></div><div class="subsection"><a name="Generating_Client_Stubs"></a><h3>Generating Client Stubs</h3><p>The WSDL2C code generator tool provides support for generating client
+</p></div><div class="subsection"><a name="17_2_Generating_Client_Stubs"></a><h3>17.2 Generating Client Stubs</h3><p>The WSDL2C code generator tool provides support for generating client
stubs as well. You can generate the required stubs from a given WSDL with the
other supporting files. Use following parameters to generate the Axis2/C
client stub code with ADB support.</p>
@@ -972,7 +1121,104 @@
<p>Like in the case of service skeletons, you have to fill in the business
logic as required in the client stubs as well. To do this, go through the
header files generated and understand the API in line with the WSDL file that
-you used to generate the code.</p><p><a name="appA"></a></p></div></div><div class="section"><a name="Appendix_A"></a><h2>Appendix A</h2><div class="subsection"><a name="axis2_xml"></a><h3>axis2.xml</h3><p>The axis2.xml file is the configuration file for Axis2/C. It has 6 top
+you used to generate the code.</p><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="tcptrans"></a></p></div></div><div class="section"><a name="18__TCP_Transport"></a><h2>18. TCP Transport</h2><div class="subsection"><a name="18_1_Building_AXIS2C_enabling_TCP"></a><h3>18.1 Building AXIS2C enabling TCP</h3><p>This section will guide you through installing Axis2C with tcp enabled, and this
+also includes how to test it by running samples. Please note that both the Server and
+the Client must be built with TCP enabled.</p></div><div class="subsection"><a name="18_1_1_Linux_Based_Systems"></a><h3>18.1.1 Linux Based Systems</h3><ol>
+<li>When you are installing, you have to use the configure command with
+the option to enable tcp by providing the following argument:</li>
+<pre> ./configure --enable-tcp=yes
+ make
+ make install</pre>
+
+<li>Then to confirm that you have successfully built the source with tcp enabled
+you can check in your $AXIS2C_HOME/lib folder for following files:</li>
+<pre> libaxis2_tcp_sender.so
+ libaxis2_tcp_reciever.so</pre>
+
+<li>To setup the tcp transport sender, you have to edit the axis2.xml by uncommenting
+following entry:</li>
+<pre> <transportSender name="tcp" class="axis2_tcp_sender">
+ <parameter name="PROTOCOL" locked="false">TCP</parameter>
+ </transportSender></pre>
+</ol></div><div class="subsection"><a name="18_1_2_MS_Windows_Based_Systems"></a><h3>18.1.2 MS Windows Based Systems</h3><ol>
+<li>When you are installing, you have to set the configure option to enable tcp
+by specifying in <code>configure.in</code>:</li>
+<pre> WITH_TCP = 1</pre>
+
+<li>Then to confirm that you have successfully built the source with tcp enabled
+you can check in your %AXIS2C_HOME%\lib folder for following files:</li>
+<pre> axis2_tcp_sender.dll
+ axis2_tcp_reciever.dll</pre>
+
+<li>To setup the tcp transport sender, you have to edit the axis2.xml by uncommenting
+following entry:</li>
+<pre> <transportSender name="tcp" class="axis2_tcp_sender">
+ <parameter name="PROTOCOL" locked="false">TCP</parameter>
+ </transportSender></pre>
+</ol></div><div class="subsection"><a name="18_2_Server_Side"></a><h3>18.2 Server Side</h3><ul>
+<li>To run the tcp server on Linux based systems, you have to start the tcp
+server which runs in 9091 as its default port.</li>
+<pre> cd $AXIS2C_HOME/bin/
+ ./axis2_tcp_server</pre>
+<li>To run the tcp server on MS Windows based systems, you have to start the tcp
+server as,</li>
+<pre> cd %AXIS2C_HOME%\bin
+ axis2_tcp_server.exe</pre>
+</ul></div><div class="subsection"><a name="18_2_1_Simple_Axis2_TCP_Server"></a><h3>18.2.1 Simple Axis2 TCP Server</h3><p>Simple Axis2 TCP Server is the inbuilt TCP server of Axis2/C.<br></br>
+</p></div><div class="subsection"><a name="18_2_1_1_Linux_Based_Systems"></a><h3>18.2.1.1 Linux Based Systems</h3><p>Synopsis :</p>
+ <div class="source"><pre> axis2_tcp_server [-p PORT] [-t TIMEOUT] [-r REPO_PATH] [-l LOG_LEVEL] [-f LOG_FILE] [-s LOG_FILE_SIZE]
+
+</pre></div>
+ <p>You can use the following options with simple axis TCP server.</p>
+ <div class="source"><pre> -p PORT port number to use, default port is 9091
+ -r REPO_PATH repository path, default is ../
+ -t TIMEOUT socket read timeout, default is 30 seconds
+ -l LOG_LEVEL log level, available log levels:
+ 0 - critical 1 - errors 2 - warnings
+ 3 - information 4 - debug 5- user 6 - trace
+ Default log level is 4(debug).
+ -f LOG_FILE log file, default is $AXIS2C_HOME/logs/axis2.log
+ or axis2.log in current folder if AXIS2C_HOME not set
+ -s LOG_FILE_SIZE Maximum log file size in mega bytes, default maximum size is 1MB.
+ -h display the help screen.
+
+</pre></div>
+ <p>Example :</p>
+ <div class="source"><pre> axis2_tcp_server -l 3 -p 8080 -r $AXIS2C_HOME -f /dev/stderr
+
+</pre></div>
+ </div><div class="subsection"><a name="18_2_1_2_MS_Windows_Based_Systems"></a><h3>18.2.1.2 MS Windows Based Systems</h3><p>Synopsis :</p>
+ <div class="source"><pre> axis2_tcp_server.exe [-p PORT] [-t TIMEOUT] [-r REPO_PATH] [-l LOG_LEVEL] [-f LOG_FILE] [-s LOG_FILE_SIZE]
+
+</pre></div>
+ <p>You can use the following options with simple axis TCP server.</p>
+ <div class="source"><pre> -p PORT port number to use, default port is 9091
+ -r REPO_PATH repository path, default is ../
+ -t TIMEOUT socket read timeout, default is 30 seconds
+ -l LOG_LEVEL log level, available log levels:
+ 0 - critical 1 - errors 2 - warnings
+ 3 - information 4 - debug 5- user 6 - trace
+ Default log level is 4(debug).
+ -f LOG_FILE log file, default is %AXIS2C_HOME%\logs\axis2.log
+ or axis2.log in current folder if AXIS2C_HOME not set
+ -s LOG_FILE_SIZE Maximum log file size in mega bytes, default maximum size is 1MB.
+ -h display the help screen.
+
+</pre></div>
+ <p>Example :</p>
+ <div class="source"><pre> axis2_tcp_server.exe -l 3 -p 8080 -r %AXIS2C_HOME% -f C:\logs\error.log
+
+</pre></div>
+ </div><div class="subsection"><a name="18_3_Client_Side"></a><h3>18.3 Client Side</h3><ul>
+<li>In your service client you have to give the end point address
+ adding tcp as the URI Schema name in the client's code.</li>
+<pre>tcp://[service_hostname]:[service_port]/axis2/services/your_service_name</pre>
+
+<li>You can use TCPMon to figure out how the message is transferred (without having
+ it's http headers) after you've built Axis2C enabling tcp.</li>
+</ul><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="appA"></a></p></div></div><div class="section"><a name="Appendix_A_-_axis2_xml"></a><h2>Appendix A - axis2.xml</h2><p>The axis2.xml file is the configuration file for Axis2/C. It has 6 top
level elements. They are <em>parameter, transportReceiver, transportSender,
module, phaseOrder</em> and <em>messageReceiver</em>. The following sections
describe these elements, their sub elements, element attributes, possible
@@ -980,7 +1226,7 @@
file.</p><table class="bodyTable"><tbody>
<tr class="b"><th>Attribute</th><th>Possible Values</th></tr>
<tr class="a"><td>name</td><td>Axis2/C</td></tr>
- </tbody></table></div><div class="subsection"><a name="parameter"></a><h3>parameter</h3><p>In Axis2/C, a parameter is a name value pair. Each and every top level
+ </tbody></table><div class="subsection"><a name="parameter"></a><h3>parameter</h3><p>In Axis2/C, a parameter is a name value pair. Each and every top level
parameter available in the axis2.xml (direct sub elements of the root
element) will be stored as parameters as <code>axis2_conf</code>. Therefore,
the top level parameters set in the configuration file can be accessed via
@@ -1101,7 +1347,7 @@
<li>MessageOut</li>
</ul><table class="bodyTable"><caption></caption><tbody>
<tr class="b"><th>Attribute</th><th>Description</th><th>Possible Values</th></tr>
- <tr class="a"><td>name</td><td>Specifies the name of the phase</td><td>TransportIn, Dispatch, PreDispatch, PostDispatch, MessageOut
+ <tr class="a"><td>name</td><td>Specifies the name of the phase</td><td>Transport, Dispatch, PreDispatch, PostDispatch, MessageOut
<p>User defined phases (can have a user defined name)</p>
</td></tr>
@@ -1132,14 +1378,15 @@
<p>On MS Windows, <em>foo.dll</em>.</p>
</td></tr>
- </tbody></table><p><a name="appB"></a></p></div></div><div class="section"><a name="Appendix_B"></a><h2>Appendix B</h2><div class="subsection"><a name="services_xml"></a><h3>services.xml</h3><p>Configuration of a service is specified using a services.xml. Each service
+ </tbody></table><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="appB"></a></p></div></div><div class="section"><a name="Appendix_B_-_services_xml"></a><h2>Appendix B - services.xml</h2><p>Configuration of a service is specified using a services.xml. Each service
or service archive file needs to have a services.xml in order to be a valid
service. The following sections describe the elements of the services.xml
file.</p><p>If services.xml describes a single service, the root element is
<em>service</em>. If it is describing a service group, then the root element
is <em>serviceGroup</em>. The<em> service</em> element will be a child
element of serviceGroup if there are multiple services specified in
-services.xml.</p></div><div class="subsection"><table class="bodyTable"><caption></caption><tbody>
+services.xml.</p><div class="subsection"><table class="bodyTable"><caption></caption><tbody>
<tr class="b"><th>Attributes</th><th>Description</th><th>Possible Values</th></tr>
<tr class="a"><td>name</td><td>Name of the service or service group.</td><td>Depends on the service or the service group.<br></br>
Examples: echo, sg_math</td></tr>
@@ -1170,8 +1417,9 @@
<p>On MS Windows, <em>foo.dll</em>.</p>
</td></tr>
- </tbody></table><p><a name="appC"></a></p></div></div><div class="section"><a name="Appendix_C"></a><h2>Appendix C</h2><div class="subsection"><a name="module_xml"></a><h3>module.xml</h3><p>The module.xml file provides the configuration details for a particular
-module in Axis2/C. The top level element is <em>module</em>.</p></div><div class="subsection"><a name="module"></a><h3>module</h3><table class="bodyTable"><caption></caption><tbody>
+ </tbody></table><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="appC"></a></p></div></div><div class="section"><a name="Appendix_C_-_module_xml"></a><h2>Appendix C - module.xml</h2><p>The module.xml file provides the configuration details for a particular
+module in Axis2/C. The top level element is <em>module</em>.</p><div class="subsection"><a name="module"></a><h3>module</h3><table class="bodyTable"><caption></caption><tbody>
<tr class="a"><th>Attributes</th><th>Description</th><th>Possible Values</th></tr>
<tr class="b"><td>name</td><td>Name of the module</td><td>Example- addressing</td></tr>
<tr class="a"><td>class</td><td>Specifies the shared library which implements the module.</td><td>Name of the shared library.
@@ -1235,7 +1483,8 @@
</tbody></table><p>Sub elements of <em>operation</em> : Any number of parameters can be
included as sub elements in the operation element.</p><p>The <em>messageReceiver</em> parameter specifies the message receiver the
message is intended for. If it is not set, the default message receiver is
-used.</p><p></p><p><a name="appD"></a></p></div></div><div class="section"><a name="Appendix_D"></a><h2>Appendix D</h2><div class="subsection"><a name="axis2_options"></a><h3>axis2_options</h3><p>This section describes various types of options that can be set with
+used.</p><p style="margin-bottom: 0in"><br></br>
+</p><p><a name="appD"></a></p></div></div><div class="section"><a name="Appendix_D_-_axis2_options"></a><h2>Appendix D - axis2_options</h2><p>This section describes various types of options that can be set with
<code>axis2_options</code>. These options are used by the service client
before sending messages.</p><p><strong>axis2_options_set_action(options, env, action)</strong></p><p>Sets the WS-Addressing action that is to be set in the addressing SOAP
headers.</p><table class="bodyTable"><caption></caption><tbody>
@@ -1375,4 +1624,22 @@
<tr class="b"><td>axis2_options_t *options</td><td>Pointer to the options struct.</td></tr>
<tr class="a"><td>const axutil_env_t *env</td><td>Pointer to the environment struct.</td></tr>
<tr class="b"><td>axis2_bool_t enable_rest</td><td>AXIS2_TRUE if REST is to be enabled, else AXIS2_FALSE</td></tr>
- </tbody></table><p></p></div></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2005-2007, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
+ </tbody></table><p><strong>axis2_options_set_http_auth_info(options, env,
+username, password, auth_type)</strong></p><p>Sets HTTP Authentication information.</p><table class="bodyTable"><caption></caption><tbody>
+ <tr class="a"><th>Parameter</th><th>Description</th></tr>
+ <tr class="b"><td>axis2_options_t *options</td><td>Pointer to the options struct.</td></tr>
+ <tr class="a"><td>const axutil_env_t *env</td><td>Pointer to the environment struct.</td></tr>
+ <tr class="b"><td>const axis2_char_t *username</td><td>String representing useranme</td></tr>
+ <tr class="a"><td>const axis2_char_t *password</td><td>String representing password.</td></tr>
+ <tr class="b"><td>const axis2_char_t *auth_type</td><td>use "Basic" to force basic authentication and "Digest" to
+ force digest authentication or NULL for not forcing authentication</td></tr>
+ </tbody></table><p><strong>axis2_options_set_proxy_auth_info(options, env,
+username, password, auth_type)</strong></p><p>Sets Proxy Authentication information.</p><table class="bodyTable"><caption></caption><tbody>
+ <tr class="a"><th>Parameter</th><th>Description</th></tr>
+ <tr class="b"><td>axis2_options_t *options</td><td>Pointer to the options struct.</td></tr>
+ <tr class="a"><td>const axutil_env_t *env</td><td>Pointer to the environment struct.</td></tr>
+ <tr class="b"><td>const axis2_char_t *username</td><td>String representing useranme</td></tr>
+ <tr class="a"><td>const axis2_char_t *password</td><td>String representing password.</td></tr>
+ <tr class="b"><td>const axis2_char_t *auth_type</td><td>use "Basic" to force basic authentication and "Digest" to
+ force digest authentication or NULL for not forcing authentication</td></tr>
+ </tbody></table></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2005-2008, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
Modified: webservices/axis2/site/c/docs/hello/client/hello.c.html
URL: http://svn.apache.org/viewvc/webservices/axis2/site/c/docs/hello/client/hello.c.html?rev=612416&r1=612415&r2=612416&view=diff
==============================================================================
--- webservices/axis2/site/c/docs/hello/client/hello.c.html (original)
+++ webservices/axis2/site/c/docs/hello/client/hello.c.html Wed Jan 16 02:59:27 2008
@@ -2,8 +2,8 @@
@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: 30 September 2007
- | Doc for 1.1.0</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuApache_Axis2_C"><h5>Apache Axis2/C</h5><ul><li class="none"><a href="../../../index.html">Apache Axis2/C 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="../../../lists_issues.html">Get Involved</a><ul><li class="none"><a href="../../../lists_issues.html">Mailing Lists & Issue Tracking</a></li><li class="none"><a href="../../../svn.html">Checkout Source Code</a></li></ul></li><li class="expanded"><a href="../../../
coding_conventions.html">Developer Guidelines</a><ul><li class="none"><a href="../../../coding_conventions.html">Coding Convention</a></li><li class="none"><a href="../../../versioning.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"><font face="Monospace">
+ Last published: 14 January 2008
+ | Doc for 1.2.0</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuApache_Axis2_C"><h5>Apache Axis2/C</h5><ul><li class="none"><a href="../../../index.html">Apache Axis2/C 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="../../../lists_issues.html">Get Involved</a><ul><li class="none"><a href="../../../lists_issues.html">Mailing Lists & Issue Tracking</a></li><li class="none"><a href="../../../svn.html">Checkout Source Code</a></li></ul></li><li class="expanded"><a href="../../../
coding_conventions.html">Developer Guidelines</a><ul><li class="none"><a href="../../../coding_conventions.html">Coding Convention</a></li><li class="none"><a href="../../../versioning.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"><font face="Monospace">
<font color="#808080"><i>/*<br></br>
* Copyright 2004,2005 The Apache Software Foundation.<br></br>
*<br></br>
@@ -154,4 +154,4 @@
<font color="#000000"><b>return</b></font> <font color="#000000">NULL</font>;<br></br>
}<br></br>
<br></br>
- </font></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2005-2007, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
+ </font></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2005-2008, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
Modified: webservices/axis2/site/c/docs/index.html
URL: http://svn.apache.org/viewvc/webservices/axis2/site/c/docs/index.html?rev=612416&r1=612415&r2=612416&view=diff
==============================================================================
--- webservices/axis2/site/c/docs/index.html (original)
+++ webservices/axis2/site/c/docs/index.html Wed Jan 16 02:59:27 2008
@@ -2,8 +2,8 @@
@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: 30 September 2007
- | Doc for 1.1.0</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuApache_Axis2_C"><h5>Apache Axis2/C</h5><ul><li class="none"><a href="../index.html">Apache Axis2/C 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="../lists_issues.html">Get Involved</a><ul><li class="none"><a href="../lists_issues.html">Mailing Lists & Issue Tracking</a></li><li class="none"><a href="../svn.html">Checkout Source Code</a></li></ul></li><li class="expanded"><a href="../coding_conventions.html">Developer Guidelines</a><ul><li cla
ss="none"><a href="../coding_conventions.html">Coding Convention</a></li><li class="none"><a href="../versioning.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="Apache_Axis2_C_Documentation"></a><h2>Apache Axis2/C Documentation</h2><div class="subsection"><a name="Getting_Started"></a><h3>Getting Started</h3><ul>
+ Last published: 14 January 2008
+ | Doc for 1.2.0</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuApache_Axis2_C"><h5>Apache Axis2/C</h5><ul><li class="none"><a href="../index.html">Apache Axis2/C 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="../lists_issues.html">Get Involved</a><ul><li class="none"><a href="../lists_issues.html">Mailing Lists & Issue Tracking</a></li><li class="none"><a href="../svn.html">Checkout Source Code</a></li></ul></li><li class="expanded"><a href="../coding_conventions.html">Developer Guidelines</a><ul><li cla
ss="none"><a href="../coding_conventions.html">Coding Convention</a></li><li class="none"><a href="../versioning.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="Apache_Axis2_C_Documentation"></a><h2>Apache Axis2/C Documentation</h2><div class="subsection"><a name="Getting_Started"></a><h3>Getting Started</h3><ul>
<li><a href="installationguide.html">Installation Guide</a></li>
</ul></div><div class="subsection"><a name="Manual"></a><h3>Manual</h3><ul>
<li><a href="axis2c_manual.html">Axis2/C Manual</a></li>
@@ -13,4 +13,4 @@
<li><a href="architecture_notes.html">C Specific Architecture Notes</a></li>
<li><a href="om_tutorial.html">OM Tutorial</a></li>
<li><a href="../coding_conventions.html">Coding Conventions in Axis2/C</a></li>
-</ul></div></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2005-2007, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
+</ul></div></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2005-2008, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-cvs-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-cvs-help@ws.apache.org