axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dee...@apache.org
Subject svn commit: r498925 [1/4] - in /webservices/axis2/trunk/java/xdocs: ./ 1_1/ 1_1/jibx/ download/1_1/ download/1_1_1/ modules/ modules/rampart/1_0/ modules/rampart/1_1/ modules/rampart/1_1/sec-conf/ modules/wss4j/0_94/0.94/ modules/wss4j/0_95/ modules/ws...
Date Tue, 23 Jan 2007 05:34:05 GMT
Author: deepal
Date: Mon Jan 22 21:34:03 2007
New Revision: 498925

URL: http://svn.apache.org/viewvc?view=rev&rev=498925
Log:
-Merge 1.1 xdocs and trunk xdocs
  - Chathra please double check whether I have done any mistake

Added:
    webservices/axis2/trunk/java/xdocs/download/1_1_1/
    webservices/axis2/trunk/java/xdocs/download/1_1_1/download.cgi
    webservices/axis2/trunk/java/xdocs/download/1_1_1/download.html
    webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/rampart-config.xsd
    webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/sample-policy.xml
    webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/sec-conf/sample-services.xml
Modified:
    webservices/axis2/trunk/java/xdocs/1_1/adv-userguide.html
    webservices/axis2/trunk/java/xdocs/1_1/contents.html
    webservices/axis2/trunk/java/xdocs/1_1/installationguide.html
    webservices/axis2/trunk/java/xdocs/1_1/jibx/jibx-codegen-integration.html
    webservices/axis2/trunk/java/xdocs/1_1/modules.html
    webservices/axis2/trunk/java/xdocs/1_1/mtom-guide.html
    webservices/axis2/trunk/java/xdocs/1_1/pojoguide.html
    webservices/axis2/trunk/java/xdocs/1_1/quickstartguide.html
    webservices/axis2/trunk/java/xdocs/1_1/reference.html
    webservices/axis2/trunk/java/xdocs/1_1/tcp-transport.html
    webservices/axis2/trunk/java/xdocs/archived_news.html
    webservices/axis2/trunk/java/xdocs/download.html
    webservices/axis2/trunk/java/xdocs/download/1_1/download.html
    webservices/axis2/trunk/java/xdocs/faq.html
    webservices/axis2/trunk/java/xdocs/index.html
    webservices/axis2/trunk/java/xdocs/modules/index.html
    webservices/axis2/trunk/java/xdocs/modules/previous.html
    webservices/axis2/trunk/java/xdocs/modules/rampart/1_0/security-module.html
    webservices/axis2/trunk/java/xdocs/modules/rampart/1_1/security-module.html
    webservices/axis2/trunk/java/xdocs/modules/wss4j/0_94/0.94/security-module.html
    webservices/axis2/trunk/java/xdocs/modules/wss4j/0_95/security-module.html
    webservices/axis2/trunk/java/xdocs/modules/wss4j/1_0/security-module.html
    webservices/axis2/trunk/java/xdocs/navigation.xml
    webservices/axis2/trunk/java/xdocs/tools/1_1/CodegenToolReference.html
    webservices/axis2/trunk/java/xdocs/tools/index.html
    webservices/axis2/trunk/java/xdocs/tools/previous.html

Modified: webservices/axis2/trunk/java/xdocs/1_1/adv-userguide.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/adv-userguide.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/adv-userguide.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/adv-userguide.html Mon Jan 22 21:34:03 2007
@@ -1,29 +1,32 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html>
 <head>
+  <meta http-equiv="content-type" content="">
   <title>Axis2 Advance User's Guide</title>
-  <link href="../css/axis-docs.css" rel="stylesheet" type="text/css" media="all" />
+  <link href="../css/axis-docs.css" rel="stylesheet" type="text/css"
+  media="all">
 </head>
 
 <body dir="ltr" lang="en-US">
 <a name="_Toc96697849" id="_Toc96697849"></a>
-<h1 align="center"> Apache Axis2 Advance User's Guide</h1>
 
-<p>This guide will help you get started with Axis2, the next generation of
-Apache Axis! It describes in detail how to write Web services and Web
-service clients using Axis2; how to write custom modules and how to use them
-with a Web service. Advanced Topics and Samples which are shipped with the
-binary distribution of Axis2, are also discussed.</p>
+<h1 align="center">Apache Axis2 Advance User's Guide</h1>
 
+<p>This guide will help you get started with Axis2, the next generation of
+Apache Axis! It describes in detail how to write Web services and Web service
+clients using Axis2; how to write custom modules and how to use them with a
+Web service. Advanced Topics and Samples which are shipped with the binary
+distribution of Axis2, are also discussed.</p>
 <a name="Introduction"></a>
+
 <h2>Introduction</h2>
 
 <p>This User's Guide is written based on <a
 href="../download/1_1/download.html/#std-bin">Axis2 Standard Binary
 Distribution</a>. The Standard Binary Distribution can be directly <a
-href="../download/1_1/download.html/#std-bin">downloaded</a> or
-built using the <a href="../download/1_1/download.html#src">Source
-Distribution</a>. If you choose to go for the latter, then <a
+href="../download/1_1/download.html/#std-bin">downloaded</a> or built using
+the <a href="../download/1_1/download.html#src">Source Distribution</a>. If
+you choose to go for the latter, then <a
 href="installationguide.html">Installation Guide</a> will instruct you on how
 to build Axis2 Standard Binary Distribution using the Source.</p>
 
@@ -56,16 +59,18 @@
 gives you step by step instructions on just how to build axis2.war and deploy
 it in your servlet container.</p>
 <a name="ws_codegen"></a><a name="Web_Services_Using_Axis2"></a>
+
 <h2>Creating a New Web Service</h2>
 
 <p>If you are looking for "How to Write a Web Service Client using Axis2?"
 please go to the <a href="#client">next section</a>. Axis2 provides two ways
-to create new Web Services, using <strong>code generation</strong> and using XML based primary
-APIs. The following section explains how to start from a WSDL, and create a new
-Service with code generation. For the XML based primary API please refer to
-the section <a href="xmlbased-server.html">Writing Web Services Using Axis2's
-Primary APIs</a> for more information. However if you are a new user it is
-better to follow the code generation approach first (given below)</p>
+to create new Web Services, using <strong>code generation</strong> and using
+XML based primary APIs. The following section explains how to start from a
+WSDL, and create a new Service with code generation. For the XML based
+primary API please refer to the section <a
+href="xmlbased-server.html">Writing Web Services Using Axis2's Primary
+APIs</a> for more information. However if you are a new user it is better to
+follow the code generation approach first (given below)</p>
 
 <h3>Starting with WSDL, Create and Deploy a Service</h3>
 
@@ -83,8 +88,8 @@
   <li>Create a *.aar archive (Axis Archive) for the Web service</li>
   <li>Deploy the Web service</li>
 </ol>
-
 <a name="Step1_:Generate_skeleton"></a>
+
 <h3>Step1: Generate Skeleton Code</h3>
 
 <p>To generate the skeleton and required classes, you can use the WSDL2Java
@@ -98,44 +103,38 @@
 will be sent to samples directory. Other data binding tools you could use are
 adb (Axis data binding) and jaxme (<a
 href="http://ws.apache.org/jaxme/">JaxMe data binding</a>)</p>
-<pre>
-WSDL2Java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans 
--o ../samples -p org.apache.axis2.userguide
-</pre>
+<pre>wsdl2java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans 
+-o ../samples -p org.apache.axis2.userguide</pre>
 
 <p>This will generate the required classes in the <b>"sample/src"</b>
 directory, and the schema classes in
 <strong>"samples/resources/schemaorg_apache_xmlbeans"</strong>
 directory<strong></strong>. Note that these are not source files and should
 be available in the class path in order to compile the generated classes.</p>
-
 <a name="Step2_Implement_Business_Logic"></a>
-<h3>Step 2: Implement Business
-Logic</h3>
 
-<p>Now you should fill the business logic in the skeleton class. You can
-find the skeleton class -Axis2SampleDocLitServiceSkeleton.java- among the
+<h3>Step 2: Implement Business Logic</h3>
+
+<p>Now you should fill the business logic in the skeleton class. You can find
+the skeleton class -Axis2SampleDocLitServiceSkeleton.java- among the
 generated classes in the
 <strong>"samples/src/org/apache/axis2/userguide</strong> directory. Let's
-fill the <code>echoString(..)</code> method in the skeleton as shown below. Our sample
-WSDL-Axis2SampleDocLit.wsdl in <strong>"samples/wsdl"</strong> directory has
-three operations: echoString, echoStringArray, echoStruct. To see how others
-will look when they are filled up see <a
+fill the <code>echoString(..)</code> method in the skeleton as shown below.
+Our sample WSDL-Axis2SampleDocLit.wsdl in <strong>"samples/wsdl"</strong>
+directory has three operations: echoString, echoStringArray, echoStruct. To
+see how others will look when they are filled up see <a
 href="src/Axis2SampleDocLitServiceCode.html">Code Listing For
 Axis2SampleDocLitService Service</a></p>
-<source>
-<pre>
-public org.apache.axis2.userguide.xsd.EchoStringReturnDocument 
+<source><pre>public org.apache.axis2.userguide.xsd.EchoStringReturnDocument 
     echoString(org.apache.axis2.userguide.xsd.EchoStringParamDocument param4) throws Exception {
     //Use the factory to create the output document.
     org.apache.axis2.userguide.xsd.EchoStringReturnDocument retDoc = 
            org.apache.axis2.userguide.xsd.EchoStringReturnDocument.Factory.newInstance();
     //send the string back.
     retDoc.setEchoStringReturn(param4.getEchoStringParam());
-   return retDoc;<br>
-</pre></source>
+   return retDoc;<br></pre>
+</source><a name="Step4_Create_archive"></a>
 
-<a name="Step4_Create_archive"></a>
 <h3>Step 3: Create Archive File</h3>
 
 <p>An Axis2 service must be bundled as a service archive. The next step is to
@@ -147,11 +146,14 @@
   <li>Compile the generated code</li>
   <li>Copy <strong>"resources/schemaorg_apache_xmlbeans</strong>" xmlbeans
     classes to your class folder</li>
-  <li>Among the generated files, there will be services.xml file, which is the
-    deployment descriptor for Axis2 service.[<a
+  <li>Among the generated files, there will be services.xml file, which is
+    the deployment descriptor for Axis2 service.[<a
     href="reference.html#servicedd">learn more about it</a>]. Copy the
     resources/service.xml to META-INF/services.xml</li>
-  <p>(To write your own service.xml file see sub section in <a href="xmlbased-server.html#Step2_:Write_the_services_xml_file">Writing Web Services Using Axis2's Primary APIs</a> section.)</p>
+
+  <p>(To write your own service.xml file see sub section in <a
+  href="xmlbased-server.html#Step2_:Write_the_services_xml_file">Writing Web
+  Services Using Axis2's Primary APIs</a> section.)</p>
   <li>Create the archive using content of the class folder. Change directory
     to class folder and run <code>jar -cf &lt;service-name&gt;.aar</code> to
     create the archive</li>
@@ -162,16 +164,16 @@
 
 <p><img src="images/userguide/DirectoryStructure.jpg" align="bottom"
 border="0"></p>
-
 <a name="Step5_Deploy_web_service"></a>
+
 <h3>Step 4: Deploy Web Service</h3>
 
 <p>The service can be deployed by simply dropping the ".aar" file into
 "services" directory in "/webapps/axis2/WEB-INF" of your servlet container.
 We recommend using <a href="http://tomcat.apache.org/">Apache Tomcat</a> as
 servlet container. <strong>Please Note that the services directory is
-available only after axis2.war is exploded by Tomcat. However, the easiest way
-to do it is to start Tomcat after axis2.war is copied to the webapps
+available only after axis2.war is exploded by Tomcat. However, the easiest
+way to do it is to start Tomcat after axis2.war is copied to the webapps
 directory</strong> (if you have not already started). Check the link
 "Services" on the <a href="http://localhost:8080/axis2/" target="_blank">Home
 Page of Axis2 Web Application</a> (http://localhost:8080/axis2) and see
@@ -179,21 +181,22 @@
 
 <p>We recommend using the exploded configuration to deploy Axis2 WAR in
 <strong>WebLogic and WebSphere</strong> application servers to support the
-hotupdate/ hotdeployment features in Axis2. See <a href="app_server.html#weblogic_websphere">Application Server Specific
+hotupdate/ hotdeployment features in Axis2. See <a
+href="app_server.html#weblogic_websphere">Application Server Specific
 Configuration Guide</a> for details.</p>
 
 <p>Note: Axis2 provides an easy way to deploy Web Services using the "Upload
 Service" tool on Axis2 Web Application's Administration module. (See the <a
 href="webadminguide.html" target="_blank">Web Administration Guide</a> for
 more information on this)</p>
-
 <a name="client"></a>
+
 <h2>Writing a Web Service Client</h2>
 
-<p>Axis2 also provides a more complex, yet powerful XML based client
-API which is intended for advanced users. Read <a
-href="dii.html">Writing Web Service Clients Using Axis2's Primary APIs</a> to
-learn more about it. However, if you are a new user we recommend using the <strong>code
+<p>Axis2 also provides a more complex, yet powerful XML based client API
+which is intended for advanced users. Read <a href="dii.html">Writing Web
+Service Clients Using Axis2's Primary APIs</a> to learn more about it.
+However, if you are a new user we recommend using the <strong>code
 generation</strong> approach presented below.</p>
 
 <h3>Generate Stubs</h3>
@@ -201,12 +204,9 @@
 <p>Let's see how we could generate java code (Stub) to handle the client side
 Web Service invocation for you. That can be done by running the WSDL2Java
 tool using following arguments</p>
-<source>
-<pre>WSDL2Java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -d xmlbeans 
-     -o ../samples/src -p org.apache.axis2.userguide
-</pre></source>
-
-
+<source><pre>wsdl2java.sh -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -d xmlbeans 
+     -o ../samples/src -p org.apache.axis2.userguide</pre>
+</source>
 <p>This will generate client side stubs and xmlbeans types for your types.
 The Stub class that you need to use will be of the form
 <strong>&lt;service-name&gt;Stub</strong>. For our example it will be called
@@ -228,8 +228,7 @@
 <code>Axis2SampleDocLitService</code> that we have already deployed. The code
 is extremely simple to understand and the explanations are in the form of
 comments.</p>
-<source>
-<pre>     try {
+<source><pre>     try {
                org.apache.axis2.userguide.Axis2SampleDocLitServiceStub stub 
                   = new org.apache.axis2.userguide.Axis2SampleDocLitServiceStub(null,
                     "http://localhost:8080/axis2/services/Axis2SampleDocLitService");
@@ -243,9 +242,8 @@
                 System.out.println(resDoc.getEchoStringReturn());
                } catch (java.rmi.RemoteException e) {
                   e.printStackTrace();
-              }
-</pre></source>
-
+              }</pre>
+</source>
 <p>First argument of <code>Axis2SampleDocLitPortTypeStub</code> should be the
 Axis2 repository for the client. Here we use null to make the stub use
 default configurations. However you could make Axis2 use your own repository
@@ -261,8 +259,7 @@
 <strong>start&lt;method-name&gt;</strong>. These methods accept a callback
 object which would be called when the response is received. Sample code that
 does an asynchronous interaction is given below.</p>
-<source>
-<pre>try {
+<source><pre>try {
          org.apache.axis2.userguide.Axis2SampleDocLitServiceStub stub
            = new org.apache.axis2.userguide.Axis2SampleDocLitServiceStub(null,
              "http://localhost:8080/axis2/services/Axis2SampleDocLitService");
@@ -280,11 +277,8 @@
            stub.startechoString(reqDoc, callback);
         } catch (java.rmi.RemoteException e) {
           e.printStackTrace();
-       }
-</pre>
+       }</pre>
 </source>
-
-
 <p>Even though the above code does a non-blocking invocation at the client
 API, the transport connection may still operate in blocking fashion. For
 example, a single HTTP connection can be used to make the Web Service request
@@ -294,14 +288,9 @@
 the following code segment after creating the stub. These will force Axis2 to
 use two transport connections for the request and the response while the
 client uses a Callback to process the response.</p>
-<source>
-<pre>
-stub._getServiceClient().engageModule(new QName("addressing"));
-stub._getServiceClient().getOptions().setUseSeparateListener(true);
-</pre>
+<source><pre>stub._getServiceClient().engageModule(new QName("addressing"));
+stub._getServiceClient().getOptions().setUseSeparateListener(true);</pre>
 </source>
-
-
 <p>Once those options are set, Axis2 client does the following:</p>
 <ol>
   <li>Start a new Transport Listener(Server) at the client side</li>
@@ -315,28 +304,22 @@
 
 <h3>Using Your Own Repository</h3>
 
-<p>You could use your own repository with Axis2 Client, code below shows
-how to do this.</p>
-<source>
-<pre>
-String axis2Repo = ...
+<p>You could use your own repository with Axis2 Client, code below shows how
+to do this.</p>
+<source><pre>String axis2Repo = ...
 String axis2xml = ...
 ConfigurationContext configContext =
 ConfigurationContextFactory.createConfigurationContextFromFileSystem(axis2Repo, axis2xml);
 Service1Stub stub1 = new Service1Stub(configContext,...);
 //invoke Service1
 Service2Stub stub2 = new Service2Stub(configContext,...);
-//invoke Service2
-</pre>
+//invoke Service2</pre>
 </source>
-
-
-<p>Note by creating the <code>ConfigurationContext</code> outside and
-passing it to the stubs, you could make number of stubs to use same
-repository, thus saving the configuration loading overhead from each
-request.</p>
-
+<p>Note by creating the <code>ConfigurationContext</code> outside and passing
+it to the stubs, you could make number of stubs to use same repository, thus
+saving the configuration loading overhead from each request.</p>
 <a name="config"></a>
+
 <h2>Configuring Axis2</h2>
 
 <h3>Axis2 Repository</h3>
@@ -385,8 +368,8 @@
 becomes available and can be engaged at global, service or operation scopes.
 Once engaged it becomes active (add handlers to the execution flow) at the
 respective scope. Please refer to <a href="Axis2ArchitectureGuide.html">Axis2
-architecture guide</a> for detailed explanation. The following table explains the
-semantics of scope and how to engage modules in those scopes.</p>
+architecture guide</a> for detailed explanation. The following table explains
+the semantics of scope and how to engage modules in those scopes.</p>
 
 <table border="1">
   <tbody>
@@ -438,8 +421,8 @@
 <ol>
   <li>To <strong>enable</strong> addressing at the server side you need to
     copy addressing.mar file to modules directory of server's axis2
-    repository. To engage the module, add a &lt;module ref="addressing"/&gt; to
-    axis2.xml. <strong>Addressing module can be engaged only at global
+    repository. To engage the module, add a &lt;module ref="addressing"/&gt;
+    to axis2.xml. <strong>Addressing module can be engaged only at global
     level</strong></li>
   <li>To <strong>enable</strong> addressing at the client side you should add
     it to the repository and provide the repository as argument to the <a
@@ -451,8 +434,8 @@
     <pre>stub._getServiceClient().engageModule(moduleName)</pre>
   </li>
 </ol>
-
 <a name="advanced"></a>
+
 <h2>Advanced Topics</h2>
 
 <h3>Transports</h3>

Modified: webservices/axis2/trunk/java/xdocs/1_1/contents.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/contents.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/contents.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/contents.html Mon Jan 22 21:34:03 2007
@@ -3,13 +3,13 @@
 <html>
 <head>
   <meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
-  <title>Axis2/Java 1.1 Documentation Home</title>
+  <title>Axis2/Java 1.1.1 Documentation Home</title>
   <link href="../css/axis-docs.css" rel="stylesheet" type="text/css"
   media="all">
 </head>
 
 <body lang="en">
-<h1>Apache Axis2/Java Version 1.1 Documentation Index</h1>
+<h1>Apache Axis2/Java Version 1.1.1 Documentation Index</h1>
 
 <h2>Introduction</h2>
 
@@ -19,10 +19,8 @@
 to support the easy addition of plug-in "modules" that extend its
 functionality for features such as security and reliability.</p>
 
-<p>Apache Axis2 Version 1.1 comes to you with better Axis2 Databinding
-Framework (ADB) support, <a
-href="http://www.w3.org/TR/SOAP-attachments">attachments API</a>, Spring and
-complete support for SOAP with Attachments (SwA).</p>
+<p>Apache Axis2 Version 1.1.1 comes to you with performance improvements and
+bug fixes over the 1.1 release.</p>
 
 <p>This page will take you through the list of documents we have in store for
 you.</p>
@@ -55,7 +53,7 @@
     receiving of SOAP messages and Message Exchange Patterns (MEPs).</li>
   <li><a href="userguide-creatingclients.html">Creating Clients from WSDL</a>
     - When it comes to creating a Web service client, you can do it manually
-    as described in the next document,, but in most cases you have a Web
+    as described in the next document, but in most cases you have a Web
     Service Description Language (WSDL) definition that describes the
     messages clients should send and expect to receive. Axis2 provides
     several ways to use this definition to automatically generate a client.
@@ -63,7 +61,7 @@
   definitions.</li>
   <li><a href="userguide-buildingservices.html">Building Services from
     Scratch</a> - Now that you know how to use Axis2 to generate clients from
-    WSDL as described in the document before,, this document digs a little
+    WSDL as described in the document before, this document digs a little
     deeper, showing you how to create services, and how to create both
     services and clients "from scratch", so to speak.</li>
   <li><a href="userguide-samples.html">Samples</a> - The Axis2 Standard
@@ -79,7 +77,7 @@
         are fast to build and easy to maintain, meaning you'll save a lot of
         time building and debugging your code</li>
       <li><a href="quickstartguide.html">Axis2 Quick Start Guide</a>-The
-        purpose of this guide is to get you started creating services and
+        purpose of this guide is to get you started on creating services and
         clients using Axis2 as quickly as possible. It demonstrates how to
         create Web services using a variety of different technologies.</></li>
     </ul>

Modified: webservices/axis2/trunk/java/xdocs/1_1/installationguide.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/installationguide.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/installationguide.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/installationguide.html Mon Jan 22 21:34:03 2007
@@ -1,400 +1,463 @@
 <html>
-
 <head>
-    <meta http-equiv="content-type" content="">
-    <title>Axis2 Installation Guide</title>
-  <link href="../css/axis-docs.css" rel="stylesheet" type="text/css" media="all" />
+  <meta http-equiv="content-type" content="">
+  <title>Axis2 Installation Guide</title>
+  <link href="../css/axis-docs.css" rel="stylesheet" type="text/css"
+  media="all">
 </head>
 
 <body lang="en">
-
 <h1 align="center">Apache Axis2 Installation Guide</h1>
 
 <p>This document will give you information on Axis2 distribution packages,
-    system prerequisites &amp; setting up environment variables and tools
-    followed by detailed instructions on installation methods.</p>
+system prerequisites &amp; setting up environment variables and tools
+followed by detailed instructions on installation methods.</p>
 
 <p><i>Send your feedback to: <a
-        href="mailto:axis-dev@ws.apache.org">axis-dev@ws.apache.org</a></i>. Prefix
-    subject with [Axis2]. To subscribe to mailing list see <a
-        href="http://ws.apache.org/axis2/mail-lists.html">here.</a></p>
+href="mailto:axis-dev@ws.apache.org">axis-dev@ws.apache.org</a></i>. Prefix
+subject with [Axis2]. To subscribe to mailing list see <a
+href="http://ws.apache.org/axis2/mail-lists.html">here.</a></p>
 
 <h2>Contents</h2>
 <ul>
-    <li><a href="#Download_Axis2">Download Axis2</a></li>
-    <li><a href="#requirements">System Requirements</a></li>
-    <li><a href="#standalone">Installation Using Standard Binary Distribution</a>
-                <ul>
-                    <li><a href="#standalone1">Install the Apache Axis2 Binary Distribution</a></li>
-                    <li><a href="#standalone2">Starting up Axis2 Standalone Server</a></li>
-                    <li><a href="#standalone3">Building WAR File Using Standard Binary Distribution</a></li>
-                    <li><a href="#standalone4">Getting Familiar with the Axis2 Convenient Scripts</a></li>
-                </ul>
-    </li>
-    <li><a href="#build_war"></a></li>
-    <li><a href="#servlet_container">Installing Axis2 in a Servlet
-        Container</a></li>
-    <li><a href="#upload">Uploading Services</a></li>
-    <li><a href="#advanced">Advanced</a>
+  <li><a href="#Download_Axis2">Download Axis2</a></li>
+  <li><a href="#requirements">System Requirements</a></li>
+  <li><a href="#standalone">Installation Using Standard Binary
+    Distribution</a>
+    <ul>
+      <li><a href="#standalone1">Install the Apache Axis2 Binary
+        Distribution</a></li>
+      <li><a href="#standalone2">Starting up Axis2 Standalone Server</a></li>
+      <li><a href="#standalone3">Building WAR File Using Standard Binary
+        Distribution</a></li>
+      <li><a href="#standalone4">Getting Familiar with the Axis2 Convenient
+        Scripts</a></li>
+    </ul>
+  </li>
+  <li><a href="#build_war"></a></li>
+  <li><a href="#servlet_container">Installing Axis2 in a Servlet
+  Container</a></li>
+  <li><a href="#upload">Uploading Services</a></li>
+  <li><a href="#advanced">Advanced</a>
+    <ul>
+      <li><a href="#source">Axis2 Source Distribution</a>
         <ul>
-            <li><a href="#source">Axis2 Source Distribution</a>
-                <ul>
-                    <li><a href="#_Toc96698083">Setting up the Environment and
-                        Tools</a></li>
-                    <li><a href="#_Toc96698085">Building Axis2 Binaries and WAR file
-                        Using the Source Distribution</a></li>
-                </ul>
-            </li>
+          <li><a href="#_Toc96698083">Setting up the Environment and
+          Tools</a></li>
+          <li><a href="#_Toc96698085">Building Axis2 Binaries and WAR file
+            Using the Source Distribution</a></li>
         </ul>
-    </li>
+      </li>
+    </ul>
+  </li>
 </ul>
 <a name="Download_Axis2"></a>
 
 <h2>Download Axis2</h2>
 
 <p>Axis2 is distributed in several convenient distribution packages and can
-    be installed either as a standalone server or as part of a J2EE compliant
-    servlet container. Axis2 is distributed under the Apache License, version
-    2.0. This Installation Guide will mainly focus on running Apache Axis2 using
-    the Standard Binary Distribution.</p>
-
-<p><a href="http://ws.apache.org/axis2/download/1_1/download.cgi">Download</a> distribution packages
-    of the Apache Axis2 1.1 version (latest).<p/>
-<p><a href="http://ws.apache.org/axis2/download.cgi">Download</a> distribution packages of all versions of Apache Axis2.</p>
+be installed either as a standalone server or as part of a J2EE compliant
+servlet container. Axis2 is distributed under the Apache License, version
+2.0. This Installation Guide will mainly focus on running Apache Axis2 using
+the Standard Binary Distribution.</p>
+
+<p><a
+href="http://ws.apache.org/axis2/download/1_1_1/download.cgi">Download</a>
+distribution packages of the Apache Axis2 1.1.1 version (latest).</p>
 
-<p>The Distribution Packages Provided are as follows:</p>
+<p></p>
+
+<p><a href="http://ws.apache.org/axis2/download.cgi">Download</a>
+distribution packages of all versions of Apache Axis2.</p>
 
+<p>The Distribution Packages Provided are as follows:</p>
 <a name="std-bin" id="std-bin"></a>
+
 <h3>1. Standard Binary Distribution</h3>
 
-<p>This is the complete version of Axis2 and include samples and convenient scripts as
-    well. 
-</p>
+<p>This is the complete version of Axis2 and include samples and convenient
+scripts as well.</p>
 
-<p><a href="http://ws.apache.org/axis2/download/1_1/download.cgi">Download</a> Standard
-    Binary Distribution</p>
+<p><a
+href="http://ws.apache.org/axis2/download/1_1_1/download.cgi">Download</a>
+Standard Binary Distribution</p>
 <a name="war1"></a>
 
 <h3>2. WAR (Web Archive) Distribution</h3>
 
 <p>This will be the Web application of Axis2 which can be deployed in most of
-    the servlet containers.</p>
+the servlet containers.</p>
 
-<p><a href="http://ws.apache.org/axis2/download/1_1/download.cgi">Download</a> WAR (Web Archive)
-    Distribution</p>
+<p><a
+href="http://ws.apache.org/axis2/download/1_1_1/download.cgi">Download</a>
+WAR (Web Archive) Distribution</p>
 
 <h3>3. Documents Distribution</h3>
 
 <p>This will contain all the documentation in one package. The package
-    includes the xdocs and the Java API docs of this project.</p>
+includes the xdocs and the Java API docs of this project.</p>
 
-<p><a href="http://ws.apache.org/axis2/download/1_1/download.cgi">Download</a> Documents
-    Distribution</p>
+<p><a
+href="http://ws.apache.org/axis2/download/1_1_1/download.cgi">Download</a>
+Documents Distribution</p>
 
 <h3>4. Source Distribution</h3>
 
 <p>This will contain the sources of Axis2 standard distribution, and is
-    mainly for the benefit of the advance users. One can generate a binary
-    distribution using the source by typing <span class="style1">$maven
-dist-bin. </span> You need to set up the Axis2 environment before
-    running this command. Step by step details on how to create the binary
-    distribution is available in the <a href="#advanced">Advanced</a> section.</p>
-
-<p><a href="http://ws.apache.org/axis2/download/1_1/download.cgi">Download</a> Source
-    Distribution</p>
-
+mainly for the benefit of the advance users. One can generate a binary
+distribution using the source by typing <span class="style1">$maven dist-bin.
+</span> You need to set up the Axis2 environment before running this command.
+Step by step details on how to create the binary distribution is available in
+the <a href="#advanced">Advanced</a> section.</p>
+
+<p><a
+href="http://ws.apache.org/axis2/download/1_1_1/download.cgi">Download</a>
+Source Distribution</p>
 <a name="requirements"></a>
+
 <h2>System Requirements</h2>
 
 <table border="2">
-    <caption></caption>
-    <tbody>
-        <tr>
-            <td>Java Development Kit (JDK)
-            </td>
-            <td>1.4 or later (For instructions on setting up the JDK in different operating systems,
-                visit
-                <a href="http://java.sun.com/">http://java.sun.com</a>)</td>
-        </tr>
-        <tr>
-            <td>Disk</td>
-            <td>Approximately 11 MB separately for standard binary distribution
-            </td>
-        </tr>
-        <tr>
-            <td>Operating system</td>
-            <td>Tested on Windows XP, Linux, Mac OS X, Fedora core, Ubuntu,
-                Gentoo</td>
-        </tr>
-        <tr>
-            <td><strong>Build Tool</strong>-<a href="http://ant.apache.org/">Apache Ant</a>  
-             <p>To run samples and to build war from Axis2 binary distribution.</p></td>
-            <td>Version 1.6.5 or higher(<a
-                    href="http://ant.apache.org/bindownload.cgi">download</a>).</td>
-        </tr>
-        <tr>
-            <td><strong>Build Tool</strong>- <a href="http://maven.apache.org/maven-1.x/">Apache
-                Maven 1.x</a>
-
-                <p>Required <em>only</em> for building Axis2 from Source
-                    Distribution</p>
-            </td>
-            <td>1.0.2 or higher in Maven 1.x series (<a
-                    href="http://maven.apache.org/maven-1.x/start/download.html">download</a>).
-                <strong>Please download maven 1.x version. Axis2 does not support maven 2.</strong></td>
-        </tr>
-    </tbody>
+  <caption></caption>
+  <tbody>
+    <tr>
+      <td>Java Development Kit (JDK)</td>
+      <td>1.4 or later (For instructions on setting up the JDK in different
+        operating systems, visit <a
+        href="http://java.sun.com/">http://java.sun.com</a>)</td>
+    </tr>
+    <tr>
+      <td>Disk</td>
+      <td>Approximately 11 MB separately for standard binary distribution</td>
+    </tr>
+    <tr>
+      <td>Operating system</td>
+      <td>Tested on Windows XP, Linux, Mac OS X, Fedora core, Ubuntu,
+      Gentoo</td>
+    </tr>
+    <tr>
+      <td><strong>Build Tool</strong>-<a href="http://ant.apache.org/">Apache
+        Ant</a>
+
+        <p>To run samples and to build war from Axis2 binary distribution.</p>
+      </td>
+      <td>Version 1.6.5 or higher (<a
+        href="http://ant.apache.org/bindownload.cgi">download</a>).</td>
+    </tr>
+    <tr>
+      <td><strong>Build Tool</strong>- <a
+        href="http://maven.apache.org/maven-1.x/">Apache Maven 1.x</a>
+
+        <p>Required <em>only</em> for building Axis2 from Source
+        Distribution</p>
+      </td>
+      <td>1.0.2 or higher in Maven 1.x series (<a
+        href="http://maven.apache.org/maven-1.x/start/download.html">download</a>).
+        <strong>Please download maven 1.x version. Axis2 does not support
+        maven 2.</strong></td>
+    </tr>
+  </tbody>
 </table>
-
 <a name="standalone"></a>
+
 <h2>Installation Using Standard Binary Distribution</h2>
 <a name="standalone1"></a>
+
 <h3>1. Download and Install the Apache Axis2 Binary Distribution</h3>
-<p> Download and install a Java Development Kit (JDK) release (version 1.4 or later) from <a href="http://java.sun.com/j2se/"
-> here .</a> Install the JDK according to the instructions included with the release.Set an environment 
-variable JAVA_HOME to the pathname of the directory into which you installed the JDK release.</p>
+
+<p>Download and install a Java Development Kit (JDK) release (version 1.4 or
+later) from <a href="http://java.sun.com/j2se/"> here .</a> Install the JDK
+according to the instructions included with the release.Set an environment
+variable JAVA_HOME to the pathname of the directory into which you installed
+the JDK release.</p>
 
 <p>Download and unpack the <a
-        href="http://ws.apache.org/axis2/download/1_1/download.cgi">Axis2 Standard Binary Distribution</a>
-        into a convenient location so that the distribution resides in its own directory. Set an 
-        environment variables AXIS2_HOME to the pathname of the extracted directory of Axis2 (Eg: /opt/axis2-1.1).
-</p>
+href="http://ws.apache.org/axis2/download/1_1_1/download.cgi">Axis2 Standard
+Binary Distribution</a> into a convenient location so that the distribution
+resides in its own directory. Set an environment variables AXIS2_HOME to the
+pathname of the extracted directory of Axis2 (Eg: /opt/axis2-1.1.1).</p>
 <a name="standalone2"></a>
+
 <h3>2. Starting up Axis2 Standalone Server</h3>
 
-<p> Standalone Axis2 server can be started by executing the following commands: <br/>
-      $AXIS2_HOME\bin\axis2server.bat (Windows) <br/>
-      $AXIS2_HOME/bin/axis2server.sh  (Unix)
- <p>After startup, the default web services included with Axis2 will be
-available by visiting http://localhost:8080/axis2/services/</p>
+<p>Standalone Axis2 server can be started by executing the following
+commands: <br>
+$AXIS2_HOME\bin\axis2server.bat (Windows) <br>
+$AXIS2_HOME/bin/axis2server.sh  (Unix)</p>
 
+<p>After startup, the default web services included with Axis2 will be
+available by visiting http://localhost:8080/axis2/services/</p>
 <a name="standalone3"></a>
-<h3>3. Building the Axis2 Web Application (axis2.war) Using Standard Binary Distribution</h3>
-<p> Download and install Apache Ant (version 1.6.5 or later) from <a href="http://ant.apache.org/bindownload.cgi"
-> here .</a> Install the Apache Ant according to the instructions included with the Ant release.</p>
-
-<p>Locate the ant build file (build.xml) inside the webapp directory which resides in your Axis2 home
- directory (i.e:- $AXIS_HOME/webapp)". Run the Ant build by executing "ant create.war" inside the $AXIS2_HOME/webapps folder. 
-You can find the generated axis2.war inside the $AXIS2_HOME/dist directory. All the services and modules that are present in the
-AXIS2_HOME/repository will be packed in to the created axis2.war together with the Axis2 configuration found
-at $AXIS2_HOME/conf/axis2.xml.</p>
-<p> You can read the <a href="#servlet_container">installing Axis2 in a servlet container</a> to figure 
-out how to deploy the Axis2 web application in a servlet container. </p>
 
+<h3>3. Building the Axis2 Web Application (axis2.war) Using Standard Binary
+Distribution</h3>
+
+<p>Download and install Apache Ant (version 1.6.5 or later) from <a
+href="http://ant.apache.org/bindownload.cgi"> here .</a> Install the Apache
+Ant according to the instructions included with the Ant release.</p>
+
+<p>Locate the ant build file (build.xml) inside the webapp directory which
+resides in your Axis2 home directory (i.e:- $AXIS_HOME/webapp)". Run the Ant
+build by executing "ant create.war" inside the $AXIS2_HOME/webapps folder.
+You can find the generated axis2.war inside the $AXIS2_HOME/dist directory.
+All the services and modules that are present in the AXIS2_HOME/repository
+will be packed in to the created axis2.war together with the Axis2
+configuration found at $AXIS2_HOME/conf/axis2.xml.</p>
+
+<p>You can read the <a href="#servlet_container">installing Axis2 in a
+servlet container</a> to figure out how to deploy the Axis2 web application
+in a servlet container.</p>
 <a name="standalone4"></a>
+
 <h3>4. Getting Familiar with the Axis2 Convenient Scripts</h3>
-<p>It is advised to add the $AXIS2_HOME/bin to the PATH, so that you'll be able to run the following scripts from any where.</p>
+
+<p>It is advised to add the $AXIS2_HOME/bin to the PATH, so that you'll be
+able to run the following scripts from any where.</p>
 
 <table border="1">
-<tr>
-	<td><b>Script Name</b></td>
-	<td><b>Description</b></td>
-</tr>
-<tr>
-	<td>axis2.{bat|sh}</td>
-	<td>You can use this script to run web service clients written using Axis2.
-	This script calls the "java" command after adding the classpath for Axis2 dependent libraries (*.jar files present in your AXIS2_HOME/lib), 
-	setting the Axis2 repository location (AXIS2_HOME/repository) and setting the Axis2 configuration file location(AXIS2_HOME/conf/axis2.xml) for you. With this you can be relieved from setting all the above Axis2 specific parameters.<br/>
-	
-	<p><em>Usage : axis2.{sh.bat}  [-options] class [args...]</em></p>	    
-</td>
-</tr>
-<tr>
-	<td>axis2server.{sh|bat}</td>
-	<td>This script will start an standalone Axis2 server using the AXIS2_HOME/repository as the
-	 Axis2 repository and the AXIS2_HOME/conf/axis2.xml as the Axis2 configuration file.  This will start all the transport listeners listed in the AXIS2_HOME/conf/axis2.xml.
-	<p>As an example, if you want to deploy a service using standalone Axis2 server,then copy your 
-	service archive to the AXIS2_HOME/repository/services directory. After that go to the "Transport Ins" section of the AXIS2_HOME/conf/axis2.xml and configure the transport receivers (simpleHttpServer in port 8080 is listed by default). Then invoke this script.</p> </td>
-</tr>
-<tr>
-	<td>wsdl2java.{bat|sh}</td>
-	<td>This script generates java code according to a given WSDL file to handle Web service invocations 
-	(Client side Stubs). This script also has the ability to generate service skeletons according to the given WSDL.<br/>
-	<p><em>Usage:  WSDL2Java.{sh|bat} [OPTION]... -uri &lt;Location of WSDL> </em></p>
-	<p>Eg:  WSDL2Java.sh -uri ../wsdl/Axis2Sample.wsdl </p>
-	<p>A more detailed reference about this script can be found <a href="reference.html">here</a></p></td>	
-</tr>
-<tr>
-	<td>java2wsdl.{bat|sh} </td>
-	<td>This script generates the appropriate WSDL file for a given java class.<br/>
-	<em><p>Usage:  Java2WSDL.{sh|bat} [OPTION]... -cn &lt;fully qualified class name> </em></p>
-	<p>Eg:  Java2WSDL.sh -cn ../samples/test/searchTool.Search</p>
-	<p>A more detailed reference about this script can be found <a href="reference.html">here</a></p>
-	</td>
-</tr>
+  <tbody>
+    <tr>
+      <td><b>Script Name</b></td>
+      <td><b>Description</b></td>
+    </tr>
+    <tr>
+      <td>axis2.{bat|sh}</td>
+      <td>You can use this script to run web service clients written using
+        Axis2. This script calls the "java" command after adding the
+        classpath for Axis2 dependent libraries (*.jar files present in your
+        AXIS2_HOME/lib), setting the Axis2 repository location
+        (AXIS2_HOME/repository) and setting the Axis2 configuration file
+        location(AXIS2_HOME/conf/axis2.xml) for you. With this you can be
+        relieved from setting all the above Axis2 specific parameters.<br>
+
+
+        <p><em>Usage : axis2.{sh.bat}  [-options] class [args...]</em></p>
+      </td>
+    </tr>
+    <tr>
+      <td>axis2server.{sh|bat}</td>
+      <td>This script will start an standalone Axis2 server using the
+        AXIS2_HOME/repository as the Axis2 repository and the
+        AXIS2_HOME/conf/axis2.xml as the Axis2 configuration file.  This will
+        start all the transport listeners listed in the
+        AXIS2_HOME/conf/axis2.xml.
+
+        <p>As an example, if you want to deploy a service using standalone
+        Axis2 server,then copy your service archive to the
+        AXIS2_HOME/repository/services directory. After that go to the
+        "Transport Ins" section of the AXIS2_HOME/conf/axis2.xml and
+        configure the transport receivers (simpleHttpServer in port 8080 is
+        listed by default). Then invoke this script.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>wsdl2java.{bat|sh}</td>
+      <td>This script generates java code according to a given WSDL file to
+        handle Web service invocations (Client side Stubs). This script also
+        has the ability to generate service skeletons according to the given
+        WSDL.<br>
+
+
+        <p><em>Usage:  wsdl2java.{sh|bat} [OPTION]... -uri &lt;Location of
+        WSDL&gt;</em></p>
+
+        <p>Eg:  wsdl2java.sh -uri ../wsdl/Axis2Sample.wsdl</p>
+
+        <p>A more detailed reference about this script can be found <a
+        href="reference.html">here</a></p>
+      </td>
+    </tr>
+    <tr>
+      <td>java2wsdl.{bat|sh}</td>
+      <td>This script generates the appropriate WSDL file for a given java
+        class.<br>
+
+        <p><em>Usage:  Java2WSDL.{sh|bat} [OPTION]... -cn &lt;fully qualified
+        class name&gt;</em></p>
+
+
+        <p>Eg:  Java2WSDL.sh -cn ../samples/test/searchTool.Search</p>
+
+        <p>A more detailed reference about this script can be found <a
+        href="reference.html">here</a></p>
+      </td>
+    </tr>
+  </tbody>
 </table>
-
-
 <a name="servlet_container"></a>
+
 <h2>Installing Axis2 in a Servlet Container</h2>
+
 <p>Which ever the distribution, installing Axis2 in a J2EE compliant servlet
-    container is as follows:</p>
+container is as follows:</p>
 <ol>
-    <li>Build the Axis2 WAR
-        file using the Axis2 Standard Binary Distribution. (Alternatively you can
-         <a href="http://ws.apache.org/axis2/download/1_1/download.cgi">download</a> the axis2.war
-        or you can build axis2.war using the <a href="#war">Source
-        Distribution</a>.</li>
-    <li>Drop the war in the webapps folder of the servlet container. Most
-        servlet containers will automatically install war. (some servlet
-        containers may require a restart in order to capture the new web
-        application. Refer your servlet container documentation for more
-        information about this.)</li>
-    <li>Once the WAR is successfully installed, test it by pointing the web
-        browser to the <strong>http://&lt;host :port&gt;/axis2. </strong>It
-        should produce the following page which is the <strong>Axis2 Web
-        Application Home Page</strong>.</li>
-
-    <p align="center"><strong><img src="images/clip_image006.jpg"
-                                   alt=""></strong></p>
-    <li>Use the link "Validate" to ensure that everything is fine and smooth.
-        If the validation fails then the war has failed to install properly or
-        some essential jars are missing. At such a situation the documentation of
-        the particular servlet container should be consulted to find the problem.
-        The following page is a successful validation. Note the statement core
-        Axis2 libraries are present.</li>
+  <li>Build the Axis2 WAR file using the Axis2 Standard Binary Distribution.
+    (Alternatively you can <a
+    href="http://ws.apache.org/axis2/download/1_1_1/download.cgi">download</a>
+    the axis2.war or you can build axis2.war using the <a href="#war">Source
+    Distribution</a>.</li>
+  <li>Drop the war in the webapps folder of the servlet container. Most
+    servlet containers will automatically install war. (some servlet
+    containers may require a restart in order to capture the new web
+    application. Refer your servlet container documentation for more
+    information about this.)</li>
+  <li>Once the WAR is successfully installed, test it by pointing the web
+    browser to the <strong>http://&lt;host :port&gt;/axis2. </strong>It
+    should produce the following page which is the <strong>Axis2 Web
+    Application Home Page</strong>.</li>
+
+  <p align="center"><strong><img src="images/clip_image006.jpg"
+  alt=""></strong></p>
+  <li>Use the link "Validate" to ensure that everything is fine and smooth.
+    If the validation fails then the war has failed to install properly or
+    some essential jars are missing. At such a situation the documentation of
+    the particular servlet container should be consulted to find the problem.
+    The following page is a successful validation. Note the statement core
+    Axis2 libraries are present.</li>
 </ol>
 
 <p align="center"><img src="images/happyaxis.jpg"></p>
 <a name="upload"></a>
 
 <p><strong>Note:</strong> For any Application server specific installation
-    information please refer <a href="app_server.html">Application Server
-    Specific Configuration Guide</a>.</p>
+information please refer <a href="app_server.html">Application Server
+Specific Configuration Guide</a>.</p>
 
 <h2>Uploading Services</h2>
 <ol>
-    <p>The Axis2 Web application also provides an interface to upload services.
-        Once a service is created according to the service specification as
-        described in <a name="adv-userguide.html" target="_blank">Advance User's Guide</a> that jar
-        file can be uploaded using the upload page.</p>
+  <p>The Axis2 Web application also provides an interface to upload services.
+  Once a service is created according to the service specification as
+  described in <a name="adv-userguide.html" target="_blank">Advance User's
+  Guide</a> that jar file can be uploaded using the upload page.</p>
+
+  <p align="center"><strong><img src="images/clip_image010.jpg"
+  alt=""></strong></p>
 
-    <p align="center"><strong><img src="images/clip_image010.jpg"
-                                   alt=""></strong></p>
+  <p>The uploaded jar files will be stored in the default service directory.
+  For Axis2 this will be the &lt;webapps&gt;/axis2/WEB-INF/services
+  directory. Once a service is uploaded it will be installed instantly.</p>
+  <a name="hot_deployment"></a>
 
-    <p>The uploaded jar files will be stored in the default service directory.
-        For Axis2 this will be the &lt;webapps&gt;/axis2/WEB-INF/services
-        directory. Once a service is uploaded it will be installed instantly.</p>
-    <a name="hot_deployment"></a>
-    <p>Since Axis2 supports <strong>hot deployment</strong> one can drop the
-        service jar directly through the file system to the above mentioned
-        services directory. It will also cause the service to be automatically
-        installed without the container being restarted.</p>
+  <p>Since Axis2 supports <strong>hot deployment</strong> one can drop the
+  service jar directly through the file system to the above mentioned
+  services directory. It will also cause the service to be automatically
+  installed without the container being restarted.</p>
 
-    <p>Use the 'Services' link on the Web Application home page to check the
-        successful installation of a service. The services and the operations of
-        successfully installed services will be displayed in the available services
-        page.</p>
+  <p>Use the 'Services' link on the Web Application home page to check the
+  successful installation of a service. The services and the operations of
+  successfully installed services will be displayed in the available services
+  page.</p>
 
-    <p align="center"><img src="images/clip_image012.jpg" alt=""></p>
+  <p align="center"><img src="images/clip_image012.jpg" alt=""></p>
 
-    <p></p>
+  <p></p>
 
-    <p>If the service has deployment time errors it will list those services as
-        faulty services. If you click on the link you can see the deployment fault
-        error message(s).</p>
+  <p>If the service has deployment time errors it will list those services as
+  faulty services. If you click on the link you can see the deployment fault
+  error message(s).</p>
 
-    <p align="center"><img src="images/faultservice.jpg" alt=""></p>
+  <p align="center"><img src="images/faultservice.jpg" alt=""></p>
 
-    <p>Deployment time error message</p>
+  <p>Deployment time error message</p>
 
-    <p align="center"><strong><img src="images/faultmsg.jpg"
-                                   alt=""></strong></p>
+  <p align="center"><strong><img src="images/faultmsg.jpg"
+  alt=""></strong></p>
 
-    <p></p>
+  <p></p>
 
-    <p>Axis2 Administration is all about configuring Axis2 at the run time and
-        the configuration will be transient. More descriptions are available in <a
-            href="webadminguide.html" target="_blank">Axis2 Web Administration
-        Guide</a></p>
+  <p>Axis2 Administration is all about configuring Axis2 at the run time and
+  the configuration will be transient. More descriptions are available in <a
+  href="webadminguide.html" target="_blank">Axis2 Web Administration
+  Guide</a></p>
 </ol>
 <a name="advanced"></a>
+
 <h2>Advanced</h2>
 <a name="source"></a>
+
 <h2>Axis2 Source Distribution</h2>
-<a name="_Toc96698083"></a>
-Using the Source Distribution both binary files (which is downloadable as the </a><a href="#std-bin">Standard Binary
-Distribution</a>) and axis2.war file (which is downloadable as the <a href="#war1">WAR distribution</a>) can be built using maven commands.
+<a name="_Toc96698083"></a> Using the Source Distribution both binary files
+(which is downloadable as the <a href="#std-bin">Standard Binary
+Distribution</a>) and axis2.war file (which is downloadable as the <a
+href="#war1">WAR distribution</a>) can be built using maven commands.
 
 <p>Required jar files do not come with the distribution and they will also
-    have to be built by running the maven command. Before we go any further it is
-    necessary to install <a href="http://maven.apache.org/maven-1.x/"
-                            target="_blank">Maven</aandsettheEnvironment.Thenextsectionwillguideyouhowtodojustthat.>
-</a></p>
+have to be built by running the maven command. Before we go any further it is
+necessary to install <a href="http://maven.apache.org/maven-1.x/"
+target="_blank">Maven</aandsettheEnvironment.Thenextsectionwillguideyouhowtodojustthat.></a></p>
 <a name="env-src"></a>
+
 <h3>Setting Up the Environment and Tools</h3>
 <a name="maven"></a>
 
 <h4>Maven</h4>
 
 <p>The Axis2 build is based on <a href="http://maven.apache.org/maven-1.x/"
-                                  target="_blank">Maven </a>. Hence the only prerequisite to build
-    Axis2 from
-    source distribution is to have Maven installed. Extensive instruction guides
-    are available at the Maven site. This guide however contains the easiest path
-    for quick environment setting. Advanced users who wish to know more about
-    Maven can visit <a href="http://maven.apache.org/maven-1.x/start/index.html"
-                       target="_blank">here </a>.</p>
+target="_blank">Maven </a>. Hence the only prerequisite to build Axis2 from
+source distribution is to have Maven installed. Extensive instruction guides
+are available at the Maven site. This guide however contains the easiest path
+for quick environment setting. Advanced users who wish to know more about
+Maven can visit <a href="http://maven.apache.org/maven-1.x/start/index.html"
+target="_blank">here </a>.</p>
 <ul>
-    <li>MS Windows</li>
+  <li>MS Windows</li>
 </ul>
 <ol>
-    <li>Download and run the Windows installer package for Maven.</li>
-    <li>Set the 'Environment Variables' ( create system variable MAVEN_HOME and
-        edit path. eg: "C:\Program Files\Apache Software Foundation\maven-1.0.2";
-        path %MAVEN_HOME%\bin)</li>
-    <li>Make sure that system variable JAVA_HOME is set to the location of your
-        JDK, eg. C:\Program Files\Java\jdk1.5.0_02</li>
-    <li>Run maven --version to verify that it is correctly installed.</li>
+  <li>Download and run the Windows installer package for Maven.</li>
+  <li>Set the 'Environment Variables' ( create system variable MAVEN_HOME and
+    edit path. eg: "C:\Program Files\Apache Software Foundation\maven-1.0.2";
+    path %MAVEN_HOME%\bin)</li>
+  <li>Make sure that system variable JAVA_HOME is set to the location of your
+    JDK, eg. C:\Program Files\Java\jdk1.5.0_02</li>
+  <li>Run maven --version to verify that it is correctly installed.</li>
 </ol>
 
 <p align="center"><img alt="clip_image002 (15K)"
-                       src="images/clip_image002.jpg" height="211" width="477"></p>
+src="images/clip_image002.jpg" height="211" width="477"></p>
 <ul>
-    <li>Unix based OS (Linux etc)</li>
+  <li>Unix based OS (Linux etc)</li>
 </ul>
 
 <p>The tar ball or the zip archive is the best option. Once the archive is
-    downloaded expand it to a directory of choice and set the environment
-    variable MAVEN_HOME and add MAVEN_HOME/bin to the path as well. More
-    instructions for installing Maven in Unix based operating systems can be
-    found <a href="http://maven.apache.org/download.html#Installation"
-             target="_blank">here </a>.</p>
+downloaded expand it to a directory of choice and set the environment
+variable MAVEN_HOME and add MAVEN_HOME/bin to the path as well. More
+instructions for installing Maven in Unix based operating systems can be
+found <a href="http://maven.apache.org/download.html#Installation"
+target="_blank">here </a>.</p>
 
 <p>Once maven is properly installed you can start building Axis2.</p>
 
 <p><a href="../faq.html#d4">Maven commands that are frequently used</a> in
-    Axis2 are listed on the <a href="../faq.html">FAQs</a> page.</p>
+Axis2 are listed on the <a href="../faq.html">FAQs</a> page.</p>
 <a name="_Toc96698085"></a>
 
 <h3>Building Binaries and WAR File Using the Source Distribution</h3>
 
 <p>The Source Distribution is available as a zipped archive. All the
-    necessary build scripts are included with the source distribution. Once the
-    source archive is expanded into a directory of choice, moving to the
-    particular directory and running <code>maven</code> command will build the
-    Axis2 jar file.</p>
+necessary build scripts are included with the source distribution. Once the
+source archive is expanded into a directory of choice, moving to the
+particular directory and running <code>maven</code> command will build the
+Axis2 jar file.</p>
 
 <p align="center"><img alt="clip_image004 (43K)" src="images/maven.jpg"><br
-        clear="all">
+clear="all">
 </p>
 
 <p>Once the command completes, the binaries (jar files in this case) can be
-    found at a newly created "target" directory.</p>
+found at a newly created "target" directory.</p>
 
 <p><strong>Note: For the first Maven build (if the maven repository is not
-    built first) it will take a while since required jars need to be downloaded.
-    However this is a once only process and will not affect any successive
-    builds.</strong></p>
+built first) it will take a while since required jars need to be downloaded.
+However this is a once only process and will not affect any successive
+builds.</strong></p>
 <a name="war"></a>
 
 <p><strong></strong>The default maven build will however build only the Axis2
-    jar file. To obtain a <strong>WAR (Web Archive)</strong>, <code>maven
-    war</code> command should be issued. This will create a complete WAR with the
-    name axis2.war inside the target directory.</p>
+jar file. To obtain a <strong>WAR (Web Archive)</strong>, <code>maven
+war</code> command should be issued. This will create a complete WAR with the
+name axis2.war inside the target directory.</p>
 
 <p>Once this build step is complete, the binaries are ready to be
-    deployed.</p>
-<a name="_Toc96698086"></a>
-</body>
+deployed.</p>
+<a name="_Toc96698086"></a></body>
 </html>

Modified: webservices/axis2/trunk/java/xdocs/1_1/jibx/jibx-codegen-integration.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/jibx/jibx-codegen-integration.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/jibx/jibx-codegen-integration.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/jibx/jibx-codegen-integration.html Mon Jan 22 21:34:03 2007
@@ -20,6 +20,11 @@
 particular, you need to come up with a set of data classes and a binding
 definition in order to work with JiBX in Axis2.</p>
 
+<p>JiBX support for Axis2 and Web services in general is continuing to evolve.
+This page covers the basics of using JiBX with Axis2 as of the current release.
+Check the <a href="http://www.sosnoski.com/jibx-wiki/space/axis2-jibx">JiBX
+Axis2 Wiki page</a> for updated information about using JiBX with Axis2.</p>
+
 <h2>Content</h2>
 <ul>
   <li><a href="#intro">Introduction</a></li>
@@ -160,7 +165,7 @@
 <p>To run the WSDL2Java tool for JiBX data binding you need:</p>
 <ol>
   <li>To specify <i>-d jibx</i> to select JiBX binding.</li>
-  <li>You also need an additional parameter, <i>-Ebindingfile {file}</i>
+  <li>You also generally need an additional parameter, <i>-Ebindingfile {file}</i>
     (where <i>{file}</i> is the file path to your JiBX binding definition).</li>
   <li>Finally, you need to have the <i>axis2-jibx-XXXX.jar</i>, the
     <i>jibx-bind-XXXX.jar</i>, and the <i>jibx-run-XXXX.jar</i> files
@@ -174,11 +179,14 @@
 attribute that matches the schema <i>complexType</i> used in the WSDL. You can
 also use formats in the binding definition to define the handling of schema
 <i>simpleType</i>s. Schema types corresponding to Java primitives and simple
-objects with build-in JiBX conversions are handled automatically.</p>
-
-<p>If you're not unwrapping the interface, your JiBX binding definition must
-include a concrete mapping for each element used as input or output by any
-operation.</p>
+objects with built-in JiBX conversions are handled automatically, and if all the
+parameter and return values in your wrapped WSDL are of these types you don't
+even need a JiBX binding definition. This is the one case where the
+<i>-Ebindingfile {file}</i> parameter is not needed.</p>
+
+<p>If you're not unwrapping the interface, you must use a JiBX binding
+definition and it must include a concrete mapping for each element used as input
+or output by any operation.</p>
 
 <a name="coming"></a>
 <h2>Coming Attractions</h2>
@@ -187,8 +195,9 @@
 corresponding JiBX binding definitions from an input schema, and also for
 generating binding+schema generation from existing code. These features will be
 integrated into the Axis2 JiBX support when they are available. Check the <a
-href="http://www.jibx.org">JiBX project site</a> for updates on both JiBX
-and the Axis2 JiBX support.</p>
+href="http://www.jibx.org">JiBX project site</a> for updates on JiBX, and the
+<a href="http://www.sosnoski.com/jibx-wiki/space/axis2-jibx">JiBX
+Axis2 Wiki page</a> for updated information about using JiBX with Axis2.</p>
 
 <h2>References</h2>
 

Modified: webservices/axis2/trunk/java/xdocs/1_1/modules.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/modules.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/modules.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/modules.html Mon Jan 22 21:34:03 2007
@@ -206,7 +206,7 @@
 outFlow, etc.). Following xml lines show the respective changes made to the
 "axis2.xml" in order to deploy this logging module in the Axis2 engine. This
 is an extract of the phase section of "axis2.xml".</p>
-<pre>&lt;!-- ================================================= --&gt;
+<p><pre>&lt;!-- ================================================= --&gt;
 &lt;!-- Phases --&gt;
 &lt;!-- ================================================= --&gt;
 
@@ -242,7 +242,7 @@
         &lt;!--  System pre defined phases       --&gt;
         &lt;!--   After Postdispatch phase module author or service author can add any phase he wants      --&gt;
         &lt;phase name="OperationInPhase"/&gt;
-        &lt;phase name="<span style="color: rgb(36, 193, 19);">loggingPhase</span>"/&gt;
+		&lt;phase name="<span style="color: rgb(36, 193, 19);">loggingPhase</span>"/&gt;
     &lt;/phaseOrder&gt;
     &lt;phaseOrder type="outflow"&gt;
         &lt;!--      user can add his own phases to this area  --&gt;
@@ -265,7 +265,7 @@
         &lt;phase name="PolicyDetermination"/&gt;
         &lt;phase name="MessageOut"/&gt;
     &lt;/phaseOrder&gt;
-    </pre>
+    </pre></p>
 
 <p>The text in green, the custom phase "loggingPhase" is placed in all the
 flows, hence that phase will be called in all the message flows in the
@@ -289,7 +289,7 @@
 "<strong>Axis2_HOME/samples/userguide/src/userguide/example2</strong>"
 directory. The simple changes that we have done to "services.xml' are shown
 in green in the following lines of xml.</p>
-<pre>&lt;service name="<span style="color: rgb(36, 193, 19);">MyServiceWithModule</span>"&gt;
+<p><pre>&lt;service name="<span style="color: rgb(36, 193, 19);">MyServiceWithModule</span>"&gt;
     &lt;description&gt;
     This is a sample Web service with a logging module engaged.
     &lt;/description&gt;
@@ -301,7 +301,7 @@
     &lt;operation name="ping"&gt;
     &lt;messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/&gt;
     &lt;/operation&gt;
-&lt;/service&gt;</pre>
+&lt;/service&gt;</pre></p>
 
 <p>In this example we have changed the service name (the implementation class
 is very similar to what we have used earlier although it is in a different
@@ -334,11 +334,8 @@
 
 <p>Deploy this service using the same steps used in <a href="adv-userguide.html#Step5_Deploy_web_service">'Step 4: Deploy Web Service'</a> sub section in '<a href="userguide.html#ws_codegen">Writing a New Service using Codegeneration</a>', and copy the
 "logging.mar" file to the "modules" directory.</p>
+<p>Then run 'ant run.client.servicewithmodule' from <strong>axis2home/samples/userguide directory</strong></p>
 
-<p>Then run using the "TestWebServiceWithModuleClient.bat" or
-"TestWebServiceWithModuleClient.sh" in the
-"<strong>Axis2Home/samples/userguide/src/userguide/clients/bin</strong>"
-directory.</p>
 
 <p>Note: To see logs, the user needs to modify the "log4j.properties" to log
 INFO. The property file is located in

Modified: webservices/axis2/trunk/java/xdocs/1_1/mtom-guide.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/mtom-guide.html?view=diff&rev=498925&r1=498924&r2=498925
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/mtom-guide.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/mtom-guide.html Mon Jan 22 21:34:03 2007
@@ -33,7 +33,7 @@
       <li><a href="#25">MTOM Databinding</a>
         <ul>
           <li><a href="#251">Using ADB</a></li>
-          <li><a href="#252">Using XMLBeans</a></li>
+          <!--li><a href="#252">Using XMLBeans</a></li-->
         </ul>
       </li>
     </ul>
@@ -511,291 +511,6 @@
 <p>The last step is to create an AAR with our Skeleton and the services.xml, and then deploy the service. You can find the completed sample in the Axis2 standard binary distribution under the samples/mtom directory</p>
 
 <a name="252"></a>
-<h3>MTOM Databinding Using XMLBeans</h3>
-
-
-<p>Lets define a full, validated doc / lit style WSDL that imports the xmime
-schema, has a service that receives a jpeg and returns a pass / fail status
-to the client:</p>
-<source><pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-
-&lt;definitions name="MyMTOMService" targetNamespace="http://myMtomNS" xmlns:tns="http://myMtomNS" xmlns="http://schemas.xmlsoap.org/wsdl/" 
-  xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:ns2="http://myMtomNS/types"&gt;
-  &lt;types&gt;
-    &lt;schema targetNamespace="http://myMtomNS/types" elementFormDefault="qualified" xmlns:tns="http://myMtomNS/types" 
-    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema" 
-    xmlns:xmime="http://www.w3.org/2005/05/xmlmime"&gt;
-      &lt;import namespace="http://schemas.xmlsoap.org/soap/encoding/"/&gt;
-
-       &lt;import namespace="http://www.w3.org/2005/05/xmlmime"
-                schemaLocation="http://www.w3.org/2005/05/xmlmime"/&gt;
-      &lt;complexType name="ReturnWebBase"&gt;
-        &lt;sequence&gt;
-          &lt;element name="errorMessage" type="xsd:string"/&gt;
-          &lt;element name="successErrorCode" type="xsd:int"/&gt;
-        &lt;/sequence&gt;
-
-      &lt;/complexType&gt;
-      &lt;element name="MyBinaryData" xmime:expectedContentTypes='image/jpeg' &gt;
-        &lt;complexType&gt;
-          &lt;simpleContent&gt;
-            &lt;extension base="base64Binary" &gt;
-              &lt;attribute ref="xmime:contentType" use="required"/&gt;
-
-            &lt;/extension&gt;
-          &lt;/simpleContent&gt;
-        &lt;/complexType&gt;
-      &lt;/element&gt;
-      &lt;element name="sendData"&gt;
-        &lt;complexType&gt;
-
-          &lt;sequence&gt;
-            &lt;element ref='tns:MyBinaryData' minOccurs="1" maxOccurs="1" /&gt;
-          &lt;/sequence&gt;
-        &lt;/complexType&gt;
-      &lt;/element&gt;
-      &lt;element name="sendDataResponse"&gt;
-
-        &lt;complexType&gt;
-          &lt;sequence&gt;
-            &lt;element minOccurs="1" maxOccurs="1" name="sendDataResult" type="tns:ReturnWebBase" /&gt;
-          &lt;/sequence&gt;
-        &lt;/complexType&gt;
-      &lt;/element&gt;
-
-    &lt;/schema&gt;
-  &lt;/types&gt;
-  &lt;message name="MyMTOMEndpoint_sendData"&gt;
-     &lt;part name="parameters" element="ns2:sendData"/&gt;
-  &lt;/message&gt;
-  &lt;message name="MyMTOMEndpoint_sendDataResponse"&gt;
-
-    &lt;part name="result" element="ns2:sendDataResponse"/&gt;
-  &lt;/message&gt;
-  &lt;portType name="MyMTOMEndpoint"&gt;
-    &lt;operation name="sendData"&gt;
-      &lt;input message="tns:MyMTOMEndpoint_sendData" name="MyMTOMEndpoint_sendData"/&gt;
-      &lt;output message="tns:MyMTOMEndpoint_sendDataResponse" name="MyMTOMEndpoint_sendDataResponse"/&gt;
-
-    &lt;/operation&gt;
-  &lt;/portType&gt;
-  &lt;binding name="MyMTOMEndpointBinding" type="tns:MyMTOMEndpoint"&gt;
-    &lt;soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/&gt;
-    &lt;operation name="sendData"&gt;
-      &lt;soap:operation soapAction="sendData"/&gt;
-
-      &lt;input name="MyMTOMEndpoint_sendData"&gt;
-        &lt;soap:body use="literal"/&gt;
-      &lt;/input&gt;
-      &lt;output name="MyMTOMEndpoint_sendDataResponse"&gt;
-        &lt;soap:body use="literal"/&gt;
-      &lt;/output&gt;
-
-    &lt;/operation&gt;
-  &lt;/binding&gt;
-  &lt;service name="MyMTOMService"&gt;
-    &lt;port name="MyMTOMEndpointPort" binding="tns:MyMTOMEndpointBinding"&gt;
-      &lt;soap:address location="http://localhost:8080/axis2/services/MyMTOMService"/&gt;&lt;/port&gt;&lt;/service&gt;&lt;/definitions&gt;
-
-  </pre>
-</source>
-<p>The important point here is we import http://www.w3.org/2005/05/xmlmime
-and define an element, 'MyBinaryData' , that utilizes MTOM.</p>
-
-<p>The next step is using the Axis2 tool 'WSDL2Java' to generate java source
-files from this WSDL. See the 'Code Generator Tool' guide for more info.
-Here, we define an ant task that chooses XMLBeans as the databinding
-implementation. We also choose to generate an interface which our Skeleton
-will implement. The name we list for the WSDL above is mtomExample.wsdl, and
-we define our package name for our generated source files to be
-'org.apache.axis2.samples.mtomDatabinding.endpoint' . Our ant task for this
-example is:</p>
-<source><pre>&lt;target name="wsdl2java" depends="clean,prepare"&gt;
-      &lt;delete dir="output" /&gt;
-      &lt;java classname="org.apache.axis2.wsdl.WSDL2Java" fork="true"&gt;
-          &lt;classpath refid="axis.classpath"/&gt; 
-          &lt;arg value="-d"/&gt;
-
-          &lt;arg value="xmlbeans"/&gt;
-          &lt;arg value="-uri"/&gt;
-          &lt;arg file="wsdl/mtomExample.wsdl"/&gt;
-          &lt;arg value="-ss"/&gt;
-          &lt;arg value="-ssi"/&gt;
-          &lt;arg value="-g"/&gt;
-
-          &lt;arg value="-sd"/&gt;
-          &lt;arg value="-o"/&gt;
-          &lt;arg file="output"/&gt;
-          &lt;arg value="-p"/&gt;
-          &lt;arg value="org.apache.axis2.samples.mtomDatabinding.endpoint"/&gt;
-      &lt;/java&gt;
-
-      &lt;!-- Move the schema folder to classpath--&gt;
-      &lt;move todir="${build.classes}"&gt;
-          &lt;fileset dir="output/resources"&gt;
-              &lt;include name="*schema*/**/*.class"/&gt;
-              &lt;include name="*schema*/**/*.xsb"/&gt;
-          &lt;/fileset&gt;
-
-      &lt;/move&gt;
-
-  &lt;/target&gt;</pre>
-</source>
-<p>Now we are ready to code. Lets edit
-output/src/org/apache/axis2/samples/mtomDatabinding/endpoint/MyMTOMServiceSkeleton.java
-and fill in the business logic. The end result becomes:</p>
-<source><pre>/**
- * MyMTOMServiceSkeleton.java
- *
- * This file was auto-generated from WSDL
- * by the Apache Axis2 version: SNAPSHOT Jul 19, 2006 (03:46:19 BRT)
- */
-package org.apache.axis2.samples.mtomDatabinding.endpoint;
-
-import java.io.File;
-import java.io.FileOutputStream;
-
-import org.apache.commons.logging.Log;
-import org.apache.commons.logging.LogFactory;
-
-import mymtomns.types.ReturnWebBase;
-import mymtomns.types.SendDataDocument;
-import mymtomns.types.SendDataResponseDocument;
-import mymtomns.types.MyBinaryDataDocument.MyBinaryData;
-import mymtomns.types.SendDataDocument.SendData;
-import mymtomns.types.SendDataResponseDocument.SendDataResponse;
-
-/**
- *  MyMTOMServiceSkeleton java skeleton for the axisService
- */
-public class MyMTOMServiceSkeleton implements MyMTOMServiceSkeletonInterface {
-     
-    /** commons logging declaration. * */
-    private static Log logger = LogFactory
-            .getLog(MyMTOMServiceSkeleton.class);
-    
-    /** Put file received here - change path for your system. */
-    private static final String MY_DIR = "/home/myuser/example_dir/output";
-    /** Success code. */
-    public static final Integer SUCCESS = new Integer(0);
-    /** Failure / Exception code. */
-    public static final Integer FAILURE = new Integer(-1);
-    
-    /**
-     * Auto generated method signature.
-     *
-     * @param sendDataDocument
-     *            input complex object
-     * @return SendDataResponseDocument complex object return values
-     */
-    public SendDataResponseDocument sendData (SendDataDocument sendDataDocument) {
-    
-        // prepare output
-        SendDataResponseDocument retDoc = SendDataResponseDocument.Factory
-                .newInstance();
-
-        SendDataResponse retElement = SendDataResponse.Factory
-                .newInstance();
-    
-        ReturnWebBase returnWebBase = ReturnWebBase.Factory
-                .newInstance();
-
-        try {
-            if (logger.isDebugEnabled()) {
-                logger.debug("Reached mtomExample on the server side...");
-            }
-            SendData sendData = sendDataDocument.getSendData();
-            MyBinaryData myBinaryData = sendData.getMyBinaryData();
-            byte [] myJpegBytes = myBinaryData.getByteArrayValue();
-
-            File jpegFile = new File(MY_DIR+"myJpeg.jpg");
-            FileOutputStream fos = new FileOutputStream(jpegFile);
-            fos.write( myJpegBytes );
-            fos.flush();
-            fos.close();        
-
-            returnWebBase.setSuccessErrorCode(SUCCESS);
-            returnWebBase.setErrorMessage("SUCCESS");
-
-        } catch (Exception ex) {
-            logger.error("MyMTOMServiceSkeleton.sendData error:"
-                    + ex.getMessage(), ex);
-            returnWebBase.setErrorMessage(ex.getMessage());
-            returnWebBase.setSuccessErrorCode(FAILURE);
-        }
-        retElement.setSendDataResult(returnWebBase);
-        retDoc.setSendDataResponse(retElement);
-        return retDoc;
-    }
-     
-}</pre>
-</source>
-<p>The code above receives a jpeg file and writes it to disk. It returns zero
-on success and in the case of an error, returns -1 along with a stacktrace.
-Now lets define the client:</p>
-<source><pre>package client;
-
-import java.io.File;
-import java.io.FileOutputStream;
-import java.io.FileInputStream;
-
-import mymtomns.types.ReturnWebBase;
-import mymtomns.types.SendDataDocument;
-import mymtomns.types.SendDataResponseDocument;
-import mymtomns.types.MyBinaryDataDocument.MyBinaryData;
-import mymtomns.types.SendDataDocument.SendData;
-import mymtomns.types.SendDataResponseDocument.SendDataResponse;
-import org.apache.axis2.samples.mtomDatabinding.endpoint.MyMTOMServiceStub;
-
-public class MTOMXMLBeansClient {
-
-    /** Read file from here - change path for your system. */
-    private static final String MY_DIR = "/home/myuser/example_dir/input/";
-
-    public static void main(String [] args) throws Exception {
- 
-        try {
-            SendData sendData
-                  = SendData.Factory
-                      .newInstance();
-            SendDataDocument doc
-                  = SendDataDocument.Factory
-                      .newInstance();
-            MyBinaryData myBinaryData
-              = MyBinaryData.Factory
-                  .newInstance();
-            
-            File file=new File(MY_DIR + "axis.jpg");
-            FileInputStream stream=new FileInputStream(file);
-            int size=stream.available();
-            byte[] bytes=new byte[size];
-            stream.read(bytes);
-            
-            myBinaryData.setByteArrayValue(bytes);
-            sendData.setMyBinaryData(myBinaryData);
-            doc.setSendData(sendData);
-       
-            MyMTOMServiceStub stub = new MyMTOMServiceStub();
-            SendDataResponseDocument responseDoc = stub
-                      .sendData(doc);
-            SendDataResponse response = responseDoc
-                      .getSendDataResponse();
-            ReturnWebBase result = response.getSendDataResult();
-            // test for errors
-            if (result.getSuccessErrorCode() ==-1) {
-                System.out.println("ERROR: " + result.getErrorMessage());
-            }
-       
-        } catch (Exception e) {
-              e.printStackTrace();
-        }
-    }
-}</pre>
-
-</source>
-<p>The last step is to create an AAR with our Skeleton and the generated
-interface and services.xml, and then deploy the service. See the user guide
-for more info.</p>
 <a name="3"></a>
 
 <h2>SOAP with Attachments (SwA) with Axis2</h2>
@@ -821,15 +536,9 @@
     attachment</strong></li>
 </ul>
 <source><pre>public class SwA {
-    private OperationContext operationContext;
-
     public SwA() {
     }
-
-    public void setOperationContext(OperationContext oc) throws AxisFault {
-        operationContext = oc;
-    }
-
+    
     public void uploadAttachment(OMElement omEle) throws AxisFault {
         OMElement child = (OMElement) omEle.getFirstOMChild();
         OMAttribute attr = child.getAttribute(new QName("href"));
@@ -841,7 +550,8 @@
             contentID = contentID.substring(4);
         }
         
-        Attachments attachment = (Attachments) (operationContext.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE)).getAttachmentMap();
+        MessageContext msgCtx = MessageContext.getCurrentMessageContext();
+        Attachments attachment = msgCtx.getAttachmentMap();
         DataHandler dataHandler = attachment.getDataHandler(contentID);
         ...........
     }



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


Mime
View raw message