axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chinth...@apache.org
Subject svn commit: r366437 [1/6] - in /webservices/axis2/trunk/java/xdocs: ./ 0_93/ 0_93/adb/ 0_93/adb/images/ 0_93/images/ 0_93/images/archi-guide/ 0_93/images/faq/ 0_93/images/tools/ 0_93/images/tools/service/ 0_93/images/tools/wsdl/ 0_93/images/userguide/ ...
Date Fri, 06 Jan 2006 06:31:04 GMT
Author: chinthaka
Date: Thu Jan  5 22:24:56 2006
New Revision: 366437

URL: http://svn.apache.org/viewcvs?rev=366437&view=rev
Log:
Seems xdocs re-strucuring is done now. We will have a separate folder for each and release from here onwards as we better keep old documentation as well. 
People who are changing documents, please get an update and put your documents in correct places.

Added:
    webservices/axis2/trunk/java/xdocs/0_93/Axis2ArchitectureGuide.html
    webservices/axis2/trunk/java/xdocs/0_93/CodegenToolReference.html
    webservices/axis2/trunk/java/xdocs/0_93/CodegenTools-EclipsePlugin.html
    webservices/axis2/trunk/java/xdocs/0_93/OMTutorial.html
    webservices/axis2/trunk/java/xdocs/0_93/ServiceArchiveToolReference.html
    webservices/axis2/trunk/java/xdocs/0_93/adb/
    webservices/axis2/trunk/java/xdocs/0_93/adb/adb-codegen-integration.html
    webservices/axis2/trunk/java/xdocs/0_93/adb/adb-howto.html
    webservices/axis2/trunk/java/xdocs/0_93/adb/adb-tweaking.html
    webservices/axis2/trunk/java/xdocs/0_93/adb/images/
    webservices/axis2/trunk/java/xdocs/0_93/adb/images/ADB.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/axis2config.html
    webservices/axis2/trunk/java/xdocs/0_93/axis2tools.html
    webservices/axis2/trunk/java/xdocs/0_93/http-transport.html
    webservices/axis2/trunk/java/xdocs/0_93/images/
    webservices/axis2/trunk/java/xdocs/0_93/images/Architecture.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/AxisService.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/Component.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/OM001.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/OM002.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/OM003.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/OM004.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/OM005.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/OM006.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/OM007.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/OM008.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/OM1.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/ServerSideFault.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/ServiceDesc.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/TotalArch.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/WomBuilder.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/admin.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/adminlogin.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/adminmain.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/ant.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi-guide/
    webservices/axis2/trunk/java/xdocs/0_93/images/archi-guide/CodegenArchitecture.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi-guide/all.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi-guide/big-picture.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi-guide/contexts.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi-guide/phases.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi-guide/soap-processing.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi-guide/soap.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi001.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi002.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi003.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi004.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi005.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi006.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi007.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi008.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi009.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi010.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi011.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi012.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi013.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi014.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi015.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi016.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi017.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi018.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi019.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi020.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi021.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi022.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi023.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi024.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi025.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/archi026.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/axis.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/ayncresult.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/call.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/callback.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/cases.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clientAPi.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clientside.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image002.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image004.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image006.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image008.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image010.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image012.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image014.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image016.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image018.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image020.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image022.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image024.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/clip_image026.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/codegen.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/correlator.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/deploymetncomponent.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/editserviecpara.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/engine1.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/faq/
    webservices/axis2/trunk/java/xdocs/0_93/images/faq/1.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/faultmsg.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/faultservice.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/globalchain.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/happyaxis.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image001.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image002.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image003.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image004.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image005.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image005.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image006.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image007.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image008.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image009.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image010.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image011.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image012.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/image013.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/maven.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/module.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/moduleengage.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/modules.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/new.gif   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/om2.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/om3.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/parameters.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/removeservice.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/send.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/sendAsync.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/sendRecievce.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/sendRecieveAsync.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/sendRecieveWithListnere.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/serverSide.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/service.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/serviceHandlers.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/ServicePage1.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/ServiceWizardSelection.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/help.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page2.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page3.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page3_hl.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page4_load.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page4_plain.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page4_search_declared.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page4_table.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page5.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page5_added.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page5_browsed.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page5_hl.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page5_remove.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/service_page6.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/service/success_msg.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/wsdl/
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/wsdl/OptionsPage.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/wsdl/OutputPage.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/wsdl/WSDLSelectionPage.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/wsdl/toolSelectionpage.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/tools/wsdl/wizardSelectionPage.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/userguide/
    webservices/axis2/trunk/java/xdocs/0_93/images/userguide/DirectoryStructure.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/userguide/ModuleView.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/userguide/MyServiceDeployed.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/userguide/ServiceDeployed.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/userguide/ServiceItems.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/userguide/TestClient.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/userguide/http-get-ws.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/viewphases.jpg   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/images/wom.png   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/installationguide.html
    webservices/axis2/trunk/java/xdocs/0_93/mail-configuration.html
    webservices/axis2/trunk/java/xdocs/0_93/mail-transport.html
    webservices/axis2/trunk/java/xdocs/0_93/migration.html
    webservices/axis2/trunk/java/xdocs/0_93/mtom-guide.html
    webservices/axis2/trunk/java/xdocs/0_93/rest-ws.html
    webservices/axis2/trunk/java/xdocs/0_93/sec-conf/
    webservices/axis2/trunk/java/xdocs/0_93/sec-conf/in-sample.xml
    webservices/axis2/trunk/java/xdocs/0_93/sec-conf/in.action.xsd
    webservices/axis2/trunk/java/xdocs/0_93/sec-conf/out-action.xsd
    webservices/axis2/trunk/java/xdocs/0_93/sec-conf/out-sample.xml
    webservices/axis2/trunk/java/xdocs/0_93/sec-conf/out-sample2.xml
    webservices/axis2/trunk/java/xdocs/0_93/security-module.html
    webservices/axis2/trunk/java/xdocs/0_93/tcp-transport.html
    webservices/axis2/trunk/java/xdocs/0_93/tools/
    webservices/axis2/trunk/java/xdocs/0_93/tools/CodegenToolReference.pdf   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/ServiceArchiveToolReference.pdf   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig1.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig10.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig11.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig12.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig13.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig14.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig15.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig16.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig17.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig2.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig3.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig4.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig5.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig6.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig7.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig8.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/fig9.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/guide.html
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/idaeguide.pdf   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/idea-icons.GIF   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/idea-icons.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/tools/idea-guide/idea-popup.JPG   (with props)
    webservices/axis2/trunk/java/xdocs/0_93/transport_howto.html
    webservices/axis2/trunk/java/xdocs/0_93/userguide.html
    webservices/axis2/trunk/java/xdocs/0_93/webadminguide.html
Removed:
    webservices/axis2/trunk/java/xdocs/docs.html
    webservices/axis2/trunk/java/xdocs/intro.html

Added: webservices/axis2/trunk/java/xdocs/0_93/Axis2ArchitectureGuide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_93/Axis2ArchitectureGuide.html?rev=366437&view=auto
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_93/Axis2ArchitectureGuide.html (added)
+++ webservices/axis2/trunk/java/xdocs/0_93/Axis2ArchitectureGuide.html Thu Jan  5 22:24:56 2006
@@ -0,0 +1,702 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+  <meta http-equiv="content-type" content="text/html; charset=windows-1252">
+  <title>Axis2 Architecture Guide</title>
+  <meta name="CREATED" content="20050916;22455288">
+  <meta name="CHANGEDBY" content="Chamikara Jayalath">
+  <meta name="CHANGED" content="20050918;22493797">
+</head>
+
+<body lang="en-US" dir="ltr">
+<h1>Axis2 Architecture Guide</h1>
+
+<h2>Contents</h2>
+<ul>
+  <li><p><a href="#bmBP">The Big Picture</a></p>
+  </li>
+  <li><p><a href="#bmInfoMod">Information Model</a></p>
+  </li>
+  <li><p><a href="#bmXML">XML Processing Model</a></p>
+  </li>
+  <li><p><a href="#bmSOAPPM">SOAP Processing Model</a></p>
+  </li>
+  <li><p><a href="#bmDeployment">Deployment</a></p>
+  </li>
+  <li><p><a href="#bmWSDL">WSDL and code generation</a></p>
+  </li>
+  <li><p><a href="#bmDB">Data Binding</a></p>
+  </li>
+  <li><p><a href="#bmClientAPI">Client API</a></p>
+  </li>
+  <li><p><a href="#bmTransports">Transports</a></p>
+  </li>
+</ul>
+
+<p><br>
+<br>
+</p>
+
+<h2><a name="bmBP"></a>The Big Picture</h2>
+
+<p>Any architecture is a result of what that architecture should yield, the
+success of an architecture should be evaluated based on the requirements the
+architecture should meet. Let us start our journey into Axis2 looking at the
+requirements that are expected from Axis2.</p>
+
+<h3>Requirement of Axis2</h3>
+
+<p>In the SOAP terminology, a participant who is taking part in a Web Service
+interaction is known as a SOAP Node. Delivery of a single SOAP Message is
+defined based on two participants, SOAP Sender and SOAP Receiver. Each SOAP
+Message is sent by SOAP Sender and received by SOAP Receiver, and single SOAP
+delivery is the most basic unit that builds the Web Service interactions.</p>
+
+<p>Each SOAP Node may be written in specific programming language, may it be
+Java, C++, .NET or Perl, the Web Services allow them to inter operate. This
+is possible because on the wire each Web Service interaction is done via
+SOAP, which is common to every SOAP Node.</p>
+
+<p><img src="images/archi-guide/soap.gif" name="Graphic1" align="bottom"
+width="691" height="319" border="0"></p>
+
+<p>Web Service middleware handles the complexity in SOAP messaging and lets the
+users work with the programming language they are accustomed to. Axis2
+allows java users to invoke Web Services using java representations,
+and handles the SOAP messaging behind the curtain.</p>
+
+<p>Axis2 handles SOAP processing along with numerous other tasks,
+this makes the life of the Web Service developer a whole lot easier. Following are the
+identified requirements:</p>
+<ol>
+  <li>
+    <p style="margin-bottom: 0in">Provide a framework to process the SOAP
+    messages. The framework should be extensible and the users should be able
+    to extend the SOAP processing per service or per operation basis. Furthermore
+    it should be able to model different Message Exchange Patterns (MEP) using the
+    processing framework.</p>
+  </li>
+  <li>Ability to deploy a Web Services (with
+  or without WSDL)</li>
+  <li>Provide a Client API that can be used to
+    invoke Web Services. This API should support both the Synchronous and
+  Asynchronous programming models.</li>
+  <li>Ability to configure Axis2 and it's
+  components via deployment.</li>
+  <li>Ability to send and receive SOAP messages with different
+  transports.</li>
+</ol>
+
+<p>Apart from the above functionalities, performance in terms of
+memory and speed is a major consideration for Axis2. Axis2 Core Architecture
+is built on three specifications, WSDL, SOAP and WS-Addressing. Other
+specifications like JAX-RPC and SAAJ are layered on top of the Core
+Architecture. The WS-Policy might join the core specifications in the near
+future.</p>
+
+<h3>Axis2, the Architecture</h3>
+
+<p>Now that we have looked at the requirements of the Axis2 we can direct our
+attention to the Architecture.</p>
+
+<p>Axis2 architecture lays out some principals to preserve the uniformity of
+the architecture. They are as follows.</p>
+<ul>
+  <li><p style="margin-bottom: 0in">Axis2 architecture separates the logic
+    and the states. The code that does the processing is stateless inside Axis2.
+    This allows the code to be executed freely by parallel threads.</p>
+  </li>
+  <li>All the information is kept in one information model, this allows
+  the system to be suspended and resumed.</li>
+</ul>
+
+<p>Axis2 architecture is modular and is broken down into
+seven modules.</p>
+<ol>
+  <li><p style="margin-bottom: 0in">Information Model</p>
+  </li>
+  <li>XML processing Model</li>
+  <li>SOAP Processing Model</li>
+  <li>Deployment</li>
+  <li>WSDL and Code Generation</li>
+  <li>Client API</li>
+  <li>Transports</li>
+</ol>
+
+<p><img src="images/archi-guide/all.png" name="Graphic2"
+width="426" height="189" border="0" align="bottom" usemap="#Graphic2Map">
+  <map name="Graphic2Map">
+    <area shape="rect" coords="123,31,222,97" href="#bmInfoMod">
+    <area shape="rect" coords="239,62,319,134" href="#bmXML">
+    <area shape="rect" coords="127,112,218,177" href="#bmSOAPPM">
+    <area shape="rect" coords="12,39,89,95" href="#bmDeployment">
+    <area shape="rect" coords="0,108,94,156" href="#bmWSDL">
+    <area shape="rect" coords="350,31,426,86" href="#bmClientAPI">
+    <area shape="rect" coords="350,114,421,164" href="#bmTransports">
+  </map>
+</p>
+
+<p>Let us look in to the rationale behind each Module, and what each does.</p>
+
+<p>Axis2 defines a model to handle the information and all the states are
+kept in this model. The model has a hierarchy for the information and the
+system manages the life cycle of the objects in this hierarchy.</p>
+
+<p>Handling the SOAP Message is the most important and the most complex task,
+the efficiency of this is the single most important factor that decides the
+performance. It makes sense to delegate this task to a separate module, and
+that module(AXIOM) provides a simple API for SOAP and XML info-set  while
+hiding the complexities of the efficient XML processing within the
+implementation.</p>
+
+<p>SOAP Processing Model controls the execution of the processing, the model
+defines different phases the execution would walk through, and the user can
+extend the Processing Model at some specific places.</p>
+
+<p>Axis2 define a transport framework that enables the user to use different
+transports. The transports fit into specific places in the SOAP
+processing model. The implementation provides a few common transports and the user
+may write new ones if and when it is needed.</p>
+
+<p>Axis2 deployment model allows the user to deploy services, configure the
+transports, extend the SOAP Processing model per system basis, per service
+basis, and per operation basis.</p>
+
+<p>Finally Axis2 provides a code generation tool that will generate server
+side and client side code along with a test case. The generated code would
+simplify the service deployment and the service invocation. This would make
+the Axis2 easier to use.</p>
+
+<h2><a name="bmInfoMod"></a>Information Model</h2>
+
+<p>Information Model has two main hierarchies, the Contexts and
+Descriptions.</p>
+
+<p><img src="images/archi-guide/contexts.png" name="Graphic3" align="bottom"
+width="400" height="443" border="0"></p>
+
+<p>This uses UML notations ( A ----&lt;&gt; B means B has 1 or more objects
+of A. A------&gt;B means the given relationship holds between A and B.)</p>
+
+<p>The two hierarchies are connected as shown in the above figure. The
+Description hierarchy represents the static data. This data may be loaded from
+a configuration file that exists throughout the lifetime of
+Axis2. Examples for such data would be deployed Web Services, operations,
+etc. On the other hand, the context hierarchy holds more dynamic information
+about the things that have more than one instances (e.g.Message Context).</p>
+
+<p>These two hierarchies creates a model that provides the ability to search
+for key value pairs. When the values are searched at a given level, they are
+searched while moving up the hierarchy until a match is found. In the
+resulting model the lower levels overrides the values in the upper levels.
+For an example when a value is looked up at the Message Context and it is
+not found, it would be looked up at the Operation Context etc, up the
+hierarchy. The Search is first done up the hierarchy, and if starting point
+is a Context then it is search in the Description hierarchy as well.</p>
+
+<p>This allows the user to declare and override values, result being a very
+flexible configuration model. The flexibility could be the Achilles heel for
+the system, as the search, specially for something that does not exist is
+expensive, yet in the final analysis developers believe that the flexibility
+would serve better in this instant.</p>
+
+<table width="955" border="1" cellpadding="2" cellspacing="3">
+  <col width="112"><col width="371"><col width="103"><col width="336"><tbody>
+    <tr>
+      <td width="112"><p>Configuration Context</p>
+      </td>
+      <td width="371"><p>Holds the current state of execution. A deep copy of
+        this would essentially make a copy of Axis2.</p>
+      </td>
+      <td width="103"><p>Axis Configuration</p>
+      </td>
+      <td width="336"><p>Holds all global configurations. Transports, global
+        modules, parameters and Services.</p>
+      </td>
+    </tr>
+    <tr>
+      <td width="112"><p>Service Group Context</p>
+      </td>
+      <td width="371"><p>Holds information about a particular usage of the
+        respective service group. The life of a Service Group Context starts
+        when a user starts interacting with a service that belong to this
+        service group. This can be used to share information between services(in
+        the same service group) in a single interaction.</p>
+      </td>
+      <td width="103"><p>ServiceGroup Description</p>
+      </td>
+      <td width="336"><p>Holds deployment time information about a particular
+        service group.</p>
+      </td>
+    </tr>
+    <tr>
+      <td width="112"><p>Service Context</p>
+      </td>
+      <td width="371"><p>This context is available throughout the usage of the
+        respective service. This can be used to share information between
+        several MEPs that belong to the same service, within a single
+        interaction.</p>
+      </td>
+      <td width="103"><p>Service Description</p>
+      </td>
+      <td width="336"><p>Hold the Operations and the service level
+        configurations</p>
+      </td>
+    </tr>
+    <tr>
+      <td width="112"><p>Operation Context</p>
+      </td>
+      <td width="371"><p>Holds the information about the current MEP
+        instance, maintain the Messages in the current MEP etc.</p>
+      </td>
+      <td width="103"><p>Operation Description</p>
+      </td>
+      <td width="336"><p>Holds the operation level configurations</p>
+      </td>
+    </tr>
+    <tr>
+      <td width="112"><p><a name="messageContext"></a>Message Context</p>
+      </td>
+      <td width="371"><p>Holds all the information about the Message
+        currently being executed.</p>
+      </td>
+      <td width="103"><p>Message Description</p>
+      </td>
+      <td width="336"><p>Do not hold any information as yet, but can be used
+        as a future extension point.</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+<h2><a name="bmXML"></a>XML Processing Model</h2>
+
+<p>Please refer to the <a href="OMTutorial.html">OM Tutorial</a></p>
+
+<h2><a name="bmSOAPPM"></a>SOAP Processing Model</h2>
+
+<p><img src="images/archi-guide/soap-processing.gif" name="Graphic4"
+align="bottom" width="755" height="348" border="0"></p>
+
+<p>The architecture identified two basic actions a SOAP processor should
+perform, sending and receiving SOAP messages. The architecture provides two
+Pipes (also named 'Flows'), to perform these two basic actions. Axis Engine
+or the driver of Axis2 defines two methods send() and receive() to implement
+these two Pipes. The two pipes are named <i>In Pipe</i> and <i>Out Pipe</i>,
+and the complex Message Exchange Patterns are constructed by combining these two
+pipes.</p>
+
+<p>Extensibility of the SOAP processing model is provided through 
+Handlers. When a SOAP message is being processed the Handlers that are
+registered would be executed. The Handlers can be registered in global,
+service, or operation scopes and the final handler chain is calculated
+combining the Handlers from all the scopes.</p>
+
+<p>The Handlers act as interceptors and they process parts of the SOAP
+message and provide add on services. Usually Handlers work on the SOAP
+headers yet they may access or change the SOAP Body as well.</p>
+
+<p>When a SOAP message is being sent through the Client API, an <i>Out Pipe</i> would
+begin, the <i>Out Pipe</i> invokes the Handlers and end with a Transport
+Sender that sends the SOAP message to the target endpoint. The SOAP message
+is received by a Transport Receiver at the target endpoint, which reads the
+SOAP message and starts the <i>In Pipe</i>. The In Pipe consists of handlers and 
+ends with the <a href="#mr">Message Receiver</a>, which consumes the SOAP
+message.</p>
+
+<p>Above explained processing happens for each and every SOAP message
+exchanged. After processing one message Axis2 may decide to create other
+SOAP messages, in which case more complex message patterns emerge. However Axis2
+always view the SOAP message in terms of processing of a single message. 
+The combination of the messages are layered on top of that basic framework.</p>
+
+<p>The two pipes does not differentiate between the Server and the Client,
+the SOAP Processing Model handles the complexity and provides two abstract
+pipes to the user. The different areas or the stages of the
+pipes are given names, and according to the Axis2 slang those are named
+'Phases'. A Handler always runs inside a Phase, and the Phase provides a
+mechanism to specify the ordering of Handlers. Both Pipes have built in
+Phases, and both define the areas for 'User Phases' which can be defined by
+the user.</p>
+
+<p>Following figure shows the two pipes with their predefined Phases, the
+user defined Phases would fit in to the User Phases.</p>
+
+<p><img src="images/archi-guide/phases.png" name="Graphic5" align="bottom"
+width="525" height="226" border="0"></p>
+
+<h3>Axis2 Default Processing Model</h3>
+
+<p>Axis2 has the, some inbuilt Handlers that run in inbuilt Phases and they
+create the default configuration for the Axis2, we will be looking more in to
+how to extend the default processing Model in the next section.</p>
+
+<p>There are four special handlers defined in Axis2.</p>
+<ol>
+  <li>
+    <p style="margin-bottom: 0in">Dispatchers - Finds the service and the operation the SOAP
+    message is directed to, always run on the In-Pipe and inside the Dispatch
+    Phase. The in-built dispatchers dispatches to a particular operation depending on various conditions like WS-Addressing information, URI information, SOAP action information, etc., </p>
+  </li>
+  <li><p style="margin-bottom: 0in"><a name="mr"></a>Message Receiver -
+    Consume the SOAP Message and run on the Message Processing Phase in the
+    inflow</p>
+  </li>
+  <li><p>Transport Sender - Send the SOAP message to the SOAP endpoint the
+    message is destined to. Always runs on the</p>
+  </li>
+</ol>
+
+<h3>Processing an Incoming SOAP Message</h3>
+
+<p>Incoming SOAP Message is always received by a Transport Receiver waiting
+for the SOAP Messages, once the SOAP Message is arrived the transport Headers
+are parsed and a <a href="#messageContext">Message Context</a> is created for
+the incoming SOAP Message. The the <i>In Pipe</i> is executed with the
+Message Context. Let us see what would happen at the each Phase of the
+execution, this process my happen in either in the server or the Client,
+there is a special case of using the two way transport where the first four
+phases in the In-Phase most likely to do nothing.</p>
+<ol>
+  <li><p style="margin-bottom: 0in">Transport Phase - The Handlers in the
+    transport Phase are taken from the transport configuration associated,
+    they are executed according to the Phase rules.</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Pre-Dispatch Phase- The Handlers that
+    goes there must be engaged globally (for all services) as the Service
+    does not known at this point. The best example for them would be,
+    Addressing Handlers and may be security Handlers if the Addressing
+    Headers are encrypted.</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Dispatch Phase - The Dispatchers are run
+    in this Phases and find the Service if the service is not found
+    already.</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Post-Dispatch Phase - This phase check
+    weather the service is found, if the service has not found by this point
+    the execution will halt and send a "service not found error". Policy
+    Determination Phase - This Phase does nothing for the time being, this is
+    placed for the implementing the Policy</p>
+  </li>
+  <li><p style="margin-bottom: 0in">User Defined Phases - User defined Phases
+    are executed here.</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Message Validation Phase - Once the user
+    level execution is taken place, this Phase will validates has the SOAP
+    Message Processing has taken place correctly. For an example the must
+    understand processing would happen here.</p>
+  </li>
+  <li><p>Message Processing Phase - The Business logic of the SOAP message,
+    executed here, the a <a href="#mr">Message Receiver</a> is registered
+    with a each Operation. The Message receiver associated with the each
+    operation would be executed as the last Handler of this Phase.</p>
+  </li>
+</ol>
+
+<p>There may be other handlers in the any of the these Phases, users may
+employ custom Handlers to override the mechanics in the each of these Phases.
+If there is a response message, that would be initiated by the <a
+href="#mr">Message Receiver</a>, yet the architecture is not aware of the
+response message and merely invoke the <a href="#mr">Message Receiver</a>.</p>
+
+<h3>Processing of the Outgoing Message</h3>
+
+<p>Out pipe is simpler because the Service and the Operation to dispatch is
+known by the time the pipe is executed. The Out pipe may be initiated by the
+<a href="#mr">Message Receiver</a> or the Client API implementation.</p>
+<ol>
+  <li><p style="margin-bottom: 0in">Message Initialize Phase - Fist Phase of
+    the out pipe, this serves as the placeholder for the custom Handlers</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Policy Determination Phase - Just like in
+    the in-pipe this is not implemented and suppose to serve as a extension
+    point</p>
+  </li>
+  <li><p style="margin-bottom: 0in">User Phases - This executes Handlers in
+    user define Phases</p>
+  </li>
+  <li><p>Transports Phase - Execute any transport Handlers taken from the
+    associated transport configuration and the last handler would be a
+    transport Sender which would send the SOAP message to the target end
+    point</p>
+  </li>
+</ol>
+
+<h3>Extending SOAP Processing Model</h3>
+
+<p>We discussed the default processing model of the Axis2, ability to extend
+the model has been the whole point of spending the energy on the SOAP
+processing model. We shall discuss the extension mechanism for the SOAP
+processing model now.</p>
+
+<p>Idea behind making each step of the SOAP processing in terms of Handlers
+(inbuilt ones we discuss earlier) and placing them in the Phases is to allow
+Handlers to be placed between those Handlers and to override or affect the
+default mechanics. There are two ways the to extend the SOAP Processing
+Model.</p>
+
+<h4>Extending the SOAP Processing Model with Handlers</h4>
+
+<p>The Handlers can specify the Phase they need to be run, further more they
+can specify the there location inside a phase via the following
+information.</p>
+<ol>
+  <li><p style="margin-bottom: 0in">Handler should run as the first in the
+    phases</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Handler should run as the last in the
+    Phases</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Handler should run before a given
+    Handlers</p>
+  </li>
+  <li><p>Handler should run after a Given Handler</p>
+  </li>
+</ol>
+
+<h4>Extending the SOAP Processing Model with Modules</h4>
+
+<p>SOAP processing Model defines a logical entity called a module that
+encapsulates two entities, Handlers and Web Service Operations. The Handlers
+will act in the same way as explained in the first method.</p>
+
+<p>Apart from the extension mechanism based on the Handlers, the WS-*
+specifications suggest a requirement for add new Operations using modules.
+For an example once a user add a Reliable Messaging capability to a Service,
+the "Create Sequence" operation needs to be available to the service end
+point. This can be implemented by letting the Modules define the operations
+and once the module is engaged to a service the operations will be added to
+that service.</p>
+
+<p>A service, operations or the system may engage a module, once the module
+is engaged the handlers and the operations defined in the module are added to
+the entity that engages them. Modules can not be added while the Axis2 is
+running but later they will be available once the system is restarted.</p>
+
+<h2><a name="bmDeployment"></a>Deployment</h2>
+
+<p>There deployment Model provides a concrete mechanism to configure Axis2.
+Deployment Model has four entities that provide the configuration.</p>
+
+<h3>The <em>axis2.xml</em> file</h3>
+
+<p>This file holds the global configuration for the client and server, and
+provide following information.</p>
+<ol>
+  <li><p style="margin-bottom: 0in">The global parameters</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Registered transports in and transport
+    outs</p>
+  </li>
+  <li><p style="margin-bottom: 0in">User defined Phase names</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Modules that are engaged globally</p>
+  </li>
+  <li><p>Globally defines <a href="#mr">Message Receiver</a>s</p>
+  </li>
+</ol>
+
+<h3>Service Archive</h3>
+
+<p>Service archive must have a <em>META-INF/services.xml</em> file and may
+contain the dependent classes. the <em>services.xml</em> file has following
+information.</p>
+<ol>
+  <li><p style="margin-bottom: 0in">Service level parameters</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Modules that are engaged Service level</p>
+  </li>
+  <li><p>Operations inside the Service</p>
+  </li>
+</ol>
+
+<h3>Module Archive</h3>
+
+<p>Module archive must have a <em>META-INF/module.xml</em> file and dependent
+classes the <em>module.xml</em> file has Module parameters and the Operations
+defined in the module.</p>
+
+<p>When the system started up the Axis2 ask the deployment model to create a
+Axis Configuration, the Deployment Model first find a <em>axis2.xml</em> file
+and build the global configuration. Then the Deployment check for the Module
+archives and then for the service archives, the corresponding services and
+Modules are added to the Axis Configuration. System will build Contexts on
+top of the Axis Configurations and the Axis2 is ready to send or receive the
+SOAP Message. The Hot deployment is allowed only for the Service and in that
+case a thread will check the repository repeatedly, and add the Service
+corresponds to the new found Service archives to the repository.</p>
+
+<h2><a name="bmWSDL"></a>WSDL and code generation</h2>
+
+<p>Although the basic objective of the code generation tool has not changed,
+the Code generation module of Axis2 has taken a different approach to
+generate code. Primarily the change is in the use of templates, namely XSL
+templates which gives the code generator the flexibility to generate code in
+multiple languages.</p>
+
+<p>The basic approach is to set the code generator to generate an XML and
+parse it with a template to generate the code file. The following figure
+shows how this shows up in the architecture of the tool.</p>
+
+<p><img src="images/archi-guide/CodegenArchitecture.jpg" name="Graphic6"
+align="bottom" width="478" height="218" border="0"></p>
+
+<p>The fact here is that it is the same information that is extracted from
+the WSDL no matter what code is generated. Code generator uses the WOM (WSDL
+Object Model) internally to manipulate the WSDL and passes that information
+to the emitter which emits an XML. the XML is then parsed with the relevant
+XSL to generate the code. No matter what the language, the process is the
+same except for the template that is being used</p>
+
+<h2><a name="bmDB"></a>Data Binding</h2>
+
+<h3>Integration with the code generation engine</h3>
+
+<p>Axis2 M2 was released with code generation support but without data
+binding. The version 0.9 was shipped with data binding support with complete
+schema support. Such claim is made possible because of the fact that the data
+binding tool, xml-beans, has the full schema support. The original
+architecture of the code generation framework did not undergo significant
+changes because of the way that the code generation framework was originally
+designed. Data binding was incorporated as a pluggable extension to the code
+generation engine. Version 0.91 did not does not support SOAP encoding. It
+only supports RPC literal or document literal massages.</p>
+
+<p><img src="images/codegen.gif" name="Graphic7" align="bottom" width="406"
+height="467" border="0"></p>
+
+<h3>Serialization and De-Serialization</h3>
+
+<p>Xml-beans supports StAX API and AXIOM is based on a StAX API. Data binding
+in Axis2 is achieved through interfacing the AXIOM with the Xml-beans using
+the StAX API which is supported by both parties. At the time of the code
+generation there will be supporter classes for each WSDL operation that will
+have the utility methods that can de-serialize the from AXIOM to data bound
+object and serialize from data bound object to AXIOM. For example if the WSDL
+has an operation called "echoString", once the code is generated there will
+be an echoStringDatabindingSupporter.java class generated that will have
+methods that will look like the following.</p>
+
+<p>public static org.apache.axis2.om.OMElement
+toOM(org.soapinterop.xsd.EchoStringParamDocument param) : This method will
+handle the serialization.</p>
+
+<p>public static org.apache.xmlbeans.XmlObject
+fromOM(org.apache.axis2.om.OMElement param, java.lang.Class type) : This
+method will handle the de-serialization.</p>
+
+<p>public static org.apache.xmlbeans.XmlObject getTestObject(java.lang.Class
+type) : This will be a utility method that can be used to create sample
+objects of the given data bound object.</p>
+
+<h2><a name="bmClientAPI"></a>Client API</h2>
+
+<p>There are three parameters that decide the nature of the Web Service
+interaction.</p>
+<ol>
+  <li><p style="margin-bottom: 0in">Message Exchange Pattern</p>
+  </li>
+  <li><p style="margin-bottom: 0in">The Behavior of the transport. Does it
+    act one-way or two way</p>
+  </li>
+  <li><p>Synchronous/ Asynchronous behavior of the Client API</p>
+  </li>
+</ol>
+
+<p>Variations of the three parameters can result in indefinite number of
+scenarios, even though Axis2 is built on a core that support any messaging
+interaction, the developers were compelled to support only two most widely
+used Message Exchange Patterns.</p>
+
+<p>Two supported transports are One-Way and the Request-Response scenarios in
+the Client API, the implementation is based on a class called
+<code>MEPClient</code> and there are extensions for each Message Exchange
+Pattern that Axis2 Client API supports.</p>
+
+<h3>One Way Messaging Support</h3>
+
+<p>The One-Way support is provided by the <code>InOnlyMEPClient</code> and
+Axis2 provides a class called <code>MessageSender</code> that provides a much simpler
+interface for the user. The Axis2 supports HTTP/SMTP and TCP transports, in
+the case of the HTTP transport the return channel is not used and the HTTP
+202 OK is returned in the return Channel.</p>
+
+<h3>Request Response Messaging Support</h3>
+
+<p>The Request-Response support is provided by the
+<code>InOutMEPClient</code> and Axis2 provides a class called
+<code>Call</code> that provides a much simpler interface for the
+user. The Client API has four ways to configure a given Message Exchange</p>
+<ol>
+  <li><p style="margin-bottom: 0in">Blocking or Non-Blocking nature - this
+    can be decided by using <code>invokeBlocking()</code> or
+    <code>invokeNonBlocking()</code> methods</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Sender transport - transport use to send
+    the SOAP Message</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Listener transport - transport the
+    Response is received</p>
+  </li>
+  <li><p>Use Separate Channel - does the response is send over a separate
+    transport connection or not, this can be false only when sender an
+    listener transport is same and is a two way transport.</p>
+  </li>
+</ol>
+
+<p>Depend on the values for the above four parameter, Axis2 behave
+differently</p>
+
+<h2><a name="bmTransports"></a>Transports</h2>
+
+<p>Axis2 has two basic constructs for transports, named as Transport In
+Configuration and Transport Out Configuration. The <a
+href="#messageContext">Message Context</a> has two fields to put the input
+and the out put transport to be used. Axis behaves according to the transport
+that is specified in each of the fields.</p>
+
+<p>SOAP Message is arrived at the Server side, the incoming transport is
+decided by the Transport Listener that accepts the incoming SOAP Message. The
+transports for the subsequent SOAP Messages that are related to the first
+message, are decided based on the addressing parameters.</p>
+
+<p>At the Client Side the user is free to specify the transport to be used,
+as in the Server side the transport for the subsequent SOAP Messages are
+decided by the addressing.</p>
+
+<p>There Transport In Configuration and the Transport Out Configuration
+contains following information.</p>
+<ol>
+  <li><p style="margin-bottom: 0in">Transport Sender in Out Configuration,
+    Transport Listener in the TransportIn Configuration</p>
+  </li>
+  <li><p style="margin-bottom: 0in">Parameters of the transport</p>
+  </li>
+  <li><p>Transport Handlers</p>
+  </li>
+</ol>
+
+<p>Transport Sender send the SOAP Message over a given transport, each and
+every transport Out Configuration should define a transport Sender that send
+the transport.</p>
+
+<p>Transport Receiver waits for the SOAP Messages and for each SOAP Message
+that arrives, uses the <i>In Pipe</i> to process the SOAP Message.</p>
+
+<p>Axis2 Presently support the following transports</p>
+<ol>
+  <li><p style="margin-bottom: 0in">HTTP - The HTTP transport, the transport
+    Listener is a Servlet or a Simple HTTP server provided by Axis2. The
+    transport Sender uses sockets to connect and send the SOAP Message.
+    Currently we have the commons-HTTP-client based HTTP Transport sender as
+    the default transport</p>
+  </li>
+  <li><p style="margin-bottom: 0in">TCP - This is the most simplest
+    transport, but needed the addressing support to be functional.</p>
+  </li>
+  <li><p>SMTP - This work off a single email account, Transport Receiver is a
+    tread that checks for emails in fixed time intervals.</p>
+  </li>
+</ol>
+</body>
+</html>

Added: webservices/axis2/trunk/java/xdocs/0_93/CodegenToolReference.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_93/CodegenToolReference.html?rev=366437&view=auto
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_93/CodegenToolReference.html (added)
+++ webservices/axis2/trunk/java/xdocs/0_93/CodegenToolReference.html Thu Jan  5 22:24:56 2006
@@ -0,0 +1,665 @@
+<html>
+<head>
+  <meta http-equiv="content-type" content="">
+  <title>Code Generator Wizard - Eclipse Plug-in</title>
+</head>
+
+<body>
+<h1>Code Generator Wizard - Command Line Tool</h1>
+
+<h2>Introduction</h2>
+
+<p>Just as old times there will be users who wish to use the command line
+version of the tool. This basic tool is implemented by the WSDL2Code class
+and just for the convenience in the java case (which would be the majority)
+there is another WSDL2Java class. One can choose to run the main classes
+directly or use one of the scripts to run the WSDL2Code and WSDL2Java
+appropriately. (the scripts are found in the bin directory of the binary
+distribution)</p>
+
+<h2>Option Reference</h2>
+
+<table border="1" cellpadding="0" cellspacing="0"
+style="border-collapse: collapse" width="100%" id="AutoNumber1">
+  <tbody>
+    <tr>
+      <td width="50%">-uri &lt;Location of WSDL&gt;</td>
+      <td width="50%">WSDL file location. This should point to a WSDL file in
+        the local file system</td>
+    </tr>
+    <tr>
+      <td width="50%">-o &lt;output Location&gt; :</td>
+      <td width="50%">output file location. This is where the files would be
+        copied once the code generation is done. If this option is omitted
+        the generated files would be copied to the working directory.</td>
+    </tr>
+    <tr>
+      <td width="50%">-l &lt;language&gt;</td>
+      <td width="50%">Output language. Currently the code generator can
+        generate code in Java and CSharp. (CSharp support is limited) When
+        omitted defaults to Java.
+
+        <p>Allowed options are</p>
+        <ul>
+          <li>java</li>
+          <li>cs</li>
+        </ul>
+      </td>
+    </tr>
+    <tr>
+      <td width="50%">-p &lt;package name&gt;</td>
+      <td width="50%">The target package name. If omitted, a default package
+        (formed using the target  namespace of the WSDL) will be used.</td>
+    </tr>
+    <tr>
+      <td width="50%">-a</td>
+      <td width="50%">Generate code only for async style . when this option
+        is used the generated stubs will have only the asynchronous
+        invocation methods. Switched off by default.</td>
+    </tr>
+    <tr>
+      <td width="50%">-s</td>
+      <td width="50%">Generate code only for sync style . When this option is
+        used the generated stubs will have only the  synchronous invocation
+        methods. Switched off by default. When used with the -a option, this
+        takes precedence.</td>
+    </tr>
+    <tr>
+      <td width="50%">-t</td>
+      <td width="50%">Generates a test case. In the case of Java it would be
+        a junit test case. This test case will generate a dummy
+        implementation of the service and a relevant service.xml and will
+        deploy this particular service in a SimpleHttpServer. Then looking at
+        the WSDL it will generate test methods that will do web service
+        invocation both synchronously and asynchronously and test the
+        deployed service.</td>
+    </tr>
+    <tr>
+      <td width="50%">-ss</td>
+      <td width="50%">Generates server side code (i.e. skeletons). Default is
+        off</td>
+    </tr>
+    <tr>
+      <td width="50%">-sd</td>
+      <td width="50%">Generates the service descriptor (i.e. server.xml).
+        Default is off. only valid with -ss</td>
+    </tr>
+  <tr>
+      <td width="50%">-d</td>
+      <td width="50%">Specifies the Databinding framwork. valid values are xmlbeans,adb and none.
+      Default is xmlbeans.
+</td>
+    </tr>
+  </tbody>
+</table>
+
+<h1>Code Generator Wizard - Ant Task</h1>
+
+<p>The code generator also comes bundled with an Ant task. The ant task is
+implemented by the org.apache.axis2.tool.ant.AntCodegenTask class. Following
+are the ant task attributes.</p>
+
+<h2>Ant Task Reference</h2>
+
+<table border="1" cellpadding="0" cellspacing="0"
+style="border-collapse: collapse" width="100%" id="AutoNumber2">
+  <tbody>
+    <tr>
+      <td width="50%" height="19">wsdlfilename</td>
+      <td width="50%" height="19">WSDL file location. Maps to the uri option
+        of the command line tool</td>
+    </tr>
+    <tr>
+      <td width="50%" height="76">output</td>
+      <td width="50%" height="76">output file location. This is where the
+        files would be copied once the code generation is done. If this
+        option is omitted the generated files would be copied to the working
+        directory. . Maps to the -o option of the command line tool</td>
+    </tr>
+    <tr>
+      <td width="50%" height="171">language</td>
+      <td width="50%" height="171">Output language. Currently the code
+        generator can generate code in Java and CSharp. (CSharp support is
+        limited) When omitted defaults to Java.
+
+        <p>Allowed options are</p>
+        <ul>
+          <li>java</li>
+          <li>cs</li>
+        </ul>
+
+        <p>Maps to the -l option of the command line tool</p>
+      </td>
+    </tr>
+    <tr>
+      <td width="50%" height="57">packagename</td>
+      <td width="50%" height="57">The target package name. If omitted, a
+        default package (formed using the target  namespace of the WSDL) will
+        be used.  Maps to the -p option of the command line tool.</td>
+    </tr>
+    <tr>
+      <td width="50%" height="75">asynconly</td>
+      <td width="50%" height="75">Generate code only for async style . when
+        this option is used the generated stubs will have only the
+        asynchronous invocation methods. Defaults to false if omitted Only
+        true and false are applicable as values. Maps to the -a option of the
+        command line tool.</td>
+    </tr>
+    <tr>
+      <td width="50%" height="16">testcase</td>
+      <td width="50%" height="16">Generates a test case</td>
+    </tr>
+    <tr>
+      <td width="50%" height="19">synconly</td>
+      <td width="50%" height="19">Generate code only for sync style . when
+        this option is used the generated stubs will have only the
+        synchronous invocation methods. Defaults to false if omitted. Only
+        true and false are applicable as values. Maps to the -s option of the
+        command line tool.</td>
+    </tr>
+    <tr>
+      <td width="50%" height="19">serverside</td>
+      <td width="50%" height="19">Generates server side code (i.e.
+        skeletons). Only true and false are applicable as values. Default is
+        false. Maps to the -ss option of the command line tool</td>
+    </tr>
+    <tr>
+      <td width="50%" height="18">generateserverxml</td>
+      <td width="50%" height="18">Generates server side code (i.e.
+        skeletons). Only true and false are applicable as values. Default is
+        false. Maps to the -sd option of the command line tool.</td>
+    </tr>
+  </tbody>
+</table>
+
+<h2>Example build file using the custom Ant task</h2>
+
+<p>Following is an example ant build file that uses the custom Ant task.</p>
+
+<p></p>
+<pre>&lt;?xml version="1.0"?&gt;
+&lt;project name="CodegenExample" default="main" basedir="."&gt;
+&lt;target name="declare" &gt;
+&lt;taskdef name="codegen"
+        classname="org.apache.axis2.tool.ant.AntCodegenTask"
+        classpath="classes"/&gt;
+&lt;/target&gt;
+&lt;target name="main" depends="declare"&gt;
+&lt;codegen 
+    wsdlfilename="C:\test\wsdl\CombinedService.wsdl"
+    output="C:\"
+    serverside="true"
+    generateserverxml="true"
+/&gt;
+&lt;/target&gt;
+&lt;/project&gt;</pre>
+
+<p>Notice the main target that uses the "codegen" task which will use the
+org.apache.axis2.tool.ant.AntCodegenTask class and run the code generation
+tool internally while passing the relevant arguments and do the proper
+generation. If a user types</p>
+
+<p>&gt;ant or &gt;ant main</p>
+
+<p>it will generate the serverside code and service.xml for the given WSDL
+file(C:\test\wsdl\CombinedService.wsdl) and the generated code will be
+written to C:\ directory.</p>
+
+<p>For this Ant task to work the following jars need to be in the class
+path.</p>
+<ul>
+  <li>axis-M2.jar (from the Axis2 distribution)</li>
+  <li>axis-wsdl4j-1.2.jar (The WSDL4J implementation jar. Bundled with the
+    Axis2 distribution)</li>
+  <li>stax-api-1.0.jar (The StAX API's that contain the
+    javax.xml.namespace.QName class. This jar may be replaced by any other
+    jar that contains the javax.xml.namespace.QName implementation. However
+    Axis2 uses this class from the stax-api-1.0.jar which comes bundled with
+    the Axis2 distribution)
+    <p></p>
+  </li>
+</ul>
+
+<h1>Invoking the Code Generator from Ant</h1>
+
+<p>Since the users may find altering their ant class path a bit daunting they
+can also follow an easier technique. The code generator main class can be
+invoked directly through the build file.</p>
+
+<p>Below is an example of a full build.xml needed to run WSDL2Java and
+generate the Java source files, compile the sources, and build an AAR file
+ready for deployment:</p>
+<pre class="code">&lt;!DOCTYPE project&gt;
+
+&lt;project name="wsdl2java-example" default="usage" basedir="."&gt;
+
+  &lt;property name="project-name" value="wsdl2java-example"/&gt;
+  &lt;property file="build.properties"/&gt;
+  
+  &lt;property name="build" value="build"/&gt;
+
+  &lt;property name="src" value="src"/&gt;
+  &lt;property name="build.classes"      value="build/classes" /&gt;
+
+  &lt;path id="axis.classpath"&gt;
+     &lt;pathelement location="build/classes" /&gt;
+     &lt;fileset dir="${axis.home}/lib"&gt;
+       &lt;include name="**/*.jar" /&gt;
+
+     &lt;/fileset&gt;
+     &lt;pathelement location="${build.classes}" /&gt;
+  &lt;/path&gt;
+
+  &lt;target name="usage" description="Build file usage info (default task)"&gt;
+    &lt;echo message=" " /&gt;
+    &lt;echo message="${project-name} " /&gt;
+
+    &lt;echo message="-------------------------------------------------------" /&gt;
+    &lt;echo message=" " /&gt;
+    &lt;echo message="Available Targets:" /&gt;
+    &lt;echo message=" " /&gt;
+    &lt;echo message=" Compiling:" /&gt;
+    &lt;echo message="  compile           - Compiles the WSDL2Java source code" /&gt;
+
+    &lt;echo message=" " /&gt;
+    &lt;echo message=" Compiling client:" /&gt;
+    &lt;echo message="  compile_client           - Compiles the client source code" /&gt;
+    &lt;echo message=" " /&gt;
+    &lt;echo message=" Cleaning up:" /&gt;
+    &lt;echo message="  clean             - Delete class files" /&gt;
+
+    &lt;echo message=" " /&gt;
+    &lt;echo message=" WSDL:" /&gt;
+    &lt;echo message="  wsdl2java               - Generate source from WSDL" /&gt;
+    &lt;echo message=" " /&gt;
+    &lt;echo message=" AAR:" /&gt;
+    &lt;echo message="  aar               - Generate an .aar for deployment into WEB-INF/services" /&gt;
+
+    &lt;echo message=" " /&gt;
+    &lt;echo message=" Executing:" /&gt;
+    &lt;echo message="  runLogin               - Execute the runLogin client" /&gt;
+  &lt;/target&gt;
+
+  &lt;target name="prepare" &gt;
+    &lt;mkdir dir="${build.classes}" /&gt;
+
+  &lt;/target&gt;
+
+  &lt;target name="clean" &gt;
+     &lt;delete dir="${build}" /&gt;
+     &lt;delete dir="${dist}" /&gt;
+  &lt;/target&gt;
+
+  &lt;target name="compile"&gt;
+    &lt;echo message="Compiling wsdl2 files"/&gt;
+
+    &lt;javac
+     srcdir="output"
+     destdir="${build.classes}"
+     deprecation="true"
+     failonerror="true" debug="true"
+    &gt;
+
+     &lt;classpath refid="axis.classpath"/&gt; 
+    &lt;/javac&gt;
+
+  &lt;/target&gt;
+
+  &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="-uri"/&gt;
+
+          &lt;arg file="wsdl/LoginEndpoint.wsdl"/&gt;
+          &lt;arg value="-ss"/&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.example.types"/&gt;
+      &lt;/java&gt;
+
+      &lt;!-- Move the schema folder to classpath--&gt;
+      &lt;move todir="${build.classes}"&gt;
+          &lt;fileset dir="output"&gt;
+              &lt;include name="**/*schema*/**/*.class"/&gt;
+
+              &lt;include name="**/*schema*/**/*.xsb"/&gt;
+          &lt;/fileset&gt;
+      &lt;/move&gt;
+
+  &lt;/target&gt;
+
+  &lt;target name="jar_wsdl" depends="compile"&gt;
+
+  &lt;jar jarfile="lib/axis2_example_wsdl.jar" &gt;
+  &lt;fileset dir="${build}/classes" /&gt;
+  &lt;/jar&gt;
+  &lt;/target&gt;
+  
+  &lt;!-- build an .aar file for axis2 web services --&gt;
+  &lt;target name="aar" depends="compile"&gt;
+
+     &lt;delete dir="${build.classes}/META-INF" /&gt;
+     &lt;mkdir dir="${build.classes}/META-INF" /&gt;
+     &lt;copy todir="${build.classes}/META-INF" &gt;
+       &lt;fileset dir="output/service_descriptors/LoginEndpoint" &gt;
+         &lt;!-- axis2 web services definitions file --&gt;
+         &lt;include name="services.xml"/&gt;
+
+       &lt;/fileset&gt;
+       &lt;fileset dir="wsdl" &gt;
+         &lt;include name="LoginEndpoint.wsdl"/&gt;
+       &lt;/fileset&gt;
+     &lt;/copy&gt;
+     &lt;jar jarfile="dist/LoginEndpoint.aar" &gt;
+
+       &lt;fileset dir="${build.classes}" /&gt;
+     &lt;/jar&gt;
+  &lt;/target&gt;
+
+  &lt;target name="compile_client"&gt;
+    &lt;echo message="Compiling client files"/&gt;
+
+    &lt;javac
+     srcdir="src"
+     destdir="${build.classes}"
+     deprecation="true"
+     failonerror="true" debug="true"
+    &gt;
+
+     &lt;classpath refid="axis.classpath"/&gt; 
+    &lt;/javac&gt;
+
+  &lt;/target&gt;
+
+  &lt;target name="runLogin" depends="compile_client" description="run webLogin client"&gt;
+
+     &lt;echo message="running the webLogin client" /&gt;
+     &lt;java classname="org.client.LoginClient" &gt;
+      &lt;classpath refid="axis.classpath"/&gt; 
+    &lt;/java&gt;
+  &lt;/target&gt;
+
+&lt;/project&gt;
+</pre>
+
+<p>The above build.xml depends on a build.properties file which defines
+'axis.home', such as:</p>
+
+<p>axis.home=/home/username/axis2-0.93-bin/</p>
+
+<p>The above build.xml example also assumes three empty directories exist,
+'dist', 'lib', and 'src'.</p>
+
+<p>Below is a validated WSDL Document following the Document/Literal Style.
+The name of this file matches the name used in the WSDL2Java ant task above,
+LoginEndpoint.wsdl</p>
+<pre class="code">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+
+&lt;definitions name="LoginService" targetNamespace="http://login" xmlns:tns="http://login" 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://login/types"&gt;
+
+  &lt;types&gt;
+    &lt;schema targetNamespace="http://login/types" xmlns:tns="http://login/types" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema"&gt;
+      &lt;import namespace="http://schemas.xmlsoap.org/soap/encoding/"/&gt;
+      &lt;element name="returnWebLoginElement"&gt;
+        &lt;complexType&gt;
+          &lt;sequence&gt;
+
+            &lt;element ref="tns:soap_session_idElement"/&gt;
+            &lt;element ref="tns:web_user_nameElement"/&gt;
+          &lt;/sequence&gt;
+        &lt;/complexType&gt;
+      &lt;/element&gt;
+      &lt;element name="webLoginElement"&gt;
+
+        &lt;complexType&gt;
+          &lt;sequence&gt;
+            &lt;element ref="tns:user_nameElement"/&gt;
+            &lt;element ref="tns:user_passwordElement"/&gt;
+          &lt;/sequence&gt;
+        &lt;/complexType&gt;
+
+      &lt;/element&gt;
+      &lt;element name="user_nameElement" type="xsd:string"/&gt;
+      &lt;element name="user_passwordElement" type="xsd:string"/&gt;
+      &lt;element name="soap_session_idElement" type="xsd:string"/&gt;
+      &lt;element name="web_user_nameElement" type="xsd:string"/&gt;
+&lt;/schema&gt;&lt;/types&gt;
+
+  &lt;message name="LoginEndpoint_webLogin"&gt;
+     &lt;part name="parameters" element="ns2:webLoginElement"/&gt;
+  &lt;/message&gt;
+  &lt;message name="LoginEndpoint_webLoginResponse"&gt;
+    &lt;part name="result" element="ns2:returnWebLoginElement"/&gt;
+  &lt;/message&gt;
+
+  &lt;portType name="LoginEndpoint"&gt;
+    &lt;operation name="webLogin"&gt;
+      &lt;input message="tns:LoginEndpoint_webLogin" name="LoginEndpoint_webLogin"/&gt;
+      &lt;output message="tns:LoginEndpoint_webLoginResponse" name="LoginEndpoint_webLoginResponse"/&gt;
+    &lt;/operation&gt;
+  &lt;/portType&gt;
+
+  &lt;binding name="LoginEndpointBinding" type="tns:LoginEndpoint"&gt;
+    &lt;soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/&gt;
+    &lt;operation name="webLogin"&gt;
+      &lt;soap:operation soapAction="webLogin"/&gt;
+      &lt;input name="LoginEndpoint_webLogin"&gt;
+        &lt;soap:body use="literal"/&gt;
+
+      &lt;/input&gt;
+      &lt;output name="LoginEndpoint_webLoginResponse"&gt; 
+        &lt;soap:body use="literal"/&gt;
+      &lt;/output&gt;
+    &lt;/operation&gt;
+  &lt;/binding&gt;
+
+  &lt;service name="LoginService"&gt;
+    &lt;port name="LoginEndpointPort" binding="tns:LoginEndpointBinding"&gt;
+      &lt;soap:address location="http://localhost:8080/axis2/services/LoginEndpoint"/&gt;&lt;/port&gt;&lt;/service&gt;&lt;/definitions&gt;</pre>
+
+<p>Place the above file, named LoginEndpoint.wsdl, in the directory 'wsdl'
+below the build.xml file. Run the WSDL2Java command via the ant task defined
+above, and there will be a directory called 'output' created. This directory
+contains the WSDL2Java generated source. An important detail is that an
+XMLBean class file is also generated by WSDL2Java, TypeSystemHolder.class.
+That file is placed into build/classes by the above ant task and will be
+needed to compile the generated sources.</p>
+
+<p>The next step is to modify the generated Skeleton Java Source file - the
+Web Service. This file as generated returns null and needs to be updated to
+contain the business logic.</p>
+
+<p>After the WSDL2Java command runs the file LoginEndpoint.wsdl, edit the
+following file:</p>
+
+<p>output/org/example/types/LoginEndpointSkeleton.java. You should see the
+following code:</p>
+<pre class="code">package org.example.types;
+    /**
+     *  Auto generated java skeleton for the service by the Axis code generator
+     */
+    public class LoginEndpointSkeleton {
+     
+ 
+        /**
+         * Auto generated method signature
+         
+          * @param param0
+         
+         */
+        public  org.example.types.databinding.login.ReturnWebLoginElementDocument webLogin
+                  (org.example.types.databinding.login.WebLoginElementDocument param0 ){
+                //Todo fill this with the necessary business logic
+                return null;
+        }
+     
+    }</pre>
+
+<p>Replace the contents of this file with the following, which uses the
+complex types generated by WSDL2Java and the example wsdl file:</p>
+<pre class="code">package org.example.types;
+import org.example.types.databinding.login.ReturnWebLoginElementDocument;
+import org.example.types.databinding.login.WebLoginElementDocument.WebLoginElement;
+
+/**
+ *  Auto generated java skeleton for the service by the Axis code generator
+ */
+public class LoginEndpointSkeleton {
+ 
+    /**
+     * Auto generated method signature
+     
+      * @param webLoginElementDocument changed from param0
+     
+     */
+    public  org.example.types.databinding.login.ReturnWebLoginElementDocument webLogin
+              (org.example.types.databinding.login.WebLoginElementDocument webLoginElementDocument ){
+
+            //Todo fill this with the necessary business logic
+            System.out.println("LoginEndpointSkeleton.webLogin reached successfully!");
+
+            // Get parameters passed in 
+            WebLoginElement webLoginElement = webLoginElementDocument.getWebLoginElement();
+            String userName = webLoginElement.getUserNameElement();
+            String password = webLoginElement.getUserPasswordElement();
+            System.out.println("LoginEndpointSkeleton.webLogin userName: " + userName);
+            System.out.println("LoginEndpointSkeleton.webLogin password: " + password);
+     
+            // input paramaters would be used here 
+    
+            // prepare output
+            org.example.types.databinding.login.ReturnWebLoginElementDocument retDoc =
+                org.example.types.databinding.login.ReturnWebLoginElementDocument.Factory.newInstance();
+            
+            org.example.types.databinding.login.ReturnWebLoginElementDocument.ReturnWebLoginElement
+            retElement =
+             org.example.types.databinding.login.ReturnWebLoginElementDocument.ReturnWebLoginElement.Factory.newInstance();
+            
+            retElement.setWebUserNameElement("joe sixpack");
+            retElement.setSoapSessionIdElement("some_random_string");
+            System.out.println("validate retElement: " + retElement.validate());
+
+            retDoc.setReturnWebLoginElement(retElement);
+            System.out.println("validate retDoc: " + retDoc.validate());
+            
+            System.out.println("LoginEndpointSkeleton.webLogin returning...");
+    
+            return retDoc; 
+    
+
+    }
+ 
+}
+</pre>
+
+<p>The next steps assume the axis2.war has been deployed and has expanded in
+a servlet container.</p>
+
+<p>Run the 'jar_wsdl' ant task from the example build.xml, which generates a
+jar file lib/axis2_example_wsdl.jar in the 'lib' directory under the
+build.xml . This jar will be used to compile the client, and also will be
+placed in the servlet container. Next, run the 'aar' ant task from the
+example build.xml, which generates the deployable axis2 web service. Place
+dist/LoginEndpoint.aar into axis2/WEB-INF/services . Place
+lib/axis2_example_wsdl.jar into axis2/WEB-INF/lib . Verify the happy axis
+page loaded the services correctly - there should be the service
+'LoginEndpoint' with the available operation 'webLogin' displayed.</p>
+
+<p>The last step is to create and run the client. In the src directory create
+the file org.client.LoginClient.java, with the contents below:</p>
+<pre class="code">package org.client;
+
+import org.apache.axis2.AxisFault;
+
+import org.example.types.LoginEndpointStub;
+import org.example.types.databinding.login.WebLoginElementDocument;
+import org.example.types.databinding.login.WebLoginElementDocument.WebLoginElement;
+import org.example.types.databinding.login.ReturnWebLoginElementDocument;
+import org.example.types.databinding.login.WebLoginElementDocument;
+import org.example.types.databinding.login.WebLoginElementDocument.WebLoginElement;
+
+/**
+ * Login.
+ *
+ */
+public class LoginClient {
+
+    public static void main(String[] args) {
+        try {
+
+            System.out.println("webLogin, firing...");
+            LoginEndpointStub stub = 
+                new LoginEndpointStub(null, 
+                    "http://localhost:8080/axis2/services/LoginEndpoint");
+                    
+            WebLoginElementDocument webLoginElementDocument 
+                = WebLoginElementDocument.Factory.newInstance();
+            WebLoginElement webLoginElement = 
+                WebLoginElement.Factory.newInstance();
+            webLoginElement.setUserNameElement("joe");
+            webLoginElement.setUserPasswordElement("sixpack");
+            
+            webLoginElementDocument.setWebLoginElement(webLoginElement);
+            
+            System.out.println("validate: " +  webLoginElement.validate());
+             stub.webLogin(webLoginElementDocument);
+ 
+            ReturnWebLoginElementDocument returnWebLoginElementDocument = 
+                stub.webLogin(webLoginElementDocument);
+
+            System.out.println("Client returned");
+
+            org.example.types.databinding.login.ReturnWebLoginElementDocument.ReturnWebLoginElement
+                retElement = returnWebLoginElementDocument.getReturnWebLoginElement();
+
+            System.out.println("WebUserName: " + retElement.getWebUserNameElement());
+            System.out.println("SOAPSessionId: " + retElement.getSoapSessionIdElement());
+            System.out.println("webLogin, completed!!!");
+
+        } catch (AxisFault axisFault) {
+            axisFault.printStackTrace();
+        } catch (Exception ex) {
+            ex.printStackTrace();
+        }
+    }
+}
+
+</pre>
+
+<p>Now run the ant task 'ant runLogin' . The following output should
+appear:</p>
+<pre class="code">runLogin:
+     [echo] running the webLogin client
+     [java] webLogin, firing...
+     [java] validate: true
+     [java] Client returned
+     [java] WebUserName: joe sixpack
+     [java] SOAPSessionId: some_random_string
+     [java] webLogin, completed!!!</pre>
+
+<p></p>
+
+<h1>Appendix</h1>
+<ul>
+  <li>Eclipse reference - <a href="http://www.eclipse.org/">
+    http://www.eclipse.org/</a></li>
+  <li>Custom Ant Tasks  - <a
+    href="http://ant.apache.org/manual/develop.html">
+    http://ant.apache.org/manual/develop.html</a></li>
+</ul>
+
+<p> </p>
+
+<p> </p>
+
+<p> </p>
+
+<p> </p>
+
+<p> </p>
+</body>
+</html>

Added: webservices/axis2/trunk/java/xdocs/0_93/CodegenTools-EclipsePlugin.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_93/CodegenTools-EclipsePlugin.html?rev=366437&view=auto
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_93/CodegenTools-EclipsePlugin.html (added)
+++ webservices/axis2/trunk/java/xdocs/0_93/CodegenTools-EclipsePlugin.html Thu Jan  5 22:24:56 2006
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+      "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+  <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
+  <title>Codegen Eclipse Wizard - Eclipse Plugin</title>
+  <meta name="generator" content="amaya 9.2.1, see http://www.w3.org/Amaya/"
+  />
+</head>
+
+<body>
+
+<h1>Code Generator Wizard - Eclipse Plug-in</h1>
+
+<h2>Introduction</h2>
+
+<p>The Axis2 code generator comes built-in with an <a
+href="http://www.eclipse.org">Eclipse</a> plug-in. This document explains the
+installation and usage of the Axis2 code generator plug-in.</p>
+
+<h2>Installation</h2>
+
+<p>The easiest way to obtain the plug-in would be the binary distribution.
+The full Axis binary distribution contains the compiled version of this
+plug-in under the tools directory.</p>
+
+<p>If one needs to build the plugin from source it is not as trivial as
+running the Maven build. The reason is that the plug-in depends heavily on
+the Eclipse classes, which are only available in an Eclipse environment. The
+recommended procedure is to run the create-project.xml (in the "modules\tool"
+directory of the source distribution) build file which will create two
+folders (the other one for the Service Archiver tool) and copy the necessary
+files to relevant folders. Then Eclipse should be configured to open the
+contents in a PDE project. Please go through the Eclipse documentation to
+learn how to open projects in the PDE format.</p>
+
+<p>Once you've obtained the plug-in just unzip the content of the plug-in
+archive to the eclipse plug-in directory (if it is the zipped-binary version)
+or copy the necessary folders to the eclipse plug-in directory and restart
+Eclipse.</p>
+
+<p><i>Note - This plug-in works on Eclipse version 3.0 and upwards</i></p>
+
+<h2>Operation</h2>
+
+<p>If the plug-in is properly installed you should see a new wizard under the
+"New" section.(use the File -&gt; New -&gt; Other or Ctrl + N )</p>
+
+<p><img src="images/tools/wsdl/wizardSelectionPage.jpg" width="500"
+height="500" alt=""/></p>
+
+<p>Selecting the wizard and pressing the next button will start the code
+generator wizard. Following is the first wizard page.</p>
+
+<p><img src="images/tools/wsdl/toolSelectionpage.jpg" width="557"
+height="501" alt=""/></p>
+
+<p>Selecting the generate code from WSDL option leads to the next page. Note
+that the Java-to-WSDL tool is disabled.</p>
+
+<p><img  src="images/tools/wsdl/WSDLSelectionPage.jpg" width="518"
+height="500" alt=""/></p>
+
+<p>To move on to the next page the WSDL file location must be given. The
+browse button can be used to easily browse for a file rather than typing the
+whole path.</p>
+
+<p>Once the WSDL file is selected, codegen options are to be selected. By far
+this is the most important page in this wizard, which determines the
+characteristics of the code being generated. Novices need not worry about
+these options since the most common options are defaulted, But advanced users
+will find it very easy to "turn the knobs" using these options.</p>
+
+<p><img border="0" src="images/tools/wsdl/OptionsPage.jpg" width="518"
+height="500" alt=""/></p>
+
+<p>Once the options are taken care of, only the final step of the code
+generation is left. it is the selection of the output file location.</p>
+
+<p><img border="0" src="images/tools/wsdl/OutputPage.jpg" width="518"
+height="500" alt=""/></p>
+
+<p>When the output file location is selected, the Finish button will be
+enabled. Pressing the finish button will generate the code and a message box
+will pop up acknowledging the success. Well Done! Now you are ready for Axis2
+Code generation.</p>
+</body>
+</html>



Mime
View raw message