You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by ch...@apache.org on 2006/01/05 10:25:50 UTC
svn commit: r366133 [1/10] - in /webservices/site/trunk/targets/axis2: ./
0_93/ 0_94/ 0_94/adb/ 0_94/adb/images/ 0_94/images/
0_94/images/archi-guide/ 0_94/images/faq/ 0_94/images/logos/
0_94/images/tools/ 0_94/images/tools/service/ 0_94/images/tools/w...
Author: chinthaka
Date: Thu Jan 5 01:17:47 2006
New Revision: 366133
URL: http://svn.apache.org/viewcvs?rev=366133&view=rev
Log:
Adding temporary 0.94 docs.
Added:
webservices/site/trunk/targets/axis2/0_93/index.html
webservices/site/trunk/targets/axis2/0_94/
webservices/site/trunk/targets/axis2/0_94/Axis2ArchitectureGuide.html
webservices/site/trunk/targets/axis2/0_94/CodegenToolReference.html
webservices/site/trunk/targets/axis2/0_94/CodegenToolReference.pdf (with props)
webservices/site/trunk/targets/axis2/0_94/CodegenTools-EclipsePlugin.html
webservices/site/trunk/targets/axis2/0_94/OMTutorial.html
webservices/site/trunk/targets/axis2/0_94/ServiceArchiveToolReference.html
webservices/site/trunk/targets/axis2/0_94/adb/
webservices/site/trunk/targets/axis2/0_94/adb/adb-codegen-integration.html
webservices/site/trunk/targets/axis2/0_94/adb/adb-howto.html
webservices/site/trunk/targets/axis2/0_94/adb/adb-tweaking.html
webservices/site/trunk/targets/axis2/0_94/adb/images/
webservices/site/trunk/targets/axis2/0_94/adb/images/ADB.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/axis2config.html
webservices/site/trunk/targets/axis2/0_94/axis2tools.html
webservices/site/trunk/targets/axis2/0_94/http-transport.html
webservices/site/trunk/targets/axis2/0_94/images/
webservices/site/trunk/targets/axis2/0_94/images/Architecture.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/AxisService.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/Component.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/OM001.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/OM002.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/OM003.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/OM004.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/OM005.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/OM006.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/OM007.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/OM008.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/OM1.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/ServerSideFault.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/ServiceDesc.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/TotalArch.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/WomBuilder.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/add.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/admin.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/adminlogin.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/adminmain.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/ant.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi-guide/
webservices/site/trunk/targets/axis2/0_94/images/archi-guide/CodegenArchitecture.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi-guide/all.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi-guide/big-picture.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi-guide/contexts.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi-guide/phases.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi-guide/soap-processing.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi-guide/soap.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi001.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi002.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi003.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi004.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi005.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi006.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi007.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi008.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi009.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi010.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi011.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi012.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi013.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi014.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi015.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi016.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi017.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi018.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi019.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi020.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi021.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi022.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi023.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi024.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi025.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/archi026.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/axis.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/ayncresult.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/call.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/callback.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/cases.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clientAPi.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/clientside.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image002.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image004.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image006.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image008.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image010.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image012.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image014.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image016.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image018.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image020.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image022.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image024.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/clip_image026.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/codegen.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/collapsed.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/correlator.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/deploymetncomponent.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/editserviecpara.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/engine1.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/expanded.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/external-classic.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/external.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/faq/
webservices/site/trunk/targets/axis2/0_94/images/faq/1.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/faultmsg.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/faultservice.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/file.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/fix.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/folder-closed.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/folder-open.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/globalchain.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/happyaxis.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/help_logo.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_alert.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_alertsml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_arrowfolder1_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_arrowfolder2_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_arrowfolderclosed1_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_arrowfolderopen2_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_arrowmembers1_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_arrowmembers2_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_arrowusergroups1_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_arrowusergroups2_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_arrowwaste1_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_arrowwaste2_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_confirmsml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_doc_lrg.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_doc_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_error_lrg.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_error_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_folder_lrg.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_folder_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_help_lrg.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_help_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_info_lrg.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_info_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_infosml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_members_lrg.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_members_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_sortdown.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_sortleft.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_sortright.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_sortup.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_success_lrg.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_success_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_usergroups_lrg.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_usergroups_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_warning_lrg.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_warning_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_waste_lrg.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/icon_waste_sml.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/image001.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/image002.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/image003.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/image004.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/image005.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/image005.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/image006.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/image007.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/image008.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/image009.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/image010.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/image011.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/image012.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/image013.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-bolt.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-brewed.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-build-successfull.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-built.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-bulldozer.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-button-1.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-button-2.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-button-3.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-button-4.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-button-5.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-button-black.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-button-blue.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-button-copper.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-button-green.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-button-pinky.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-button-purple.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-button-teal.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-feather.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-frankenstein.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-mavenfactured.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-petesucks.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-propaganda-2.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-propaganda.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/logos/maven-redgreen.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/maven.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/module.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/moduleengage.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/modules.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/new.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/newwindow-classic.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/newwindow.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/none.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/nw_maj.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/nw_maj_hi.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/nw_maj_rond.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/nw_med.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/nw_med_hi.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/nw_med_rond.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/nw_min.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/nw_min_036.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/nw_min_hi.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/om2.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/om3.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/parameters.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/pdf.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/poweredby_036.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/product_logo.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/remove.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/removeservice.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/se_maj_rond.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/send.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/sendAsync.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/sendRecievce.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/sendRecieveAsync.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/sendRecieveWithListnere.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/serverSide.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/service.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/serviceHandlers.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/servicegroups.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/strich.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/sw_maj_rond.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/sw_med_rond.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/sw_min.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/
webservices/site/trunk/targets/axis2/0_94/images/tools/service/
webservices/site/trunk/targets/axis2/0_94/images/tools/service/ServicePage1.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/ServiceWizardSelection.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/help.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page2.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page3.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page3_hl.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page4_load.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page4_plain.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page4_search_declared.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page4_table.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page5.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page5_added.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page5_browsed.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page5_hl.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page5_remove.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/service_page6.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/service/success_msg.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/wsdl/
webservices/site/trunk/targets/axis2/0_94/images/tools/wsdl/OptionsPage.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/wsdl/OutputPage.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/wsdl/WSDLSelectionPage.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/wsdl/toolSelectionpage.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/tools/wsdl/wizardSelectionPage.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/update.gif (with props)
webservices/site/trunk/targets/axis2/0_94/images/userguide/
webservices/site/trunk/targets/axis2/0_94/images/userguide/DirectoryStructure.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/userguide/ModuleView.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/userguide/MyServiceDeployed.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/userguide/ServiceDeployed.JPG (with props)
webservices/site/trunk/targets/axis2/0_94/images/userguide/ServiceItems.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/userguide/TestClient.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/userguide/http-get-ws.png (with props)
webservices/site/trunk/targets/axis2/0_94/images/viewphases.jpg (with props)
webservices/site/trunk/targets/axis2/0_94/images/wom.png (with props)
webservices/site/trunk/targets/axis2/0_94/index.html
webservices/site/trunk/targets/axis2/0_94/installationguide.html
webservices/site/trunk/targets/axis2/0_94/mail-configuration.html
webservices/site/trunk/targets/axis2/0_94/mail-transport.html
webservices/site/trunk/targets/axis2/0_94/migration.html
webservices/site/trunk/targets/axis2/0_94/mtom-guide.html
webservices/site/trunk/targets/axis2/0_94/rest-ws.html
webservices/site/trunk/targets/axis2/0_94/sec-conf/
webservices/site/trunk/targets/axis2/0_94/sec-conf/in-sample.png (with props)
webservices/site/trunk/targets/axis2/0_94/sec-conf/in.action.xsd
webservices/site/trunk/targets/axis2/0_94/sec-conf/out-action.xsd
webservices/site/trunk/targets/axis2/0_94/sec-conf/out-sample.png (with props)
webservices/site/trunk/targets/axis2/0_94/sec-conf/out-sample2.png (with props)
webservices/site/trunk/targets/axis2/0_94/security-module.html
webservices/site/trunk/targets/axis2/0_94/tcp-transport.html
webservices/site/trunk/targets/axis2/0_94/transport_howto.html
webservices/site/trunk/targets/axis2/0_94/userguide.html
webservices/site/trunk/targets/axis2/0_94/webadminguide.html
Modified:
webservices/site/trunk/targets/axis2/dependencies.html
webservices/site/trunk/targets/axis2/download.html
webservices/site/trunk/targets/axis2/downloads.html
webservices/site/trunk/targets/axis2/faq.html
webservices/site/trunk/targets/axis2/guidelines.html
webservices/site/trunk/targets/axis2/index.html
webservices/site/trunk/targets/axis2/intro.html
webservices/site/trunk/targets/axis2/issue-tracking.html
webservices/site/trunk/targets/axis2/mail-lists.html
webservices/site/trunk/targets/axis2/maven-help.html
webservices/site/trunk/targets/axis2/maven-reports.html
webservices/site/trunk/targets/axis2/overview.html
webservices/site/trunk/targets/axis2/project-info.html
webservices/site/trunk/targets/axis2/projects-overview.html
webservices/site/trunk/targets/axis2/refLib.html
webservices/site/trunk/targets/axis2/siteHowTo.html
webservices/site/trunk/targets/axis2/svn.html
webservices/site/trunk/targets/axis2/team-list.html
webservices/site/trunk/targets/axis2/thanks.html
Added: webservices/site/trunk/targets/axis2/0_93/index.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/axis2/0_93/index.html?rev=366133&view=auto
==============================================================================
--- webservices/site/trunk/targets/axis2/0_93/index.html (added)
+++ webservices/site/trunk/targets/axis2/0_93/index.html Thu Jan 5 01:17:47 2006
@@ -0,0 +1,50 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><title>Axis 2.0 - Axis2 0.93 Documentation</title><style type="text/css" media="all">
+ @import url("../style/maven-base.css");
+
+ @import url("../style/maven-theme.css");</style><link rel="stylesheet" href="../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://www.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://www.apache.org/images/asf-logo.gif"></img></a><a href="http://ws.apache.org/axis2/" id="projectLogo"><img alt="Apache Axis 2.0" src="http://ws.apache.org/axis2/images/axis.jpg"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
+ Last published: 05 January 2006
+ | Doc for 0.94</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis_2_0"><h5>Axis 2.0</h5><ul><li class="none"><a href="../index.html">Home</a></li><li class="expanded"><a href="../">Download Axis2</a><ul><li class="none"><a href="../download.cgi">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/?root=Apache-SVN" class="externalLink" title="External Link">Source Code</a></li></ul></li><li class="expanded"><a href="../">Documentation</a><ul><li class="none"><strong><a href="../0_93/index.html">Version 0.93</a></strong></li><li class="none"><a href="../0_94/index.html">Version 0.94</a></li></ul></li><li class="expanded"><a href="../overview.html">Get Involved</a><ul><li class="none"><a href="../svn.html">Checkout the Source</a></li><li class="none"><a href="../siteHowTo.html">Build the Site</a></li><li class="none"><a href="../guide
lines.html">Developer Guidelines</a></li><li class="none"><a href="../refLib.html">Reference Library</a></li><li class="none"><a href="../mail-lists.html">Mailing Lists</a></li><li class="none"><a href="../faq.html">FAQ</a></li></ul></li><li class="none"><a href="../thanks.html">Ackknowledgements</a></li><li class="expanded"><a href="../">Project Information</a><ul><li class="none"><a href="../team-list.html">Project Team</a></li><li class="none"><a href="../issue-tracking.html">Issue Tracking</a></li></ul></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="../images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="Getting_Started_Guides_for_Axis2"></a><h2>Getting Started Guides for Axis2</h2><ul>
+ <li><a href="installationguide.html">Installation Guide</a></li>
+ <li><a href="userguide.html">User's Guide</a></li>
+ <li><a href="webadminguide.html">Web Administration Guide </a></li>
+</ul></div><div class="section"><a name="Additional_References"></a><h2>Additional References</h2><ul>
+ <li><a href="http://wiki.apache.org/ws/FrontPage/Axis2" class="externalLink" title="External Link">Axis2 Wiki</a></li>
+ <li><a href="Axis2ArchitectureGuide.html">Architecture Guide</a></li>
+ <li><a href="OMTutorial.html">AXIOM Tutorial</a></li>
+ <li><a href="CodegenToolReference.html">Code Generation Tutorial</a></li>
+ <li><a href="rest-ws.html">REST Support</a></li>
+ <li> <a href="mtom-guide.html">Handling Binary Data with Axis2</a></li>
+ <li> <a href="axis2config.html">Axis2 Configuration Guide</a></li>
+ <li> <a href="migration.html">Migrating from Axis 1.x</a></li>
+ <li> <a href="api/api.html">Online Java Docs</a></li>
+ <li> <a href="adb/adb-howto.html">ADB How-to</a></li>
+ <li> <a href="security-module.html">WS-Security How-to</a></li>
+</ul></div><div class="section"><a name="Other_Tutorials"></a><h2>Other Tutorials</h2><div class="subsection"><a name="Axis2"></a><h3>Axis2</h3><ul>
+ <li><a href="http://www.jaxmagazine.com/itr/online_artikel/psecom,id,747,nodeid,147.html" class="externalLink" title="External Link">Axis2
+ - The Future of Web Services</a>
+ </li>
+ <li>
+ <a href="http://www.developer.com/services/article.php/3525481" class="externalLink" title="External Link">Introducing
+ Axis2</a>
+ </li>
+ <li><a href="http://www.onjava.com/pub/a/onjava/2005/07/27/axis2.html" class="externalLink" title="External Link">Web
+ Services Messaging with Apache Axis2: Concepts and Techniques</a></li>
+ <li><a href="http://developer.com/java/web/article.php/3529321" class="externalLink" title="External Link">Axis2
+ Execution Framework</a>
+ </li>
+ <li><a href="http://jaxmag.com/itr/online_artikel/psecom,id,757,nodeid,147.html" class="externalLink" title="External Link">Axis2
+ Deployment Model</a>
+ </li>
+ <li><a href="http://www.developer.com/open/article.php/3557741" class="externalLink" title="External Link">Undertanding Axis2 Deployment Architecture</a>
+ </li>
+
+</ul></div><div class="subsection"><a name="AXIOM"></a><h3>AXIOM</h3><ul>
+ <li><a href="http://www.jaxmag.com/itr/online_artikel/psecom,id,726,nodeid,147.html" class="externalLink" title="External Link">Fast
+ and Lightweight Object Model for XML </a> - An Introduction to AXIOM, the
+ Open Source API for Working with XML
+ </li>
+ <li><a href="http://www-128.ibm.com/developerworks/library/x-axiom/" class="externalLink" title="External Link">Get
+ the most out of XML processing with AXIOM</a> - Explaining the
+ flexibilities of AXIOM in developerworks.
+ </li>
+</ul></div></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2004-2006, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
Added: webservices/site/trunk/targets/axis2/0_94/Axis2ArchitectureGuide.html
URL: http://svn.apache.org/viewcvs/webservices/site/trunk/targets/axis2/0_94/Axis2ArchitectureGuide.html?rev=366133&view=auto
==============================================================================
--- webservices/site/trunk/targets/axis2/0_94/Axis2ArchitectureGuide.html (added)
+++ webservices/site/trunk/targets/axis2/0_94/Axis2ArchitectureGuide.html Thu Jan 5 01:17:47 2006
@@ -0,0 +1,444 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><title>Axis 2.0 - Axis2 Architecture Guide</title><style type="text/css" media="all">
+ @import url("./style/maven-base.css");
+
+ @import url("./style/maven-theme.css");</style><link rel="stylesheet" href="./style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://www.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://www.apache.org/images/asf-logo.gif"></img></a><a href="http://ws.apache.org/axis2/" id="projectLogo"><img alt="Apache Axis 2.0" src="http://ws.apache.org/axis2/images/axis.jpg"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
+ Last published: 05 January 2006
+ | Doc for 0.94</div><div class="xright"></div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuAxis_2_0"><h5>Axis 2.0</h5><ul><li class="none"><a href="index.html">Home</a></li><li class="expanded"><a href="">Download Axis2</a><ul><li class="none"><a href="download.cgi">Releases</a></li><li class="none"><a href="http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/?root=Apache-SVN" class="externalLink" title="External Link">Source Code</a></li></ul></li><li class="expanded"><a href="">Documentation</a><ul><li class="none"><a href="0_93/index.html">Version 0.93</a></li><li class="none"><a href="0_94/index.html">Version 0.94</a></li></ul></li><li class="expanded"><a href="overview.html">Get Involved</a><ul><li class="none"><a href="svn.html">Checkout the Source</a></li><li class="none"><a href="siteHowTo.html">Build the Site</a></li><li class="none"><a href="guidelines.html">Developer Guidelines</a></li><li cl
ass="none"><a href="refLib.html">Reference Library</a></li><li class="none"><a href="mail-lists.html">Mailing Lists</a></li><li class="none"><a href="faq.html">FAQ</a></li></ul></li><li class="none"><a href="thanks.html">Ackknowledgements</a></li><li class="expanded"><a href="">Project Information</a><ul><li class="none"><a href="team-list.html">Project Team</a></li><li class="none"><a href="issue-tracking.html">Issue Tracking</a></li></ul></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="./images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="Axis2_Architecture_Guide"></a><h2>Axis2 Architecture Guide</h2><div class="subsection"><a name="Contents"></a><h3>Contents</h3><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>
+<br></br>
+</p></div><div class="subsection"><a name="The_Big_Picture"></a><h3>The Big Picture</h3><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></div><div class="subsection"><a name="Requirement_of_Axis2"></a><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" alt=""></img></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></div><div class="subsection"><a name="Axis2__the_Architecture"></a><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" alt=""></img>
+ <map name="Graphic2Map">
+ <area shape="rect" coords="123,31,222,97" href="#bmInfoMod"></area>
+ <area shape="rect" coords="239,62,319,134" href="#bmXML"></area>
+ <area shape="rect" coords="127,112,218,177" href="#bmSOAPPM"></area>
+ <area shape="rect" coords="12,39,89,95" href="#bmDeployment"></area>
+ <area shape="rect" coords="0,108,94,156" href="#bmWSDL"></area>
+ <area shape="rect" coords="350,31,426,86" href="#bmClientAPI"></area>
+ <area shape="rect" coords="350,114,421,164" href="#bmTransports"></area>
+ </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></div><div class="subsection"><a name="Information_Model"></a><h3>Information Model</h3><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" alt=""></img></p><p>This uses UML notations ( A ----<> B means B has 1 or more objects
+of A. A------>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 class="bodyTable"><col width="112"></col><col width="371"></col><col width="103"></col><col width="336"></col><tbody>
+ <tr class="a"><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 class="b"><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 class="a"><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 class="b"><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 class="a"><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></div><div class="subsection"><a name="XML_Processing_Model"></a><h3>XML Processing Model</h3><p>Please refer to the <a href="OMTutorial.html">OM Tutorial</a></p></div><div class="subsection"><a name="SOAP_Processing_Model"></a><h3>SOAP Processing Model</h3><p><img src="images/archi-guide/soap-processing.gif" name="Graphic4" align="bottom" width="755" height="348" border="0" alt=""></img></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" alt=""></img></p></div><div class="subsection"><a name="Axis2_Default_Processing_Model"></a><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></div><div class="subsection"><a name="Processing_an_Incoming_SOAP_Message"></a><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></div><div class="subsection"><a name="Processing_of_the_Outgoing_Message"></a><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></div><div class="subsection"><a name="Extending_SOAP_Processing_Model"></a><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></div><div class="subsection"><a name="Extending_the_SOAP_Processing_Model_with_Handlers"></a><h3>Extending the SOAP Processing Model with Handlers</h3><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></div><div class="subsection"><a name="Extending_the_SOAP_Processing_Model_with_Modules"></a><h3>Extending the SOAP Processing Model with Modules</h3><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></div><div class="subsection"><a name="Deployment"></a><h3>Deployment</h3><p>There deployment Model provides a concrete mechanism to configure Axis2.
+Deployment Model has four entities that provide the configuration.</p></div><div class="subsection"><a name="The__file"></a><h3>The 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></div><div class="subsection"><a name="Service_Archive"></a><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></div><div class="subsection"><a name="Module_Archive"></a><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></div><div class="subsection"><a name="WSDL_and_code_generation"></a><h3>WSDL and code generation</h3><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" alt=""></img></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></div><div class="subsection"><a name="Data_Binding"></a><h3>Data Binding</h3></div><div class="subsection"><a name="Integration_with_the_code_generation_engine"></a><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" alt=""></img></p></div><div class="subsection"><a name="Serialization_and_De-Serialization"></a><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></div><div class="subsection"><a name="Client_API"></a><h3>Client API</h3><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></div><div class="subsection"><a name="One_Way_Messaging_Support"></a><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></div><div class="subsection"><a name="Request_Response_Messaging_Support"></a><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></div><div class="subsection"><a name="Transports"></a><h3>Transports</h3><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></div></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 2004-2006, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file