axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chinth...@apache.org
Subject svn commit: r375935 [1/2] - in /webservices/axis2/trunk/java/xdocs/latest: ./ tools/idea/
Date Wed, 08 Feb 2006 11:33:53 GMT
Author: chinthaka
Date: Wed Feb  8 03:33:41 2006
New Revision: 375935

URL: http://svn.apache.org/viewcvs?rev=375935&view=rev
Log:
updating latest forlder docs

Modified:
    webservices/axis2/trunk/java/xdocs/latest/CodegenToolReference.html
    webservices/axis2/trunk/java/xdocs/latest/CodegenTools-EclipsePlugin.html
    webservices/axis2/trunk/java/xdocs/latest/ServiceArchiveToolReference.html
    webservices/axis2/trunk/java/xdocs/latest/axis2config.html
    webservices/axis2/trunk/java/xdocs/latest/http-transport.html
    webservices/axis2/trunk/java/xdocs/latest/index.html
    webservices/axis2/trunk/java/xdocs/latest/installationguide.html
    webservices/axis2/trunk/java/xdocs/latest/mail-configuration.html
    webservices/axis2/trunk/java/xdocs/latest/mail-transport.html
    webservices/axis2/trunk/java/xdocs/latest/mtom-guide.html
    webservices/axis2/trunk/java/xdocs/latest/rest-ws.html
    webservices/axis2/trunk/java/xdocs/latest/security-module.html
    webservices/axis2/trunk/java/xdocs/latest/tools/idea/Idea_plug-in_userguide.html
    webservices/axis2/trunk/java/xdocs/latest/transport_howto.html
    webservices/axis2/trunk/java/xdocs/latest/userguide.html
    webservices/axis2/trunk/java/xdocs/latest/userguide1.html
    webservices/axis2/trunk/java/xdocs/latest/userguide2.html
    webservices/axis2/trunk/java/xdocs/latest/userguide3.html
    webservices/axis2/trunk/java/xdocs/latest/userguide4.html
    webservices/axis2/trunk/java/xdocs/latest/userguide5.html
    webservices/axis2/trunk/java/xdocs/latest/webadminguide.html

Modified: webservices/axis2/trunk/java/xdocs/latest/CodegenToolReference.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/CodegenToolReference.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/CodegenToolReference.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/CodegenToolReference.html Wed Feb  8 03:33:41 2006
@@ -62,7 +62,7 @@
       <td width="20%">-p &lt;package name&gt;</td>
       <td width="20%">--package</td>
       <td width="60%">The target package name. If omitted, a default package
-        (formed using the target  namespace of the WSDL) will be used.</td>
+        (formed using the target namespace of the WSDL) will be used.</td>
       <td></td>
     </tr>
     <tr>
@@ -192,8 +192,8 @@
     <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>
+        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>
@@ -253,15 +253,15 @@
 &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;
+ 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;
+ wsdlfilename="C:\test\wsdl\CombinedService.wsdl"
+ output="C:\"
+ serverside="true"
+ generateserverxml="true"/&gt;
 &lt;/target&gt;
 &lt;/project&gt;</pre>
 
@@ -714,19 +714,19 @@
 <ul>
   <li>Eclipse reference - <a href="http://www.eclipse.org/">
     http://www.eclipse.org/</a></li>
-  <li>Custom Ant Tasks  - <a
+  <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>
+<p></p>
 
-<p> </p>
+<p></p>
 
-<p> </p>
+<p></p>
 </body>
 </html>

Modified: webservices/axis2/trunk/java/xdocs/latest/CodegenTools-EclipsePlugin.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/CodegenTools-EclipsePlugin.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/CodegenTools-EclipsePlugin.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/CodegenTools-EclipsePlugin.html Wed Feb  8 03:33:41 2006
@@ -41,9 +41,9 @@
 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.1 and upwards. The
-provided screen shots may slightly differ with what the user would actually
-see but the fuctuonality has not been changed.</i></p>
+<p><strong>Note</strong> - This plug-in works on Eclipse version 3.1 and
+upwards. The provided screen shots may slightly differ with what the user
+would actually see but the fuctuonality has not been changed.</p>
 
 <h2>Operation</h2>
 
@@ -56,8 +56,8 @@
 <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><img alt="" src="images/tools/wsdl/toolSelectionpage.jpg" width="557"
+height="501" /></p>
 
 <p>Selecting the generate code from WSDL option leads to the next page. Note
 that the Java-to-WSDL tool is disabled.</p>
@@ -75,9 +75,9 @@
 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><em>Note - The databinding option "xmlbeans" would not work for Eclipse
-version 3.0. This has been a known problem and users are recommended to use
-Eclipse version 3.1 or upwards</em></p>
+<p><strong>Note</strong> - The databinding option "xmlbeans" would not work
+for Eclipse version 3.0. This has been a known problem and users are
+recommended to use Eclipse version 3.1 or upwards</p>
 
 <p><img src="images/tools/wsdl/OptionsPage.jpg" width="518" height="500"
 alt="" /></p>

Modified: webservices/axis2/trunk/java/xdocs/latest/ServiceArchiveToolReference.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/ServiceArchiveToolReference.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/ServiceArchiveToolReference.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/ServiceArchiveToolReference.html Wed Feb  8 03:33:41 2006
@@ -27,41 +27,41 @@
 <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 align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/ServiceWizardSelection.jpg" width="500"
 height="500"></p>
 
 <p>Selecting the wizard and pressing the next button will start the service
 generator wizard. Following is the first wizard page.</p>
 
-<p align="center"><img border="0" src="images/tools/service/ServicePage1.jpg"
+<p align="center"><img alt="" border="0" src="images/tools/service/ServicePage1.jpg"
 width="500" height="500"></p>
 
-<p>Once the class file folder  is given (which should be a folder in the file
+<p>Once the class file folder is given (which should be a folder in the file
 system) the next button will be enabled. </p>
 
 <p>Page 2 of the wizard requires you to locate the wsdl file. Note that the
 WSDL file cannot be skipped in this version of the tool.</p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page2.JPG" width="500" height="500"></p>
 
 <p align="center">Select the service.XML file in the next wizard page</p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page3.JPG" width="500" height="500"></p>
 
 <p>Note that The service XML file can be generated if needed. To proceed to
 the service generation page, check the "generate automatically" checkbox.</p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page3_hl.JPG"></p>
 
 <p>If the automatic mode is not selected, then the wizard will directly jump
 to the library selection page. However if the automatic mode is selected the
 wizard will show the following page.</p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page4_plain.JPG" width="500"
 height="500"></p>
 
@@ -70,21 +70,21 @@
 implementation class, type in the fully qualified class name and hit the load
 button to view the operations.</p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page4_load.JPG"></p>
 
 <p>The loaded operations should be displayed in a table. Once this is
 displayed you can filter the methods by selecting/deselecting the methods
 using the checkbox at each row.</p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page4_table.JPG" width="500"
 height="500"></p>
 
 <p>Further filtering can be achieved by using the "search declared methods"
 only checkbox.</p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page4_search_declared.JPG"></p>
 
 <p>Once the method selection is complete the wizard has enough information to
@@ -94,28 +94,28 @@
 <p>The next step is to add the libraries. The library addition page looks
 like this</p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page5.JPG"></p>
 
 <p>The library name (with full path) can be either typed on the text box or
 browsed for using the browse button.</p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page5_browsed.JPG"></p>
 
 <p>Hit the Add button to add the library to the list. The added libraries
 should be displayed in the list box</p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page5_hl.JPG"></p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page5_added.JPG"></p>
 
 <p>If any library needs to be removed, highlight it in the list and hit
 remove. Click next to proceed to the last page of the wizard</p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page5_remove.JPG"></p>
 
 <p>The last page of the wizard asks for the output location and the output
@@ -123,13 +123,13 @@
 
 <p></p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/service_page6.JPG"></p>
 
 <p>Once all the parameters are filled, hit the finish button to complete the
 wizard and generate the service archive.</p>
 
-<p align="center"><img border="0"
+<p align="center"><img alt="" border="0"
 src="images/tools/service/success_msg.JPG"></p>
 
 <p>If you see the above message, then you've successfully generated the
@@ -138,15 +138,15 @@
 <p>The plugin also adds a help document to the Eclipse help system. You
 should see it if you go to Eclipse help content</p>
 
-<p align="center"><img border="0" src="images/tools/service/help.JPG"></p>
+<p align="center"><img alt="" border="0" src="images/tools/service/help.JPG"></p>
 <hr>
 
-<p> </p>
+<p></p>
 
-<p> </p>
+<p></p>
 
-<p> </p>
+<p></p>
 
-<p> </p>
+<p></p>
 </body>
 </html>

Modified: webservices/axis2/trunk/java/xdocs/latest/axis2config.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/axis2config.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/axis2config.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/axis2config.html Wed Feb  8 03:33:41 2006
@@ -18,7 +18,8 @@
   (module.xml)</a></li>
 </ul>
 
-<h2><a name="Global_Configuration">Global Configuration</a></h2>
+<a name="Global_Configuration"/>
+<h2>Global Configuration</h2>
 <ul>
   <li>Writing axis2.xml</li>
 </ul>
@@ -37,20 +38,22 @@
   <li>Listeners (Observers)</li>
 </ul>
 
-<p><b>Parameter </b> <br>
+<p><b>Parameter </b> <br/>
 In axis2 a parameter is nothing but name value pair, each and every top level
 parameter available in the axis2.xml (direct sub elements of root element)
 will be transformed into properties in AxisConfiguration. Therefore the top
 level parameters in configuration document can be accessed via
 AxisConfiguration in the running system. The correct way of defining a
-parameter looks like what is shown below; <source></p>
+parameter looks like what is shown below;</p>
+<source>
 <pre> 
   &lt;parameter name="name of the parameter" &gt;parameter value &lt;/parameter&gt;</pre>
 </source>
-<p><b>Transport Receiver</b><br>
+
+<p><b>Transport Receiver</b><br/>
 Depending on the underline transport that axis going to be run , need to have
 different transport receivers so the way of adding them to the system can be
-done as follows; <source></p>
+done as follows; <p><source>
 <pre> 
 &lt;transportReceiver name="http" class="org.apache.axis2.transport.http.SimpleHTTPServer"&gt;
         &lt;parameter name="port" &gt;6060&lt;/parameter&gt;
@@ -66,12 +69,12 @@
 any, then those parameters can be accessed via the corresponding transport
 receiver.
 
-<p><b>Transport Senders</b><br>
+<p><b>Transport Senders</b><br/>
 As same as transport receivers it is possible to register transport senders
 in the system, and latter at the run time those senders can be used to send
 the messages. As an example consider Axis2 running under tomcat, then axis
 can use TCP transport senders to send message rather than HTTP. The way of
-specifying transport senders is as follows: <source></p>
+specifying transport senders is as follows: <p><source>
 <pre> 
 &lt;transportSender name="http" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"&gt;
         &lt;parameter name="PROTOCOL" locked="xsd:false"&gt;HTTP/1.0&lt;/parameter&gt;
@@ -83,9 +86,9 @@
 more parameters, and if there is any then it can be accessed via
 corresponding transport sender.
 
-<p><b>Phase Order</b><br>
+<p><b>Phase Order</b><br/>
 The specifying order of phases in execution chain has to be done using phase
-order element and it will be look like below; <source></p>
+order element and it will be look like below; <p><source>
 <pre>&lt;phaseOrder type="inflow"&gt;
          &lt;phase name="TransportIn"/&gt;
          .
@@ -156,9 +159,9 @@
 
 <p>In addition to that only child element allowed inside pahseOrder is phase
 element, which represents available phases in the execution chain. The way of
-specifying phase inside phaseOrder has to be done as follows; <source></p>
+specifying phase inside phaseOrder has to be done as follows; <p><source>
 <pre> &lt;phase name="TransportIn"/&gt;</pre>
-</source>name: Name of the phase. <br>
+</source>name: Name of the phase. <br/>
 There are number of things that one has to keep in mind when changing
 pahseOrder,
 <ul>
@@ -171,9 +174,9 @@
 <ol>
   If you closely look at the default axis2.xml can clearly identify that.</ol>
 
-<p><b>Module References</b><br>
+<p><b>Module References</b><br/>
 If you want to engage a module system wide you can do it by adding top level
-module element in axis2.xml.  It should be look like following: <source></p>
+module element in axis2.xml.  It should be look like following: <p><source>
 <pre>&lt;module ref="addressing"/&gt;  </pre>
 </source>ref: the module name which is going to be engage, system wide.
 Listeners (Observers) In Axis2 AxisConfiguration is observable so that one
@@ -195,8 +198,8 @@
 be note that the implementation class should implement AxisObserver
 interface, and the class has to be available in the classpath.
 
-<h2><font><a name="Service_Configuration">Service
-Configuration</a></font></h2>
+<a name="Service_Configuration"/>
+<h2><font>Service Configuration</font></h2>
 <ul>
   <li><font>Writing services.xml</font></li>
 </ul>
@@ -204,8 +207,10 @@
 <p><font>The description of service is specified using services.xml, each
 service archive file need to have services.xml in order to be a valid
 service. And which has to be available in META-INF directory of the archive
-file. <br>
-A very simple services.xml is shown below: </font><font><source></font></p>
+file. <br/>
+A very simple services.xml is shown below: </font>
+    </p>
+    <source>
 <pre><font>&lt;service &gt;
     &lt;description&gt; The description of the service  &lt;/description&gt;
 
@@ -216,69 +221,70 @@
         &lt;messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/&gt;
     &lt;/operation&gt;
   &lt;/service&gt;
-</font><font></source></font></pre>
+</font></pre></source>
+
 <font>service name: the service name will be the name of the archive file.
-<br>
+<br/>
 description: This is an optional element if you want to display any
 description about the service via Axis2 web-admin module then the description
 can be specified here.</font>
 
-<p><b>Parameter:</b><br>
+<p><b>Parameter:</b><br/>
 services.xml can have any number of top level parameters and all the
 specified parameters will be transformed into service properties in
 corresponding ServiceDescrption. There is a compulsory parameter in a
 services.xml called ServiceClass which specify the java class which really
 does the job and the class will be loaded by MessageReceiver.</p>
 
-<p><b>Handler</b><br>
+<p><b>Handler</b><br/>
 Handler element consists of compulsory and optional attribute and the way of
-defining a handler will be look like follows; <source></p>
+defining a handler will be look like follows; <p><source>
 <pre>&lt;handler name="handler1" class="handlerClass "&gt;
             &lt;order phase="userphase1" /&gt;
  &lt;/handler&gt;
-</source></pre>
-<b><i>Compulsory attributes</i></b> <br>
-name: name of the handler<br>
-nlass: handler implementation class<br>
+</pre></source>
+<b><i>Compulsory attributes</i></b> <br/>
+name: name of the handler<br/>
+nlass: handler implementation class<br/>
 phase: name of the phase that the handler should stay in the execution chain
-<br>
-<br>
-<i><b>Optional attributes :</b></i><br>
-phaseLast: to indicate the handler is last handler of the phase<br>
-phaseFirst: to indicate the handler is first handler of the phase.<br>
+<br/>
+<br/>
+<i><b>Optional attributes :</b></i><br/>
+phaseLast: to indicate the handler is last handler of the phase<br/>
+phaseFirst: to indicate the handler is first handler of the phase.<br/>
 before : the handler should be invoked before the handler specified by before
-handler<br>
+handler<br/>
 after:  the handler should be invoked after the handler specified by after
-handler<br>
+handler<br/>
 
 
-<p><b>Operations</b><br>
+<p><b>Operations</b><br/>
 All the operations you are going to exposeby the service has to be indicated
 in the services.xml and the correct way of specifying that should be as
-follows: <source></p>
+follows: <p><source>
 <pre>    &lt;operation name="echoString"&gt;
         &lt;module ref=" a module name "/&gt;
         &lt;messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/&gt;
     &lt;/operation&gt;
-</source></pre>
+</pre></source>
 Only compulsory attribute here is name, which represent the operation name
 that is going to be exposed. Any operation can contains module references,
 any number of parameters. The most interesting is that one can register
 custom message receiver per operation, then the registered message receiver
 will be the message receiver for the corresponding operation. If one does not
 specify the message receiver then the default message receiver will do the
-job. <br>
-
+job. <br/>
 
-<h2><a name="Module_Configuration">Module Configuration</a></h2>
+<a name="Module_Configuration"/>
+<h2>Module Configuration</h2>
 <ul>
   <li>Writing module.xml</li>
 </ul>
 
 <p>The description of module is specified using module.xml, each module
 archive file need to have module.xml in order to be a valid module. And which
-has to be available in META-INF directory of the archive file. <br>
-A very simple module.xml is shown below: <source></p>
+has to be available in META-INF directory of the archive file. <br/>
+A very simple module.xml is shown below: <p><source>
 <pre>&lt;module name="module1" class="org.apache.module.Module1Impl"&gt;
     &lt;inflow&gt;
         .
@@ -304,9 +310,9 @@
         &lt;parameter name="para1" locked="xsd:true"&gt;10&lt;/parameter&gt;
     &lt;/operation&gt;
 &lt;/module&gt;
-</source></pre>
+</pre></source>
 name: This is a compulsory attribute and which indicates the name of the
-module <br>
+module <br/>
 class: This is an optional attribute which indicate module implementation
 class, a module may or may not contain module implementation class since the
 module can also be a collection of handlers. If a module contains an
@@ -317,16 +323,16 @@
 listed parameters in the module.xml will be transformed into corresponding
 ModuleDescription of the module.</p>
 
-<p><b>Flow :</b><br>
+<p><b>Flow :</b><br/>
 It is possible to add handlers into a flow directly form services.xml rather
 than engaging a modules and the way of doing that is through flow elements.
 It is possible to add any number of handlers into a flow and those handlers
 will be available in corresponding operations flows in the service (inflow
 consist of two parts, one part is up to post dispatch phase and other part is
-consisting of operation handlers) <br>
+consisting of operation handlers) <br/>
 There are four types of valid flows that can be available in services.xml,
 and the adding the handles into them can be done by following the above
-procedure. <br>
+procedure. <br/>
 Valid flows:</p>
 <ul>
   <li>Inflow</li>
@@ -338,6 +344,6 @@
 <p><b>operations</b> If a module wants to add an operation when it is engaged
 into a service it can be done by adding operation tag in module.xml and the
 way of specifying the operation is same as operation in services.xml.</p>
-<br>
+<br/>
 </body>
 </html>

Modified: webservices/axis2/trunk/java/xdocs/latest/http-transport.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/http-transport.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/http-transport.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/http-transport.html Wed Feb  8 03:33:41 2006
@@ -6,7 +6,8 @@
 </head>
 
 <body lang="en">
-<h1><a name="#configTransport">HTTP transports</a></h1>
+<a name="configTransport"/>
+<h1>HTTP transports</h1>
 
 <h3>CommonsHTTPTransportSender</h3>
 
@@ -21,7 +22,7 @@
 
 <p>&lt;transportSender/&gt; element is used to define transport senders in
 the axis2.xml as follows:</p>
-<pre><code>&lt;transportSender name="http" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"&gt;<br>        &lt;parameter name="PROTOCOL" locked="false"&gt;HTTP/1.1&lt;/parameter&gt;<br>        &lt;parameter name="Transfer-Encoding"&gt;chunked&lt;/parameter&gt;<br>&lt;/transportSender&gt;<br></code></pre>
+<pre>&lt;transportSender name="http" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"&gt;<br/>        &lt;parameter name="PROTOCOL" locked="false"&gt;HTTP/1.1&lt;/parameter&gt;<br/>        &lt;parameter name="Transfer-Encoding"&gt;chunked&lt;/parameter&gt;<br/>&lt;/transportSender&gt;<br/></pre>
 
 <p>Above code snippet shows the complete configuration of the transport
 sender. &lt;parameter/&gt; element introduces the additional parameters that
@@ -38,12 +39,12 @@
 <h4>HTTPS support</h4>
 It should be noted that CommonsHTTPTransportSender can be used to communicate
 over https. <code></code>
-<pre>&lt;transportSender name="<b>https</b>" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"&gt;<br>        &lt;parameter name="PROTOCOL" locked="false"&gt;HTTP/1.1&lt;/parameter&gt;<br>        &lt;parameter name="Transfer-Encoding"&gt;chunked&lt;/parameter&gt;<br>&lt;/transportSender&gt;<br></pre>
+<pre>&lt;transportSender name="<b>https</b>" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"&gt;<br/>        &lt;parameter name="PROTOCOL" locked="false"&gt;HTTP/1.1&lt;/parameter&gt;<br/>        &lt;parameter name="Transfer-Encoding"&gt;chunked&lt;/parameter&gt;<br/>&lt;/transportSender&gt;<br/></pre>
 Please note that https works only when the server does not expect to
 authenticate the clients and where the server has the clients' public keys in
 its trust store.
 
-<h2>Timeout Configuraiton</h2>
+<h2>Timeout Configuration</h2>
 
 <p>There are two timeout exists in transport level. They are called, Socket
 timeout and Connection timeout. This can be configured in deployment time or
@@ -55,7 +56,7 @@
 
 <p>For Connection timeout:</p>
 <pre> &lt;parameter name="CONNECTION_TIMEOUT" locked="false"&gt;some_int_value&lt;/parameter&gt;</pre>
-<br>
+<br/>
 In runtime it's set as follows in the Stub. <source>
 <pre>...
 Options options = new Options();
@@ -65,6 +66,18 @@
 </source>
 <p></p>
 
+<h2>HTTP Version Configuration</h2>
+<p>The default HTTP version is 1.1. There are two methods in which user can change HTTP version to 1.0</p> 
+<ol>
+<li>By defining version in Axis2.xml as shown below.</li>
+<pre> &lt;parameter name="PROTOCOL" locked="false"&gt;HTTP/1.0&lt;/parameter&gt;</pre>
+
+<li>Or user can change version at runtime by doing the following</li>
+<pre>...
+options.setProperty(org.apache.axis2.context.MessageContextConstants.HTTP_PROTOCOL_VERSION,org.apache.axis2.transport.http.HTTPConstants.HEADER_PROTOCOL_10);
+...</pre>
+</ol>
+
 <h2>Proxy and NTLM Authentication</h2>
 
 <p>HttpClient support "Basic, Digest and NTLM" authentication schemes. These
@@ -76,7 +89,7 @@
 <pre>&lt;transportSender name="<b>http</b>" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"&gt;
         &lt;parameter name="PROTOCOL" locked="false"&gt;HTTP/1.1&lt;/parameter&gt;
         &lt;parameter name="PROXY" proxy_host="proxy_host_name" proxy_port="proxy_host_port" locked="true&gt;userName:domain:passWord&lt;/parameter&gt;
-&lt;/transportSender&gt;<br></pre>
+&lt;/transportSender&gt;<br/></pre>
 
 <p>For a particular proxy, if authentication is not available fill
 "userName:domain:passWord"as "anonymous:anonymous:anonymous".</p>

Modified: webservices/axis2/trunk/java/xdocs/latest/index.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/index.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/index.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/index.html Wed Feb  8 03:33:41 2006
@@ -22,7 +22,7 @@
     Eclipse Plug-in</a></li>
   <li><a href="ServiceArchiveToolReference.html">Service Archive Wizard -
     Eclipse Plug-in</a></li>
-  <li><a href="tools\idea\Idea_plug-in_userguide.html">IntelliJ IDEA
+  <li><a href="tools/idea/Idea_plug-in_userguide.html">IntelliJ IDEA
     Plug-ins</a></li>
 </ul>
 

Modified: webservices/axis2/trunk/java/xdocs/latest/installationguide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/installationguide.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/installationguide.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/installationguide.html Wed Feb  8 03:33:41 2006
@@ -1,309 +1,336 @@
-<!-- saved from url=(0022)http://internet.e-mail -->
-<html>
-<head>
-  <meta http-equiv="content-type" content="">
-  <title>Axis2 Installation Guide</title>
-  <style type="text/css">
-<!--
-.style1 {
-	font-family: "Courier New", Courier, mono;
-	font-size: 14px;
-	font-style: italic;
-}
-.style2 {font-family: Arial, Helvetica, sans-serif}
--->
-  </style>
-</head>
-
-<body lang="en">
-<h1 align="center">Axis2 Installation Guide</h1>
-
-<p><i>Version 0.94</i></p>
-<i>Feedback: <a
-href="mailto:axis-dev@ws.apache.org">axis-dev@ws.apache.org</a></i>
-
-<h3>Contents</h3>
-<ul>
-  <li><a href="#Download_Axis2">Download Axis2</a></li>
-  <li><p><a href="#requirements">System Requirements</a></p>
-  </li>
-  <li><a href="#_Toc96698083">Setting up the Environment and tools</a>
-    <ul>
-      <li><p><a href="#_Toc96698084">Maven</a></p>
-      </li>
-      <li><a href="#_Toc96698085">The Axis2 source distribution</a></li>
-    </ul>
-  </li>
-  <li><p><a href="#_Toc96698086">Installing Axis2 in a Servlet
-    container</a></p>
-    <ul>
-      <li><a href="#upload">Uploading services</a></li>
-    </ul>
-  </li>
-</ul>
-
-<h3><a name="Download_Axis2">Download Axis2</a></h3>
-
-<p>Axis2 is distributed in several convenient distribution packages and can be installed either as a
-standalone server or as part of a J2EE compliant servlet container. Axis2 is
-distributed under the Apache License, version 2.0. You can download Axis2 <a href="http://ws.apache.org/axis2/download.cgi">here</a>. Latest release of Axis2 is version 0.94. </p>
-<table width="940" border="1" cellpadding="1">
-  <tr>
-    <th width="83" scope="col">Distribution Name</th>
-    <th width="633" scope="col">Description</th>
-    <th width="202" scope="col">Items</th>
-  </tr>
-  <tr>
-    <td>Minimal Distribution - Binary </td>
-    <td>This distribution is aimed at advanced users who will be embedding Axis2. It will contain the minimal runtime required to act as a Web Service client and/or a server (axis2-core-0.94.jar will contain compiled versions of common, xml, wsdl and core modules.) </td>
-    <td><ul>
-      <li>axis2-core-0.94.jar, axis2-adb-0.94.jar</li>
-      <li>third party distributable libraries</li>
-      <li>README.TXT and release-notes.html </li>
-    </ul></td>
-  </tr>
-  <tr>
-    <td>Minimal Distribution - Source </td>
-    <td background="#_Toc96698083"><p>This will contain the sources of Axis2 minimal distribution. One can generate a binary distribution from this by typing  <span class="style1">$maven dist-min-bin. </span>(<a href="#_Toc96698083">Set up Axis2 environment</a> before running this command) </p></td>
-    <td><ul>
-      <li>sources of Axis2 common, xml, wsdl, adb and core modules </li>
-      <li>README.TXT and release-notes.html</li>
-    </ul></td>
-  </tr>
-  <tr>
-    <td>Standard Distribution - Binary </td>
-    <td>This is the complete version of Axis2 and will contain useful samples as well. Useful for some one to get familiar with Axis2. (Since WS-Addressing implementation module is engaged in to Axis2, by default, this distribution will contain addressing.mar. But  the other modules that are being developed within Axis2 will not be included here and are available to be downloaded separately from <a href="http://ws.apache.org/axis2/modules/index.html">here</a>.)</td>
-    <td><ul>
-      <li>all the content of minimal-binary distribution</li>
-      <li>Contents of codegen and DOOM modules</li>
-      <li>Samples</li>
-      <li>addressing.mar</li>
-    </ul></td>
-  </tr>
-  <tr>
-    <td>Standard Distribution - Source </td>
-    <td>This will contain the sources of Axis2 standard distribution. One can generate a binary distribution from this by typing <span class="style1">$maven dist-standard-bin. </span>(<a href="#_Toc96698083">Set up Axis2 environment</a> before running this command) </td>
-    <td><ul>
-      <li>all the content of minimal-source distribution</li>
-      <li>Contents of codegen and DOOM modules</li>
-      <li>Samples</li>
-      </ul></td>
-  </tr>
-  <tr>
-    <td>WAR (Web Archive) Distribution </td>
-    <td>This will be the web application of Axis2 which can be deployed in most of the servlet containers. </td>
-    <td><ul>
-      <li>
-        all the contents of the minimal distribution 
-      </li>
-      <li>
-        Admin web app
-      </li>
-    </ul></td>
-  </tr>
-  <tr>
-    <td>Documents Distribution </td>
-    <td>This will contain all the documentation in one package.</td>
-    <td><ul>
-      <li>xdocs</li>
-      <li>javadocs </li>
-    </ul></td>
-  </tr>
-  <tr>
-    <td>Plugin Distribution </td>
-    <td>This will contain the plugins that are created for Eclipse and IDEA.</td>
-    <td><ul>
-      <li>Intellij IDEA plugins</li>
-      <li>Eclipse plugins</li>
-    </ul></td>
-  </tr>
-</table>
-<h3><a name="requirements">System Requirements</a></h3>
-
-<table border="2">
-  <caption></caption>
-  <tbody>
-    <tr>
-      <td>Java Runtime
-
-        <p>Environment</p>
-      </td>
-      <td>1.4 (It has not been fully tested on the latest JRE 1.5)
-
-        <p>For instructions on setting up the JRE in different operating
-        systems, visit <a
-        href="http://java.sun.com/">http://java.sun.com</a></p>
-      </td>
-    </tr>
-    <tr>
-      <td>Maven</td>
-      <td>1.0.2 or higher (<a href="http://maven.apache.org/">download</a>)
-
-        <p>Required only for building Axis2 from source distribution</p>
-      </td>
-    </tr>
-    <tr>
-      <td>Memory</td>
-      <td>No minimum requirement</td>
-    </tr>
-    <tr>
-      <td>Disk</td>
-      <td>No minimum requirement.
-
-        <p>Approximately 20 MB will be used for war distribution</p>
-      </td>
-    </tr>
-    <tr>
-      <td>Operating system</td>
-      <td>Tested on Windows XP, Mac OS X, Fedora core, Ubuntu, Gentoo</td>
-    </tr>
-  </tbody>
-</table>
-
-<p></p>
-
-<p>All the required jars are shipped with the binary distribution.</p>
-
-<p>Running the Maven build will automatically download the required jars when
-using source distribution.</p>
-
-<h3><a name="_Toc96698083"></a>Setting up the Environment and Tools</h3>
-
-<h4><a name="_Toc96698084" id="_Toc96698084"></a>Maven</h4>
-
-<p>The Axis2 build is based on <a href="http://maven.apache.org/">Maven </a>.
-Hence the only prerequisite to build Axis2 from source distribution is to
-have Maven installed. Extensive instruction guides are available at the Maven
-site.This guide however contains the easiest path for quick environment
-setting. Advanced users who wish to know more about Maven can visit <a
-href="http://maven.apache.org/start/index.html">here </a>.</p>
-<ul>
-<li>Windows</li>
-<ol>
-  <li>Download and run the Windows installer package</li>
-  <li>Set the 'Environment Variables' ( create system variable MAVEN_HOME and
-    edit path. eg: "C:\Program Files\Apache Software Foundation\maven-2.0.1";
-    path %MAVEN_HOME%\bin)</li>
-  <li>Make sure that system variable JAVA_HOME is set to the location of your
-    JDK, eg. C:\Program Files\Java\jdk1.5.0_02</li>
-  <li>Run maven --version to verify that it is correctly installed.</li>
-</ol>
-
-
-<p align="center"><img alt="clip_image002 (15K)"
-src="images/clip_image002.jpg" height="211" width="477"></p>
-
-<li>Unix based OS (Linux etc)</li>
-
-<p>The tar ball or the zip archive is the best option. Once the archive is
-downloaded expand it to a directory of choice and set the environment
-variable MAVEN_HOME and add MAVEN_HOME/bin to the path as well. More
-instructions for installing Maven in Unix based operating systems can be
-found <a href="http://maven.apache.org/start/install.html">here </a>.</p>
-
-</ul>
-<p>Once maven is properly installed you can start building Axis2.</p>
-
-<h4><a name="_Toc96698085"></a>The Axis2 source distribution</h4>
-
-<p>The <a href="http://ws.apache.org/axis2/download.cgi">source distribution </a> is available as a
-zipped archive. All the necessary build scripts are included with the source
-distribution. Once the source archive is expanded into a directory of choice,
-moving to the particular directory and running maven command will build the
-Axis2 jar file.</p>
-
-<p align="center"><img alt="clip_image004 (43K)" src="images/maven.jpg"
-height="248" width="668"></p>
-
-<p>Once the command completes, the binaries (jar files in this case) can be
-found at a newly created "target" directory.</p>
-
-<p><strong>Note: For the first Maven build (if the maven repository is not
-built first) it will take a while since required jars need to be downloaded.
-However this is a once only process and will not affect any successive
-builds.</strong></p>
-
-<p><strong></strong>The default maven build will however build only the Axis2
-jar file. To obtain a WAR (Web Archive), "maven war" command should be
-issued. This will create a complete WAR with the name axis2.war inside the
-target directory.</p>
-
-<p>Once this build step is complete, the binaries are ready to be
-deployed.</p>
-
-<h3><a name="_Toc96698086"></a>Installing Axis2 in a Servlet container</h3>
-<ol>
-  <li>Download Axis2 war file</li>
-  <li>Drop the war in the webapps folder. Most servlet containers will
-    automatically install war. (some servlet containers may require a restart
-    in order to capture the new web application. Refer your servlet container
-    documentation for more information about this.)</li>
-  <li>Once the WAR is successfully installed, test it by pointing the web
-    browser to the <strong>http:// &lt;host :port&gt;/ axis2. </strong>It
-    should produce the following page.</li>
-
-  <p align="center"><strong><img src="images/clip_image006.jpg"></strong></p>
-
-  <p></p>
-  <li>Use validate link to ensure that everything is fine and smooth. If the
-    validation fails then the war has failed to install properly or some
-    essential jars are missing. At such a situation the documentation of the
-    particular servlet container should be consulted to find the problem. The
-    following page is a successful validation. Note the statement core Axis2
-    libraries are present.
-    <p></p>
-  </li>
-
-  <p align="center"><strong><img src="images/happyaxis.jpg"></strong></p>
-</ol>
-
-<p></p>
-
-<h4><a name="upload">Uploading services</a></h4>
-<ol>
-  <p>The Axis2 web application also provides an interface to upload services.
-  Once a service is created according to the service specification as
-  described in userguide that jar file can be uploaded using the upload
-  page.</p>
-
-  <p align="center"><strong><img src="images/clip_image010.jpg"
-  alt=""></strong></p>
-
-  <p>The uploaded jar files will be stored in the default service directory.
-  For Axis2 this will be the &lt;webapps&gt;/axis2/WEB-INF/services
-  directory. Once a service is uploaded it will be installed instantly.</p>
-
-  <p>Since Axis2 supports hot deployment one can drop the service jar
-  directly through the file system to the above mentioned services
-  directory.It will also cause the service to be automatically installed
-  without the container being restarted.</p>
-
-  <p>Use the <i>available services link</i> to check the successful
-  installation of a service. The services and the operations of successfully
-  installed services will be displayed in the available services page.</p>
-
-  <p align="center"><img src="images/clip_image012.jpg"
-  alt=""></p>
-
-  <p></p>
-
-  <p>If the service has deployment time error it will list those services
-  as faulty services. If you click on the link you can see the your deployment
-  fault error message(s).</p>
-
-  <p align="center"><img src="images/faultservice.jpg"
-  alt=""></p>
-
-  <p>Deployment time error message</p>
-
-  <p align="center"><strong><img src="images/faultmsg.jpg"
-  alt=""></strong></p>
-
-  <p>  </p>
-
-  <p>Axis2 Administration is all about configuring Axis2 at the run time and
-  the configuration will be transient. More descriptions are available in <a
-  href="webadminguide.html">Axis2 Web Administration Guide</a></p>
-</ol>
-</body>
-</html>
+<html>
+<head>
+  <meta http-equiv="content-type" content="">
+  <title>Axis2 Installation Guide</title>
+  <style type="text/css">
+  </style>
+</head>
+
+<body lang="en">
+<h1 align="center">Axis2 Installation Guide</h1>
+
+<p><i>Version 0.94</i></p>
+<i>Feedback: <a
+href="mailto:axis-dev@ws.apache.org">axis-dev@ws.apache.org</a></i>
+
+<h3>Contents</h3>
+<ul>
+  <li><a href="#Download_Axis2">Download Axis2</a></li>
+  <li><p><a href="#requirements">System Requirements</a></p>
+  </li>
+  <li><a href="#_Toc96698083">Setting up the Environment and tools</a>
+    <ul>
+      <li><p><a href="#maven">Maven</a></p>
+      </li>
+      <li><a href="#_Toc96698085">The Axis2 source distribution</a></li>
+    </ul>
+  </li>
+  <li><p><a href="#_Toc96698086">Installing Axis2 in a Servlet
+    container</a></p>
+    <ul>
+      <li><a href="#upload">Uploading services</a></li>
+    </ul>
+  </li>
+</ul>
+<a name="Download_Axis2"></a>
+<h3>Download Axis2</h3>
+
+<p>Axis2 is distributed in several convenient distribution packages and can
+be installed either as a standalone server or as part of a J2EE compliant
+servlet container. Axis2 is distributed under the Apache License, version
+2.0. You can download Axis2 <a
+href="http://ws.apache.org/axis2/download.cgi">here</a>. Latest release of
+Axis2 is version 0.94.</p>
+
+<table width="940" border="1" cellpadding="1">
+  <tbody>
+    <tr>
+      <th width="83" scope="col">Distribution Name</th>
+      <th width="633" scope="col">Description</th>
+      <th width="202" scope="col">Items</th>
+    </tr>
+    <tr>
+      <td>Minimal Distribution - Binary</td>
+      <td>This distribution is aimed at advanced users who will be embedding
+        Axis2. It will contain the minimal runtime required to act as a Web
+        Service client and/or a server (axis2-core-0.94.jar will contain
+        compiled versions of common, xml, wsdl and core modules.)</td>
+      <td><ul>
+          <li>axis2-core-0.94.jar, axis2-adb-0.94.jar</li>
+          <li>third party distributable libraries</li>
+          <li>README.TXT and release-notes.html</li>
+        </ul>
+      </td>
+    </tr>
+    <tr>
+      <td>Minimal Distribution - Source</td>
+      <td background="#_Toc96698083"><p>This will contain the sources of
+        Axis2 minimal distribution. One can generate a binary distribution
+        from this by typing  <span class="style1">$maven dist-min-bin.
+        </span>(<a href="#_Toc96698083">Set up Axis2 environment</a> before
+        running this command)</p>
+      </td>
+      <td><ul>
+          <li>sources of Axis2 common, xml, wsdl, adb and core modules</li>
+          <li>README.TXT and release-notes.html</li>
+        </ul>
+      </td>
+    </tr>
+    <tr>
+      <td>Standard Distribution - Binary</td>
+      <td>This is the complete version of Axis2 and will contain useful
+        samples as well. Useful for some one to get familiar with Axis2.
+        (Since WS-Addressing implementation module is engaged in to Axis2, by
+        default, this distribution will contain addressing.mar. But  the
+        other modules that are being developed within Axis2 will not be
+        included here and are available to be downloaded separately from <a
+        href="http://ws.apache.org/axis2/modules/index.html">here</a>.)</td>
+      <td><ul>
+          <li>all the content of minimal-binary distribution</li>
+          <li>Contents of codegen and DOOM modules</li>
+          <li>Samples</li>
+          <li>addressing.mar</li>
+        </ul>
+      </td>
+    </tr>
+    <tr>
+      <td>Standard Distribution - Source</td>
+      <td>This will contain the sources of Axis2 standard distribution. One
+        can generate a binary distribution from this by typing <span
+        class="style1">$maven dist-standard-bin. </span>(<a
+        href="#_Toc96698083">Set up Axis2 environment</a> before running this
+        command)</td>
+      <td><ul>
+          <li>all the content of minimal-source distribution</li>
+          <li>Contents of codegen and DOOM modules</li>
+          <li>Samples</li>
+        </ul>
+      </td>
+    </tr>
+    <tr>
+      <td>WAR (Web Archive) Distribution</td>
+      <td>This will be the web application of Axis2 which can be deployed in
+        most of the servlet containers.</td>
+      <td><ul>
+          <li>all the contents of the minimal distribution</li>
+          <li>Admin web app</li>
+        </ul>
+      </td>
+    </tr>
+    <tr>
+      <td>Documents Distribution</td>
+      <td>This will contain all the documentation in one package.</td>
+      <td><ul>
+          <li>xdocs</li>
+          <li>javadocs</li>
+        </ul>
+      </td>
+    </tr>
+    <tr>
+      <td>Plugin Distribution</td>
+      <td>This will contain the plugins that are created for Eclipse and
+      IDEA.</td>
+      <td><ul>
+          <li>Intellij IDEA plugins</li>
+          <li>Eclipse plugins</li>
+        </ul>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<a name="requirements"></a>
+<h3>System Requirements</h3>
+
+<table border="2">
+  <caption></caption>
+  <tbody>
+    <tr>
+      <td>Java Runtime
+
+        <p>Environment</p>
+      </td>
+      <td>1.4 (It has not been fully tested on the latest JRE 1.5)
+
+        <p>For instructions on setting up the JRE in different operating
+        systems, visit <a
+        href="http://java.sun.com/">http://java.sun.com</a></p>
+      </td>
+    </tr>
+    <tr>
+      <td>Maven</td>
+      <td>1.0.2 or higher in Maven 1.x series (<a
+        href="http://maven.apache.org/">download</a>). <strong>Please
+        download maven 1.x version. Axis2 is not compatible with maven2
+        yet.</strong>
+
+        <p>Required only for building Axis2 from source distribution</p>
+      </td>
+    </tr>
+    <tr>
+      <td>Memory</td>
+      <td>No minimum requirement</td>
+    </tr>
+    <tr>
+      <td>Disk</td>
+      <td>No minimum requirement.
+
+        <p>Approximately 20 MB will be used for war distribution</p>
+      </td>
+    </tr>
+    <tr>
+      <td>Operating system</td>
+      <td>Tested on Windows XP, Linux, Mac OS X, Fedora core, Ubuntu,
+      Gentoo</td>
+    </tr>
+  </tbody>
+</table>
+
+
+<p>All the required jars are shipped with the binary distribution.</p>
+
+<p>Running the Maven build will automatically download the required jars when
+using source distribution.</p>
+<a name="_Toc96698083"></a>
+<h3>Setting up the Environment and Tools</h3>
+<a name="maven"></a>
+<h4>Maven</h4>
+
+<p>The Axis2 build is based on</p>
+<a href="http://maven.apache.org/maven-1.x/">Maven </a>. Hence the only
+prerequisite to build Axis2 from source distribution is to have Maven
+installed. Extensive instruction guides are available at the Maven site.This
+guide however contains the easiest path for quick environment setting.
+Advanced users who wish to know more about Maven can visit <a
+href="http://maven.apache.org/start/index.html">here </a>.
+<ul>
+  <li>Windows</li>
+</ul>
+<ol>
+  <li>Download and run the Windows installer package</li>
+  <li>Set the 'Environment Variables' ( create system variable MAVEN_HOME and
+    edit path. eg: "C:\Program Files\Apache Software Foundation\maven-1.0.2";
+    path %MAVEN_HOME%\bin)</li>
+  <li>Make sure that system variable JAVA_HOME is set to the location of your
+    JDK, eg. C:\Program Files\Java\jdk1.5.0_02</li>
+  <li>Run maven --version to verify that it is correctly installed.</li>
+</ol>
+
+<p align="center"><img alt="clip_image002 (15K)"
+src="images/clip_image002.jpg" height="211" width="477"></p>
+<ul>
+  <li>Unix based OS (Linux etc)</li>
+</ul>
+
+<p>The tar ball or the zip archive is the best option. Once the archive is
+downloaded expand it to a directory of choice and set the environment
+variable MAVEN_HOME and add MAVEN_HOME/bin to the path as well. More
+instructions for installing Maven in Unix based operating systems can be
+found <a href="http://maven.apache.org/start/install.html">here </a>.</p>
+
+<p>Once maven is properly installed you can start building Axis2.</p>
+<a name="_Toc96698085"></a>
+
+<h4>The Axis2 source distribution</h4>
+
+<p>The <a href="http://ws.apache.org/axis2/download.cgi">source distribution
+</a> is available as a zipped archive. All the necessary build scripts are
+included with the source distribution. Once the source archive is expanded
+into a directory of choice, moving to the particular directory and running
+maven command will build the Axis2 jar file.</p>
+
+<p align="center"><img alt="clip_image004 (43K)" src="images/maven.jpg"
+height="248" width="668"></p>
+
+<p>Once the command completes, the binaries (jar files in this case) can be
+found at a newly created "target" directory.</p>
+
+<p><strong>Note: For the first Maven build (if the maven repository is not
+built first) it will take a while since required jars need to be downloaded.
+However this is a once only process and will not affect any successive
+builds.</strong></p>
+
+<p><strong></strong>The default maven build will however build only the Axis2
+jar file. To obtain a WAR (Web Archive), "maven war" command should be
+issued. This will create a complete WAR with the name axis2.war inside the
+target directory.</p>
+
+<p>Once this build step is complete, the binaries are ready to be
+deployed.</p>
+<a name="_Toc96698086"></a>
+
+<h3>Installing Axis2 in a Servlet container</h3>
+<ol>
+  <li><a href="http://ws.apache.org/axis2/download.cgi">Download</a> Axis2 war file</li>
+  <li>Drop the war in the webapps folder. Most servlet containers will
+    automatically install war. (some servlet containers may require a restart
+    in order to capture the new web application. Refer your servlet container
+    documentation for more information about this.)</li>
+  <li>Once the WAR is successfully installed, test it by pointing the web
+    browser to the <strong>http:// &lt;host :port&gt;/ axis2. </strong>It
+    should produce the following page which is the <strong>Axis2 Web
+    Application Home Page</strong>.</li>
+
+  <p align="center"><strong><img src="images/clip_image006.jpg"
+  alt=""></strong></p>
+
+  <p></p>
+  <li>Use validate link to ensure that everything is fine and smooth. If the
+    validation fails then the war has failed to install properly or some
+    essential jars are missing. At such a situation the documentation of the
+    particular servlet container should be consulted to find the problem. The
+    following page is a successful validation. Note the statement core Axis2
+    libraries are present.
+    <p></p>
+  </li>
+
+  <p align="center"><strong><img src="images/happyaxis.jpg"
+  alt=""></strong></p>
+</ol>
+<a name="upload"></a>
+<h4>Uploading services</h4>
+<ol>
+  <p>The Axis2 web application also provides an interface to upload services.
+  Once a service is created according to the service specification as
+  described in userguide that jar file can be uploaded using the upload
+  page.</p>
+
+  <p align="center"><strong><img src="images/clip_image010.jpg"
+  alt=""></strong></p>
+
+  <p>The uploaded jar files will be stored in the default service directory.
+  For Axis2 this will be the &lt;webapps&gt;/axis2/WEB-INF/services
+  directory. Once a service is uploaded it will be installed instantly.</p>
+
+  <p>Since Axis2 supports hot deployment one can drop the service jar
+  directly through the file system to the above mentioned services
+  directory.It will also cause the service to be automatically installed
+  without the container being restarted.</p>
+
+  <p>Use the 'Services' link on the Web Application home page to check the
+  successful installation of a service. The services and the operations of
+  successfully installed services will be displayed in the available services
+  page.</p>
+
+  <p align="center"><img src="images/clip_image012.jpg" alt=""></p>
+
+  <p></p>
+
+  <p>If the service has deployment time error it will list those services as
+  faulty services. If you click on the link you can see the your deployment
+  fault error message(s).</p>
+
+  <p align="center"><img src="images/faultservice.jpg" alt=""></p>
+
+  <p>Deployment time error message</p>
+
+  <p align="center"><strong><img src="images/faultmsg.jpg"
+  alt=""></strong></p>
+
+  <p></p>
+
+  <p>Axis2 Administration is all about configuring Axis2 at the run time and
+  the configuration will be transient. More descriptions are available in <a
+  href="webadminguide.html">Axis2 Web Administration Guide</a></p>
+</ol>
+</body>
+</html>

Modified: webservices/axis2/trunk/java/xdocs/latest/mail-configuration.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/mail-configuration.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/mail-configuration.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/mail-configuration.html Wed Feb  8 03:33:41 2006
@@ -1,110 +1,110 @@
-<!-- saved from url=(0022)http://internet.e-mail -->
-<html>
-<head>
-<title>Mail transport</title>
-
-</head>
-
-<body><h1>Mail transport</h1>
-<p>The inner workings of the mail transport has two parts, the transport sender and the transport listener. The transport listener is a basic email client which will be on a loop checking for new messages for a particular email address. When an email comes in it will be tunneled into the Axis engine.</p>
-<p>Mail transport can be used against a generic mail server or it can be used like a mailet. The simple mailet provided with Axis2 will direct any message that is coming to a particular address into the Axis engine. The engine will process the message and will use the Transport sender to send the reply.</p>
-<p></p>
-<p>To get started on the mail transport you need the following additional jar dependencies on the classpath.</p>
-  <ol>
-  <li>javamail</li>
-  <li>activation</li>
-  </ol>
-<p>We use the Geronimo version of these jars to compile but you will need the sun version to run the code. Specificaly we are using geronimo-spec-javamail-[version].jar and geronimo-spec-activation-[version].jar. These will be downloaded by maven when you run the maven build.</p>
-
-<h2>Transport Sender</h2>
-<p>You need to have a mail account to activate the mail functionality. This can either be a generic mail server or you can start up a james mail server. The Mail transport sender can be activated by adding following entry to the axis2.xml file.</p>
-  <source>
-  <pre>
-   &lt;transportSender name="mail" class="org.apache.axis2.transport.mail.MailTransportSender"&gt;
-        &lt;parameter name="transport.mail.smtp.host" locked="xsd:false"&gt;smtp server host&lt;/parameter&gt;
-        &lt;parameter name="transport.mail.smtp.user" locked="xsd:false"&gt;user name&lt;/parameter&gt;
-        &lt;parameter name="transport.mail.smtp.password" locked="xsd:false"&gt;password&lt;/parameter&gt;
-        &lt;parameter name="transport.mail.smtp.port" locked="xsd:false"&gt;Port on the server for pop&lt;/parameter&gt;
-   &lt;/transportSender&gt;
-  </pre>
-  </source>
-
-  <h2>Transport Receiver</h2>
-
-  <p>The mail Listener can be activated by adding the following entry to the axis2.xml file.</p>
-
-  <source><pre>
-   &lt;transportReceiver name="mail" class="org.apache.axis2.transport.mail.SimpleMailListener"&gt;
-        &lt;parameter name="transport.mail.pop3.host" locked="xsd:false"&gt;pop server host&lt;/parameter&gt;
-        &lt;parameter name="transport.mail.pop3.user" locked="xsd:false"&gt;user name&lt;/parameter&gt;
-        &lt;parameter name="transport.mail.pop3.password" locked="xsd:false"&gt;password&lt;/parameter&gt;
-        &lt;parameter name="transport.mail.pop3.port" locked="xsd:false"&gt;Port on the server for smtp&lt;/parameter&gt;
-        &lt;parameter name="transport.mail.replyToAddress" locked="xsd:false"&gt;email address&lt;/parameter&gt;
-  &lt;/transportReceiver&gt;
-  </pre></source>
-
-  <p>At the Client side if the Mail Listener is needed it is automatically started by Axis2.</p>
-
-  <h2>Using Mail transport in the Server Side</h2>
-  <p> If the Mail Listener is need to be started as the server it can be done with following command with the all the axis2 jars and the mail dependency jars in the classpath.</p>
-  <source><pre>java org.apache.axis2.transport.mail.SimpleMailListener repository-directory</pre></source>
-
-  <h2>Using Mail transport in the Client Side</h2>
-  <p>Following code segment shows how to send a oneway SOAP message using the mail transport, this need the Transport Sender configured.</p>
-<source>
-<pre>
-OMElement payload = ....
-
-MessageSender sender = new MessageSender(serviceContext);
-sender.setTo(targetEPR);
-sender.setSenderTransport(Constants.TRANSPORT_MAIL);
-
-sender.send(operationName.getLocalPart(), payload);
-</pre>
-</source>
-  
-  <h2>Configure James as SMTP and POP server</h2>
-  <p>Download the <a href="http://james.apache.org/">Apache James</a> and start James, connect to the James via telnet for administrator James with the following code
-</p>
-
-<source>
-<pre>
-$telnet 127.0.0.1 4555
-Trying 127.0.0.1...
-Connected to localhost.localdomain (127.0.0.1).
-Escape character is '^]'.
-JAMES Remote Administration Tool 2.2.0
-Please enter your login and password
-Login id:
-root
-Password:
-root
-Welcome root. HELP for a list of commands
-</pre>
-</source>
-
-<p>Add users to James</p>
-<source>
-<pre>
-adduser axis2-server axis2
-User axis2-server added
-adduser axis2-client axis2
-User axis2-client added
-Connection closed by foreign host.
-</pre>
-</source>
-
-  <p>Now James is up and running with the accounts</p>
-
-  <h2>Using the included mail server</h2>
-
-  <p>The inbuilt mail server can be started from the command line using the following piece of code when all the needed jars are in the class path.</p>
-<p><code>java org.apache.axis2.transport.mail.server.MailServer</code></p>
-  <p>The server itself does not need any configuration or tinkering to work. A ConfigurationContext and the ports to operate on are the only details needed. The server will store the mails in memory against the recipient till the recipient pops it from the server. To facilitate the use in *nix environments as a non root user the pop and smtp ports used by default config/test cases are (1024 + 25) and (1024 + 110).</p>
-
-  <hr/>
-
-  <p>&nbsp;</p>
-
-</body>
-</html>
+<!-- saved from url=(0022)http://internet.e-mail -->
+<html>
+<head>
+<title>Mail transport</title>
+
+</head>
+
+<body><h1>Mail transport</h1>
+<p>The inner workings of the mail transport has two parts, the transport sender and the transport listener. The transport listener is a basic email client which will be on a loop checking for new messages for a particular email address. When an email comes in it will be tunneled into the Axis engine.</p>
+<p>Mail transport can be used against a generic mail server or it can be used like a mailet. The simple mailet provided with Axis2 will direct any message that is coming to a particular address into the Axis engine. The engine will process the message and will use the Transport sender to send the reply.</p>
+<p></p>
+<p>To get started on the mail transport you need the following additional jar dependencies on the classpath.</p>
+  <ol>
+  <li>javamail</li>
+  <li>activation</li>
+  </ol>
+<p>We use the Geronimo version of these jars to compile but you will need the sun version to run the code. Specificaly we are using geronimo-spec-javamail-[version].jar and geronimo-spec-activation-[version].jar. These will be downloaded by maven when you run the maven build.</p>
+
+<h2>Transport Sender</h2>
+<p>You need to have a mail account to activate the mail functionality. This can either be a generic mail server or you can start up a james mail server. The Mail transport sender can be activated by adding following entry to the axis2.xml file.</p>
+  <source>
+  <pre>
+   &lt;transportSender name="mail" class="org.apache.axis2.transport.mail.MailTransportSender"&gt;
+        &lt;parameter name="transport.mail.smtp.host" locked="xsd:false"&gt;smtp server host&lt;/parameter&gt;
+        &lt;parameter name="transport.mail.smtp.user" locked="xsd:false"&gt;user name&lt;/parameter&gt;
+        &lt;parameter name="transport.mail.smtp.password" locked="xsd:false"&gt;password&lt;/parameter&gt;
+        &lt;parameter name="transport.mail.smtp.port" locked="xsd:false"&gt;Port on the server for pop&lt;/parameter&gt;
+   &lt;/transportSender&gt;
+  </pre>
+  </source>
+
+  <h2>Transport Receiver</h2>
+
+  <p>The mail Listener can be activated by adding the following entry to the axis2.xml file.</p>
+
+  <source><pre>
+   &lt;transportReceiver name="mail" class="org.apache.axis2.transport.mail.SimpleMailListener"&gt;
+        &lt;parameter name="transport.mail.pop3.host" locked="xsd:false"&gt;pop server host&lt;/parameter&gt;
+        &lt;parameter name="transport.mail.pop3.user" locked="xsd:false"&gt;user name&lt;/parameter&gt;
+        &lt;parameter name="transport.mail.pop3.password" locked="xsd:false"&gt;password&lt;/parameter&gt;
+        &lt;parameter name="transport.mail.pop3.port" locked="xsd:false"&gt;Port on the server for smtp&lt;/parameter&gt;
+        &lt;parameter name="transport.mail.replyToAddress" locked="xsd:false"&gt;email address&lt;/parameter&gt;
+  &lt;/transportReceiver&gt;
+  </pre></source>
+
+  <p>At the Client side if the Mail Listener is needed it is automatically started by Axis2.</p>
+
+  <h2>Using Mail transport in the Server Side</h2>
+  <p> If the Mail Listener is need to be started as the server it can be done with following command with the all the axis2 jars and the mail dependency jars in the classpath.</p>
+  <source><pre>java org.apache.axis2.transport.mail.SimpleMailListener repository-directory</pre></source>
+
+  <h2>Using Mail transport in the Client Side</h2>
+  <p>Following code segment shows how to send a oneway SOAP message using the mail transport, this need the Transport Sender configured.</p>
+<source>
+<pre>
+OMElement payload = ....
+
+MessageSender sender = new MessageSender(serviceContext);
+sender.setTo(targetEPR);
+sender.setSenderTransport(Constants.TRANSPORT_MAIL);
+
+sender.send(operationName.getLocalPart(), payload);
+</pre>
+</source>
+  
+  <h2>Configure James as SMTP and POP server</h2>
+  <p>Download the <a href="http://james.apache.org/">Apache James</a> and start James, connect to the James via telnet for administrator James with the following code
+</p>
+
+<source>
+<pre>
+$telnet 127.0.0.1 4555
+Trying 127.0.0.1...
+Connected to localhost.localdomain (127.0.0.1).
+Escape character is '^]'.
+JAMES Remote Administration Tool 2.2.0
+Please enter your login and password
+Login id:
+root
+Password:
+root
+Welcome root. HELP for a list of commands
+</pre>
+</source>
+
+<p>Add users to James</p>
+<source>
+<pre>
+adduser axis2-server axis2
+User axis2-server added
+adduser axis2-client axis2
+User axis2-client added
+Connection closed by foreign host.
+</pre>
+</source>
+
+  <p>Now James is up and running with the accounts</p>
+
+  <h2>Using the included mail server</h2>
+
+  <p>The inbuilt mail server can be started from the command line using the following piece of code when all the needed jars are in the class path.</p>
+<source><pre>java org.apache.axis2.transport.mail.server.MailServer</pre></source>
+  <p>The server itself does not need any configuration or tinkering to work. A ConfigurationContext and the ports to operate on are the only details needed. The server will store the mails in memory against the recipient till the recipient pops it from the server. To facilitate the use in *nix environments as a non root user the pop and smtp ports used by default config/test cases are (1024 + 25) and (1024 + 110).</p>
+
+  <hr/>
+
+  <p>&nbsp;</p>
+
+</body>
+</html>

Modified: webservices/axis2/trunk/java/xdocs/latest/mail-transport.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/mail-transport.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/mail-transport.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/mail-transport.html Wed Feb  8 03:33:41 2006
@@ -32,9 +32,9 @@
 <p>Broadly speaking there are 3 ways of calling a service through mail.</p>
 
 <blockquote>
-  1. Using the simple mail server included in Axis2.<br>
-  2. Using a generic mail server.<br>
-  3. Using mailets.<br>
+  1. Using the simple mail server included in Axis2.<br/>
+  2. Using a generic mail server.<br/>
+  3. Using mailets.<br/>
 </blockquote>
 
 <p></p>
@@ -60,7 +60,7 @@
 
 <p>Now that we have the environment set up, let us start pumping out some
 code to get the mail functionality off the ground. First we'll have a look at
-it from the mail server side. <br>
+it from the mail server side. <br/>
 </p>
 <source><pre>        // Start the mail server using the default configurations.
         ConfigurationContext configContext = UtilsMailServer.start();

Modified: webservices/axis2/trunk/java/xdocs/latest/mtom-guide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/mtom-guide.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/mtom-guide.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/mtom-guide.html Wed Feb  8 03:33:41 2006
@@ -35,7 +35,7 @@
 there are times when serializing data into XML does not make sense. Web
 services users may need to transmit binary attachments of various sorts like
 images, drawings, xml docs, etc together with SOAP message. Such data are
-often in a particular binary format.<br>
+often in a particular binary format.<br/>
 Traditionally, two techniques have been used in dealing with opaque data in
 XML;</p>
 <ol>
@@ -238,9 +238,11 @@
   </li>
 </ul>
 
-<p><source></p>
+<p><source>
 <pre>&lt;parameter name="enableMTOM" locked="false"&gt;true&lt;/parameter&gt;</pre>
-</source><ul>
+</source>
+</p>
+<ul>
   <ul>
     <p>User must restart the server after setting this parameter.</p>
   </ul>
@@ -276,7 +278,8 @@
     }
 }</pre>
 </source><ul>
-  <li><strong><a name="242"></a>Client</strong></li>
+    <a name="242"/>
+  <li><strong>Client</strong></li>
 </ul>
 <source><pre>        Options options = new Options();
         options.setTo(targetEPR); 

Modified: webservices/axis2/trunk/java/xdocs/latest/rest-ws.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/rest-ws.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/rest-ws.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/rest-ws.html Wed Feb  8 03:33:41 2006
@@ -54,12 +54,12 @@
 
 <p>There is an example named, userguide.clients.RESTClient.java which
 demonstrates the usage of the above, using the "echo"operation of the
-<source></p>
+    </p>
 <pre>userguide.example1.MyService </pre>
 
 <p>of the samples.The class source will be as follows:</p>
 
-<p><source></p>
+<source>
 <pre>public class RESTClient {
 
     private static String toEpr = "http://localhost:8080/axis2/services/MyService";
@@ -111,9 +111,9 @@
 <source><pre>http://127.0.0.1:8080/axis2/services/version/getVersion</pre>
 </source>
 <p>Result can be shown in the browser as follows:</p>
-<img src="images/userguide/http-get-ws.png">
+<img src="images/userguide/http-get-ws.png" alt="" />
 
-<p>For example, the following request, <source></p>
+<p>For example, the following request, </p><source>
 <pre>http://127.0.0.1:8080/axis2/services/version/getVersion</pre>
 </source>will be converted to the following SOAP Message for processing by
 Axis2.<source>
@@ -124,5 +124,7 @@
       &lt;/soapenv:Body&gt;
    &lt;/soapenv:Envelope&gt;
     </pre>
-</source></body>
+</source>
+
+</body>
 </html>

Modified: webservices/axis2/trunk/java/xdocs/latest/security-module.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/security-module.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/security-module.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/security-module.html Wed Feb  8 03:33:41 2006
@@ -1,23 +1,34 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html><title>The Security Module</title>
+<html><title>The Security Module</title>
+
 <body>
 <h1>Securing SOAP Messages with WSS4J</h1>
 
-<p>Axis2 comes with a module based on WSS4J [1] to provide WS-Security features. This section explains how to engage and configure the security module. Since the security module inserts handlers in the system specific pre-dispatch phase, it must be engaged globally. But it is possible to activate the security module for the inflow or the outflow when required by the service or the clients.</p>
+<p>Axis2 comes with a module based on WSS4J [1] to provide WS-Security features. This section
+   explains how to engage and configure the security module. Since the security module inserts
+   handlers in the system specific pre-dispatch phase, it must be engaged globally. But it is
+   possible to activate the security module for the inflow or the outflow when required by the
+   service or the clients.</p>
+
+<p>The security module (security.mar) is available in the axis2.war but it is not engaged by
+   default.</p>
 
-<p>The security module (security.mar) is available in the axis2.war but it is not engaged by default.</p>
 <p>First it should be engaged by inserting the following in the axis2.xml file.</p>
 <source><pre>
-	&lt;module ref="security"/&gt;
+    &lt;module ref="security"/&gt;
 </pre></source>
-<p>The web admin interface can be used when Axis2 is deployed in a servlet container such as Apache Tomcat.</p>
 
-<p>At the server it is possible to provide security on a per service basis. The configuration parameters should be set in the service.xml file of the service. The client side config parameters should be set in the axis2.xml of the client's Axis2 repository.</p>
+<p>The web admin interface can be used when Axis2 is deployed in a servlet container such as Apache
+   Tomcat.</p>
+
+<p>At the server it is possible to provide security on a per service basis. The configuration
+   parameters should be set in the service.xml file of the service. The client side config
+   parameters should be set in the axis2.xml of the client's Axis2 repository.</p>
 
 <p>The security module uses two parameters:</p>
 <ul>
-<li>OutflowSecurity</li>
-<li>InflowSecurity</li>
+    <li>OutflowSecurity</li>
+    <li>InflowSecurity</li>
 </ul>
 
 The configuration that can go in each of these parameters are described below:
@@ -25,145 +36,176 @@
 <h3>OutflowSecurity parameter</h3>
 
 This parameter is used to configure the outflow security handler. The outflow
- handler can be invoked more than once in the outflow one can provide
- configuration for each of these invocations. The 'action' element describes
- one of these configurations. Therefore the 'OutflowSecurity' parameter can 
- contain more than one 'action' elements. The schema of this 'action' element 
- is available <a href="sec-conf/out-action.xsd">here</a>.
-<p>An outflow configuration to add a timestamp, sing and encrypt 
- the message once, is shown in<a href="#ex1"> Example 1</a> and <a href="#ex1">
- Example 2</a> shows how to sign the message twice by chaining the outflow 
- handler (using two 'action' elements)</p>
- 
-<p>Following is a description of the elements that can go in an 'action' 
-element of the OutflowSecurity parameter</p>
-<br>
+handler can be invoked more than once in the outflow one can provide
+configuration for each of these invocations. The 'action' element describes
+one of these configurations. Therefore the 'OutflowSecurity' parameter can
+contain more than one 'action' elements. The schema of this 'action' element
+is available <a href="sec-conf/out-action.xsd">here</a>.
+<p>An outflow configuration to add a timestamp, sing and encrypt
+   the message once, is shown in<a href="#ex1"> Example 1</a> and <a href="#ex1">
+    Example 2</a> shows how to sign the message twice by chaining the outflow
+                  handler (using two 'action' elements)</p>
+
+<p>Following is a description of the elements that can go in an 'action'
+   element of the OutflowSecurity parameter</p>
+<br/>
 <table border="1">
-<tr>
-<td><b>Parameter</b></td>
-<td><b>Description</b></td>
-<td><b>Example</b></td>
-</tr>
-<tr>
-<td>items</td>
-<td>Security actions for the inflow</td>
-<td>Add a Timestamp, Sign the SOAP body and Encrypt the SOAP body <br>&lt;items&gt; Timestamp Signature Encrypt&lt;/items&gt;</td>
-</tr>
-<tr>
-<td>user</td>
-<td>The user's name</td>
-<td>Set alias of the key to be used to sign<br>&lt;user&gt; bob&lt;/user&gt;</td>
-</tr>
-<tr>
-<td>passwordCallbackClass</td>
-<td>Callback class used to provide the password required to create the UsernameToken or to sign the message</td>
-<td>&lt;passwordCallbackClass&gt; org.apache.axis2.security.PWCallback&lt;/passwordCallbackClass&gt;</td>
-</tr>
-<tr>
-<td>signaturePropFile</td>
-<td>property file used to get the signature parameters such as crypto provider, keystore and its password</td>
-<td>Set example.properties file as the signature property file<br>&lt;signaturePropFile&gt; example.properties&lt;/signaturePropFile&gt;</td>
-</tr>
-<tr>
-<td>signatureKeyIdentifier</td>
-<td>Key identifier to be used in referring the key in the signature</td>
-<td>Use the serial number of the certificate<br>&lt;signatureKeyIdentifier&gt; IssuerSerial&lt;/signatureKeyIdentifier&gt;</td>
-</tr>
-<tr>
-<td>encryptionKeyIdentifier</td>
-<td>Key identifier to be used in referring the key in encryption</td>
-<td>Use the serial number of the certificate <br>&lt;encryptionKeyIdentifier&gt;IssuerSerial&lt;/encryptionKeyIdentifier&gt;</td>
-</tr>
-<tr>
-<td>encryptionUser</td>
-<td>The user's name for encryption.</td>
-<td><br>&lt;encryptionUser&gt;alice&lt;/encryptionUser&gt;</td>
-</tr>
-<tr>
-<td>encryptionSymAlgorithm</td>
-<td>Symmetric algorithm to be used for encryption</td>
-<td>Use AES-128<br>&lt;encryptionSymAlgorithm&gt; http://www.w3.org/2001/04/xmlenc#aes128-cbc&lt;/encryptionSymAlgorithm&gt;</td>
-</tr>
-<tr>
-<td>encryptionKeyTransportAlgorithm</td>
-<td>Key encryption algorithm</td>
-<td>Use RSA-OAEP<br>&lt;parameter name="encryptionSymAlgorithm"&gt; http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p&lt;/parameter&gt;</td>
-</tr>
-<tr>
-<td>signatureParts</td>
-<td>Sign multiple parts in the SOAP message</td>
-<td>Sign Foo and Bar elements qualified by "http://app.ns/ns"<br>&lt;signatureParts&gt; {Element}{http://app.ns/ns}Foo;{Element}{http://app.ns/ns}Bar &lt;/signatureParts&gt;</td>
-</tr>
-<tr>
-<td>optimizeParts</td>
-<td>MTOM Optimize the elements specified by the XPath query</td>
-<td>Optimize the CipherValue<br>&lt;optimizeParts&gt; //xenc:EncryptedData/xenc:CipherData/xenc:CipherValue &lt;/optimizeParts&gt;</td>
-</tr>
+    <tr>
+        <td><b>Parameter</b></td>
+        <td><b>Description</b></td>
+        <td><b>Example</b></td>
+    </tr>
+    <tr>
+        <td>items</td>
+        <td>Security actions for the inflow</td>
+        <td>Add a Timestamp, Sign the SOAP body and Encrypt the SOAP body <br/>&lt;items&gt;
+            Timestamp Signature Encrypt&lt;/items&gt;</td>
+    </tr>
+    <tr>
+        <td>user</td>
+        <td>The user's name</td>
+        <td>Set alias of the key to be used to sign<br/>&lt;user&gt; bob&lt;/user&gt;</td>
+    </tr>
+    <tr>
+        <td>passwordCallbackClass</td>
+        <td>Callback class used to provide the password required to create the UsernameToken or to
+            sign the message</td>
+        <td>&lt;passwordCallbackClass&gt; org.apache.axis2.security.PWCallback&lt;/passwordCallbackClass&gt;</td>
+    </tr>
+    <tr>
+        <td>signaturePropFile</td>
+        <td>property file used to get the signature parameters such as crypto provider, keystore and
+            its password</td>
+        <td>Set example.properties file as the signature property file<br/>&lt;signaturePropFile&gt;
+            example.properties&lt;/signaturePropFile&gt;</td>
+    </tr>
+    <tr>
+        <td>signatureKeyIdentifier</td>
+        <td>Key identifier to be used in referring the key in the signature</td>
+        <td>Use the serial number of the certificate<br/>&lt;signatureKeyIdentifier&gt; IssuerSerial&lt;/signatureKeyIdentifier&gt;
+        </td>
+    </tr>
+    <tr>
+        <td>encryptionKeyIdentifier</td>
+        <td>Key identifier to be used in referring the key in encryption</td>
+        <td>Use the serial number of the certificate <br/>&lt;encryptionKeyIdentifier&gt;IssuerSerial&lt;/encryptionKeyIdentifier&gt;
+        </td>
+    </tr>
+    <tr>
+        <td>encryptionUser</td>
+        <td>The user's name for encryption.</td>
+        <td><br/>&lt;encryptionUser&gt;alice&lt;/encryptionUser&gt;</td>
+    </tr>
+    <tr>
+        <td>encryptionSymAlgorithm</td>
+        <td>Symmetric algorithm to be used for encryption</td>
+        <td>Use AES-128<br/>&lt;encryptionSymAlgorithm&gt;
+            http://www.w3.org/2001/04/xmlenc#aes128-cbc&lt;/encryptionSymAlgorithm&gt;</td>
+    </tr>
+    <tr>
+        <td>encryptionKeyTransportAlgorithm</td>
+        <td>Key encryption algorithm</td>
+        <td>Use RSA-OAEP<br/>&lt;parameter name="encryptionSymAlgorithm"&gt;
+            http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p&lt;/parameter&gt;</td>
+    </tr>
+    <tr>
+        <td>signatureParts</td>
+        <td>Sign multiple parts in the SOAP message</td>
+        <td>Sign Foo and Bar elements qualified by "http://app.ns/ns"<br/>&lt;signatureParts&gt;
+            {Element}{http://app.ns/ns}Foo;{Element}{http://app.ns/ns}Bar &lt;/signatureParts&gt;
+        </td>
+    </tr>
+    <tr>
+        <td>optimizeParts</td>
+        <td>MTOM Optimize the elements specified by the XPath query</td>
+        <td>Optimize the CipherValue<br/>&lt;optimizeParts&gt;
+            //xenc:EncryptedData/xenc:CipherData/xenc:CipherValue &lt;/optimizeParts&gt;</td>
+    </tr>
 </table>
-<br>
+<br/>
+
 <h3>InflowSecurity parameter</h3>
-<p>This parameter is used to configure the inflow security handler. The 'action' element is used to 
-encapsulate the configuration elements here as well. The schema of the 'action' element is available here. 
-<a href="#ex3">Example 3</a> shows the configuration to decrypt, verify signature and validate timestamp.</p>
-<table border="1">
-<tr>
-<td><b>Parameter</b></td>
-<td><b>Description</b></td>
-<td><b>Example</b></td>
-</tr>
-<tr>
-<td>items</td>
-<td>Security actions for the inflow</td>
-<td>first the incoming message should be decrypted and then the signatures should be verified and should be checked for the availability of the Timestamp <br>&lt;items&gt; Timestamp Signature Encrypt&lt;/items&gt;</td>
-</tr>
-<tr>
-<td>passwordCallbackClass</td>
-<td>Callback class used to obtain password for decryption and UsernameToken verification</td>
-<td><br>&lt;passwordCallbackClass&gt; org.apache.axis2.security.PWCallback&lt;/passwordCallbackClass&gt;</td>
-</tr>
-<tr>
-<td>signaturePropFile</td>
-<td>Property file used for signature verification</td>
-<td><br>&lt;signaturePropFile&gt; sig.properties&lt;/signaturePropFile&gt;</td>
-</tr>
-<td>decryptionPropFile</td>
-<td>Property file used for decryption</td>
-<td> <br>&lt;decryptionPropFile&gt; dec.properties&lt;/decryptionPropFile&gt;</td>
-</tr>
 
+<p>This parameter is used to configure the inflow security handler. The 'action' element is used to
+   encapsulate the configuration elements here as well. The schema of the 'action' element is
+   available here.
+    <a href="#ex3">Example 3</a> shows the configuration to decrypt, verify signature and validate
+                                 timestamp.</p>
+<table border="1">
+    <tr>
+        <td><b>Parameter</b></td>
+        <td><b>Description</b></td>
+        <td><b>Example</b></td>
+    </tr>
+    <tr>
+        <td>items</td>
+        <td>Security actions for the inflow</td>
+        <td>first the incoming message should be decrypted and then the signatures should be
+            verified and should be checked for the availability of the Timestamp <br/>&lt;items&gt;
+            Timestamp Signature Encrypt&lt;/items&gt;</td>
+    </tr>
+    <tr>
+        <td>passwordCallbackClass</td>
+        <td>Callback class used to obtain password for decryption and UsernameToken
+            verification</td>
+        <td><br/>&lt;passwordCallbackClass&gt; org.apache.axis2.security.PWCallback&lt;/passwordCallbackClass&gt;
+        </td>
+    </tr>
+    <tr>
+        <td>signaturePropFile</td>
+        <td>Property file used for signature verification</td>
+        <td><br/>&lt;signaturePropFile&gt; sig.properties&lt;/signaturePropFile&gt;</td>
+    </tr>
+    <tr>
+        <td>decryptionPropFile</td>
+        <td>Property file used for decryption</td>
+        <td><br/>&lt;decryptionPropFile&gt; dec.properties&lt;/decryptionPropFile&gt;</td>
+    </tr>
 </table>
-<br>
-<p>Please note that the '.properties' files used in properties such as OutSignaturePropFile are the same property files that are using in the WSS4J project. 
-Following shows the properties defined in a sample property file</p>
+<br/>
+
+<p>Please note that the '.properties' files used in properties such as OutSignaturePropFile are the
+   same property files that are using in the WSS4J project.
+   Following shows the properties defined in a sample property file</p>
 
 <source>
-<pre>
-org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
-org.apache.ws.security.crypto.merlin.keystore.type=pkcs12
-org.apache.ws.security.crypto.merlin.keystore.password=security
-org.apache.ws.security.crypto.merlin.keystore.alias=16c73ab6-b892-458f-abf5-2f875f74882e
-org.apache.ws.security.crypto.merlin.alias.password=security
-org.apache.ws.security.crypto.merlin.file=keys/x509.PFX.MSFT
-</pre>
+    <pre>
+        org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
+        org.apache.ws.security.crypto.merlin.keystore.type=pkcs12
+        org.apache.ws.security.crypto.merlin.keystore.password=security
+        org.apache.ws.security.crypto.merlin.keystore.alias=16c73ab6-b892-458f-abf5-2f875f74882e
+        org.apache.ws.security.crypto.merlin.alias.password=security
+        org.apache.ws.security.crypto.merlin.file=keys/x509.PFX.MSFT
+    </pre>
 </source>
 
-org.apache.ws.security.crypto.provider defines the implementation of the org.apache.ws.security.components.crypto.Crypto 
-interface to provide the crypto information required by WSS4J. The other properties defined are the configuration
- properties used by the implementation class (org.apache.ws.security.components.crypto.Merlin).
- 
+org.apache.ws.security.crypto.provider defines the implementation of the
+org.apache.ws.security.components.crypto.Crypto
+interface to provide the crypto information required by WSS4J. The other properties defined are the
+configuration
+properties used by the implementation class (org.apache.ws.security.components.crypto.Merlin).
+
 <p><b>References</b></p>
+
 <p>1. <a href="http://ws.apache.org/wss4j">Apache WSS4J</a></p>
-<br>
+<br/>
+
 <p><b>Examples</b></p>
-<p id="ex1">Example 1: An outflow configuration to add a timestamp, sing and encrypt 
- the message once</p>
-<p><img src="sec-conf/out-sample.png"/>
+
+<p id="ex1">Example 1: An outflow configuration to add a timestamp, sing and encrypt
+            the message once</p>
+
+<p><img alt="" src="sec-conf/out-sample.png"/>
 </p>
 
 <p id="ex2">Example 2: An outflow configuration to sign the message twice and add a timestamp</p>
-<p><img src="sec-conf/out-sample2.png"/>
+
+<p><img alt="" src="sec-conf/out-sample2.png"/>
 </p>
-<p id="ex3">Example 3: An inflow configuration to decrypt, verify signature and validate timestamp</p>
-<p><img src="sec-conf/in-sample.png"/>
+
+<p id="ex3">Example 3: An inflow configuration to decrypt, verify signature and validate
+            timestamp</p>
+
+<p><img alt="" src="sec-conf/in-sample.png"/>
 </p>
 </body></html>

Modified: webservices/axis2/trunk/java/xdocs/latest/tools/idea/Idea_plug-in_userguide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/tools/idea/Idea_plug-in_userguide.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/tools/idea/Idea_plug-in_userguide.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/tools/idea/Idea_plug-in_userguide.html Wed Feb  8 03:33:41 2006
@@ -11,7 +11,7 @@
 <body lang="en">
 <h1>IntelliJ IDEA Plug-ins</h1>
 
-<p><a href="http://ws.apache.org/axis2/download.cgi">[Download]</p>
+<p><a href="http://ws.apache.org/axis2/download.cgi">[Download]</a></p>
 
 <h2>Introduction</h2>
 
@@ -47,7 +47,8 @@
 
 <p><img alt="Figure3" src="images/fig1.jpg"></p>
 
-<h2><a name="WSDL2Java_Code_Generation">WSDL2Java Code Generation</a></h2>
+<a name="WSDL2Java_Code_Generation"/>
+<h2>WSDL2Java Code Generation</h2>
 
 <p>Select WSDL2Java codegenaration and click OK to generate code from a WSDL
 file. Then the following window will appear.</p>
@@ -89,7 +90,8 @@
 
 <p>If everything has gone well you will see the above message.</p>
 
-<h2><a name="Create_Service_Archive">Ceate Service Archive</a></h2>
+<a name="Create_Service_Archive"/>
+<h2>Ceate Service Archive</h2>
 
 <p>First step is to click on Axis2 IDEA plug-in icon and select 'create a
 service archive' radio button.</p>
@@ -175,7 +177,8 @@
 
 <p>If you click No, Next button will enable and you can go to next page.</p>
 
-<p><a name="Note">Note</a>: From this point onwards the steps are similar to
+<a name="Note">
+<p>Note: From this point onwards the steps are similar to
 all the sub wizards.</p>
 
 <p><img alt="fig12" src="images/fig12.jpg"></p>

Modified: webservices/axis2/trunk/java/xdocs/latest/transport_howto.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/transport_howto.html?rev=375935&r1=375934&r2=375935&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/transport_howto.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/transport_howto.html Wed Feb  8 03:33:41 2006
@@ -70,7 +70,7 @@
 should ideally be only done once for the lifetime of the Transport
 receiver.</p>
 
-<p><source></p>
+<p><source>
 <pre>try {
         //Create a factory 
         ConfigurationContextFactory factory = new ConfigurationContextFactory();
@@ -80,6 +80,7 @@
         log.info(e.getMessage());
 }</pre>
 </source>
+</p>
 <p>Now we need some kind of a listener to listen to the requests that come
 in. This you will need to implement according to the transport that you are
 trying to build. After a message is received at the receiver you can use the



Mime
View raw message