You are viewing a plain text version of this content. The canonical link for it is here.
Posted to axis-cvs@ws.apache.org by ch...@apache.org on 2006/05/15 07:51:47 UTC
svn commit: r406543 [2/6] - in /webservices/axis2/trunk/java/xdocs/latest:
./ adb/ adb/images/ images/ images/archi-guide/ images/userguide/ jibx/
resources/ resources/schemas/
Added: webservices/axis2/trunk/java/xdocs/latest/adb/adb-codegen-integration.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/adb/adb-codegen-integration.html?rev=406543&view=auto
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/adb/adb-codegen-integration.html (added)
+++ webservices/axis2/trunk/java/xdocs/latest/adb/adb-codegen-integration.html Sun May 14 22:51:17 2006
@@ -0,0 +1,102 @@
+<html>
+<head>
+ <meta http-equiv="content-type" content="">
+ <title></title>
+</head>
+
+<body>
+<h1>ADB Integration With Axis2</h1>
+
+<p>This document will assist you to write an extension using the integrator
+in order to integrate ADB with Axis2.</p>
+
+<h2>Content</h2>
+<ul>
+ <li><a href="#intro">Introduction</a></li>
+ <li><a href="#select_modes">Selection of Generation Modes for ADB</a></li>
+ <li><a href="#remember">Things to Remember</a></li>
+</ul>
+
+<h2><a name="intro">Introduction</a></h2>
+
+<p>ADB Integration with Axis2 is simple and straightforward. Given the
+extension mechanism of the Axis2 code generator, the obvious choice for the
+integrator is to write an extension. The extension that is added to support
+ADB is the SimpleDBExtension
+(<strong>org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension</strong>)
+and can be found in the extensions list of the codegen-config.properties
+file.</p>
+<a name="select_modes"></a>
+
+<h2>Selection of Generation Modes for ADB</h2>
+
+<p>The extension sets the options for the code generator via the
+CompilerOptions, depending on the users settings. The following table
+summarizes the use of options. Please refer the <a href="adb-howto.html"
+target="_blank">ADB-How to document</a> for the different generation modes
+and their descriptions.</p>
+
+<table border="1">
+ <caption></caption>
+ <tbody>
+ <tr>
+ <td><strong>User parameters</strong></td>
+ <td><strong>Selected code generation parameters</strong></td>
+ </tr>
+ <tr>
+ <td>None (no other parameter than the mandatory ones)</td>
+ <td>wrapClasses=false,writeClasses=false</td>
+ </tr>
+ <tr>
+ <td>-ss (server side)</td>
+ <td>wrapClasses=false,writeClasses=true</td>
+ </tr>
+ <tr>
+ <td>-u (unwrap classes)</td>
+ <td>wrapClasses=false,writeClasses=true</td>
+ </tr>
+ </tbody>
+</table>
+
+<p>If the users want to override these settings manually, they need to use
+the following parameters in the command line (prefixed with -E)</p>
+
+<table border="1">
+ <caption></caption>
+ <tbody>
+ <tr>
+ <td><strong>Parameter Name</strong></td>
+ <td><strong>Allowed values</strong></td>
+ <td><strong>Description</strong></td>
+ </tr>
+ <tr>
+ <td>r</td>
+ <td>true, false</td>
+ <td>Sets the write flag. If set to true the classes will be written by
+ ADB</td>
+ </tr>
+ <tr>
+ <td>w</td>
+ <td>true, false</td>
+ <td>Sets the packing flag. if true the classes will be packed.</td>
+ </tr>
+ </tbody>
+</table>
+
+<p></p>
+
+<p>Note that these parameters have no relevant long names and MUST be
+prefixed with a -E to be processed by the code generator. For example</p>
+<pre>WSDL2Java .... -Er true</pre>
+<a name="remember"></a>
+
+<h2>Things to Remember</h2>
+<ol>
+ <li>SimpleDBExtension is made to process requests only when the databinding
+ framework is specified as ADB (using the switch -d adb ). In the most
+ recent release, the default has been set as ADB and hence if the -d
+ option is missing then the databinding framework will be ADB.</li>
+</ol>
+<hr>
+</body>
+</html>
Added: webservices/axis2/trunk/java/xdocs/latest/adb/adb-howto.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/adb/adb-howto.html?rev=406543&view=auto
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/adb/adb-howto.html (added)
+++ webservices/axis2/trunk/java/xdocs/latest/adb/adb-howto.html Sun May 14 22:51:17 2006
@@ -0,0 +1,370 @@
+<html>
+<head>
+ <meta http-equiv="content-type" content="text/html; charset=UTF-8">
+ <meta content="">
+ <meta content="">
+ <meta content="">
+ <meta content="">
+ <meta content="">
+ <meta content="">
+ <title>ADB - Howto</title>
+</head>
+
+<body lang="en">
+<h1>Axis2 Databinding Framework</h1>
+
+<p>This document aims to provide the architectural overview of the Axis2
+Databinding Framework (referred to as ADB from here onwards) and be a guide
+to anyone who wants to use and modify ADB. The information is presented under
+the following topics.</p>
+
+<h2>Content</h2>
+<ul>
+ <li><a href="#intro">Introduction</a></li>
+ <li><a href="#archi">Architectural Overview</a></li>
+ <li><a href="#code_depend">Code and Dependencies</a></li>
+ <li><a href="#code_gen">Invoking the ADB Code Generator</a>
+ <ul>
+ <li><a href="#schema_compiler">As a Stand-alone Schema Compiler</a></li>
+ <li><a href="#api">Through the API</a></li>
+ </ul>
+ </li>
+ <li><a href="#gen_modes">Generation Modes</a></li>
+ <li><a href="#deep">Deep into Generated Code</a>
+ <ul>
+ <li><a href="#example">An Example!</a></li>
+ </ul>
+ </li>
+ <li><a href="#limitation">Known Limitations</a></li>
+ <li><a href="#more">Want to Learn More?</a></li>
+</ul>
+
+<h2><a name="intro">Introduction</a></h2>
+
+<p>The objective of the Axis2 Databinding framework is to provide a
+lightweight and simple schema compiler/ Java bean generator for Axis2. By no
+means it's to be a fully functional schema compiler like XMLBeans. Note that
+ADB is written in a fashion that allows it to be used as a stand-alone schema
+compiler and also to be extended to generate code for other languages.</p>
+<a name="archi"></a>
+
+<h2>Architectural Overview</h2>
+
+<p>ADB is built on a modular architecture that allows it to utilize a pre
+configured writer depending on the configuration.The 'big block diagram' for
+the code generator architecture is depicted below</p>
+
+<p><img src="images/ADB.jpg"></p>
+
+<p>ADB utilizes the WS-commons XmlSchema library for reading the Schema. The
+object model for the schema comes in the form of an XmlSchema object. The
+schema compiler keeps an instance of the writer (in the default case it's the
+JavaBeanWriter) which actually writes the classes. The writers may use
+whatever technique they prefer, in the case of the JavaBeanWriter, it uses an
+XSLT template. The SchemaCompiler also uses a typemapper object that tells it
+what classnames to be used for the QNames that it encounters. This type
+mapper is also part of the configuration and the users can override the
+default type mapper by overriding the property setting.</p>
+<a name="code_depend"></a>
+
+<h2>Code and Dependencies</h2>
+
+<p>As explained in the previous section, the schema compiler depends on the
+WS-Commons XmlSchema library. The XSLT transformations are dependent on the
+JVM's DOMimplementation (either crimson or xerces) which means that the
+underlying JVM should be 1.4 or higher. Apart from that ADB has no
+dependencies on any other special jar files. The code for the schema compiler
+is completely in the <strong>org.apache.axis2.schema.*</strong> package. This
+package resides in the codegen module of the Axis2 source tree.</p>
+
+<p>Following are the important classes and files:</p>
+<ol>
+ <li><strong>SchemaCompiler</strong> - The work horse that really compiles
+ the schema into classes.</li>
+ <li><strong>BeanWriter</strong> - BeanWriter represents the kind of
+ interface the SchemaCompiler accepts as a writer. The writer needs to
+ handle the actual writing of the clasess</li>
+ <li><strong>JavaBeanWriter</strong> - The default implementation of the
+ BeanWriter interface.</li>
+ <li><strong>TypeMap</strong> - represents the interface that the schema
+ compiler looks towards to find classes</li>
+ <li><strong>JavaTypeMap</strong> - the default implementation of the
+ TypeMap</li>
+ <li><strong>BeanTemplate.xsl</strong> - the XSLtemplate the JavaBeanWriter
+ uses.</li>
+ <li><strong>Schema-compile.properties</strong> - The property file for the
+ schema compiler</li>
+</ol>
+
+<p>The easiest way to obtain the ADB binaries is to run the maven build for
+the codegen module. This will generate the
+<strong>axis2-codegen-{$version}.jar</strong> inside the target folder which
+is directly usable when the ADB schema compiler is required.</p>
+
+<p>The runtime dependancies for the ADB generated classes is in the Axis2 ADB
+module. Hence to compile and work with the generated classes the
+<strong>axis2-adb-{$version}.jar</strong> needs to be in the classpath apart
+from other dependancies like the StAX utilities.</p>
+
+<p><a name="code_gen"></a></p>
+
+<h2>Invoking the ADB Code Generator</h2>
+
+<h3>As a Standalone Schema Compiler</h3>
+
+<p>ADB comes with a main class XSD2Java that allows the schemas to be
+compiled just by giving the schema file reference.This main class is pretty
+much primitive and does not provide much control over the code generation
+process. This is bound to improve in the near future.</p>
+
+<p>Code generator accepts the following parameters</p>
+<ol>
+ <li>The Schema file name - This should be a complete file name pointing to
+ the local file system</li>
+ <li>The output folder name - This should be the name of a folder within the
+ local file system</li>
+</ol>
+
+<p>Since the main class has no validations built in, the compiler is likely
+to cough up an unexpected error message if these parameters are not supplied
+properly.</p>
+<a name="api"></a>
+
+<h3>Through the API</h3>
+
+<p>This is the only way to harness the full potential of the schema compiler.
+The current Axis2 integration of ADB happens through this API. The most
+important classes and methods of the Schema compiler are as follows.</p>
+<ul>
+ <li><strong>SchemaCompiler - Constructor</strong>
+ <p>The constructor of the schema compiler expects a CompilerOptions
+ object. This compilerOptions object is more of a holder for the
+ parameters that are passed to the SchemaCompiler. The only mandatory
+ parameter in the CompilerOptions is the output directory</p>
+ </li>
+ <li><strong>SchemaCompiler - Compile(XMLSchema schema)</strong>
+ <p>The compile method to call for a single schema. The expected object is
+ a XMLSchema which is part of the XmlSchema library.</p>
+ </li>
+ <li><strong>SchemaCompiler - Compile(List schemaList)</strong>
+ <p>Similar to the previous method but accepts a list of schemas instead
+ of one.</p>
+ </li>
+</ul>
+
+<p>For a comprehensive code sample in invoking the schema compiler through
+the API, the following classes would be helpful. One would also need an
+understanding of the generation modes of the ADB schema compiler when using
+it through the API. Hence the following section includes a brief description
+of the generation modes .</p>
+<ul>
+ <li><strong>org.apache.axis2.schema.XSD2Java</strong></li>
+ <li><strong>org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension</strong></li>
+</ul>
+<a name="gen_modes"></a>
+
+<h2>Generation Modes</h2>
+
+<p>ADB extension provides several generation modes for the data bound
+classes.</p>
+<ol>
+ <li><strong>Integrated Mode</strong>
+ <p>In this mode the classes are generated as inner classes of the stub,
+ message receiver or the interface. The ADB framework refrains from
+ writing the classes but provides a map of DOM document objects that
+ contains the model for the databinding class. The implementers are free
+ to use the models for their needs. The Axis2 codegen engine parses these
+ documents within its own XSLT parser to create the necessary code.</p>
+ <p>Integrated mode is supposed to be used by the tool builders.</p>
+ </li>
+ <li><strong>Wrapped Mode</strong>
+ <p>In the wrapped mode, the ADB databinder generates one class that
+ contains all the databound classes. This is convenient when the number of
+ classes need to be limited.</p>
+ </li>
+ <li><strong>Expanded Mode</strong>
+ <p>This is the usual mode where the codegenerator generates a class for
+ each of the outer elements and the named complex types. The command line
+ tool (XSD2Java) always generates code in the expanded mode.</p>
+ </li>
+</ol>
+
+<p>The rules for generating code (described in the next section) applies
+regardless of the mode. Switching these modes can be done by passing the
+correct options via the CompilerOptions object. The following is table lists
+the options and the consequences of using them.</p>
+
+<table border="1">
+ <caption></caption>
+ <tbody>
+ <tr>
+ <td><strong>Field Name in Options</strong></td>
+ <td><strong>Description</strong></td>
+ </tr>
+ <tr>
+ <td>writeOutput</td>
+ <td>This determines whether to write the output or not. If the flag is
+ on then the classes will be written by ADB. The default is off.</td>
+ </tr>
+ <tr>
+ <td>wrapClasses</td>
+ <td>This determines whether to wrap the generated classes. If the flag
+ is on then a single class (with adb added to the end of the specified
+ package) will be generated. The default is off.</td>
+ </tr>
+ </tbody>
+</table>
+<a name="deep"></a>
+
+<h2>Deep into Generated Code</h2>
+
+<p>When the schema compiler is invoked (one-way or another) it generates code
+depending on the following rules</p>
+<ol>
+ <li>All named complex types become bean classes. Any attribute or element
+ encapsulated in this complex type will become a field in the generated
+ class. Note that the support for constructs other than the sequence and
+ all is not yet implemented.</li>
+ <li>All top level elements become classes. This is a rather questioning
+ feature since unless classes are generated for the top level elements the
+ handling of elements become difficult and messy!</li>
+ <li>SimpleType restrictions are handled by replacing the relevant type with
+ the basetype</li>
+</ol>
+
+<p>Once the code is generated according to the rules it looks like the
+following. Consider the following piece of schema</p>
+<pre><schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+xmlns:tns="http://soapinterop.org/types" targetNamespace="http://soapinterop.org/types">
+<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
+ <complexType name="SOAPStruct">
+ <sequence>
+ <element name="varString" type="xsd:string"/>
+ <element name="varInt" type="xsd:int"/>
+ <element name="varFloat" type="xsd:float"/>
+ </sequence>
+ </complexType>
+<element name="myElement" type="tns:SOAPStruct"/>
+</schema></pre>
+
+<p>For comprehension let us consider the expanded mode for the code
+generator. Unless specifically mentioned, the rest of this document assumes
+that the expanded mode of the code generation is used. This particular schema
+generates the following two classes in the designated package, which in this
+case would be <strong>org.soapinterop.types</strong>. This package is derived
+from the target namespace of the schema.</p>
+<ol>
+ <li>MyElement.java</li>
+ <li>SOAPStruct.java</li>
+</ol>
+
+<p>As explained earlier, SOAPStruct refers to the complexType. MyElement is
+the class that refers to the element. Just as expected, the SOAPStruct bean
+has getters and setters for varString, varInt and varFloat which are String,
+int and float respectively. MyElement on the other hand has a single field
+representing the SOAPStruct object that it encapsulates.</p>
+
+<p>The most important aspect of the generated code is that it encapsulates
+two methods for creation and serializing the beans. Note that to make this
+work, the generated beans implement the
+<strong>org.apache.axis2.databinding.ADBBean</strong> interface</p>
+
+<p>The creator and reader methods look like the following</p>
+<ul>
+ <li><pre>public javax.xml.stream.XMLStreamReader
+ getPullParser(javax.xml.namespace.QName qName)</pre>
+ <p>This method returns a pull parser that throws the right events for
+ this particular object. However there is a subtle difference between
+ element based classes and complexType based classes</p>
+ <ol>
+ <li>An element based bean class (like MyElement.java in the example)
+ will <strong><em>ignore the passed in QName</em></strong>. Instead of
+ using the passed in QName it'll utilize it's own QName which is
+ embedded in the class under the constant MY_QNAME, during the code
+ generation. Hence it is usual to call getPullparser with a null for
+ the elements.</li>
+ <li>A ComplexType based bean class(like SOAPStruct.java in the example)
+ will use the passed in QName to return an instance of the
+ ADBpullparser. This will effectively wrap the elements inside with an
+ element having the passed QName</li>
+ </ol>
+ </li>
+ <li><pre> public static [Object]
+ parse(javax.xml.stream.XMLStreamReader reader)
+ throws java.lang.Exception </pre>
+ <p>This method returns a populated instance of the class in question.
+ Note that</p>
+ <pre>[Object]</pre>
+ will be replaced by the actual class that contains this method. Say for
+ SOAPStruct the method looks like
+ <pre>public static SOAPStruct
+ parse(javax.xml.stream.XMLStreamReader reader)
+ throws java.lang.Exception</pre>
+ <p>Also note that the above parse method is available in the
+ <strong>Factory</strong> class generated into the relevant top level
+ class.Hence one will have to get the static Factory instance before calling the parse methods</p>
+
+ </li>
+</ul>
+<a name="example"></a>
+
+<h3>An Example!</h3>
+
+<p>Consider the following XML fragment</p>
+<pre><myElement>
+ <varInt>5</varInt>
+ <varString>Hello</varString>
+ <varFloat>3.3</varFloat>
+</myElement></pre>
+
+<p>Enthusiastic readers might already have figured out that this piece of XML
+complies to the Schema mentioned above. The following piece of code shows how
+to build a populated instance of MyElement with this fragment of XML</p>
+<pre>XMLStreamReader reader = XMLInputFactory.newInstance().
+ createXMLStreamReader(
+ new ByteArrayInputStream(xmlString.getBytes()));
+MyElement elt = MyElement.parse(reader);</pre>
+
+<p>Although this example takes on the tedious effort of creating a reader out
+of the String, inside the Axis2 environment an XMLStreamReader can be
+direclty asked from the OMElement! Hence the parse method becomes a huge
+advantage for hassle free object creation.</p>
+
+<p>Similarly the reader obtained from the object can also be utilized as
+needed. The following code fragment shows how to utilize the getPullParser
+method to create an OMElement</p>
+<pre>XMLStreamReader reader = elt.getPullParser(null);
+OMElement omElt = new StAXOMBuilder(reader).getDocumentElement();</pre>
+
+<p>That's all to it! If you are interested in learning more on ADB the
+following documents may also be helpful. However be sure to check the
+limitations section that follows if you are planning to use ADB for something
+serious.</p>
+<a name="limitation"></a>
+
+<h2>Known Limitations</h2>
+
+<p>ADB is meant to be a 'Simple' databinding framework and was not meant to
+compile all types of schemas. The following limitations are the most
+highlighted.</p>
+<ol>
+ <li>Complex Extensions and Restrictions, Simple Extensions and Restrictions
+ are not supported.</li>
+ <li>xsi:type based deserialization is not supported. Hence extension based
+ structures that use xsi:type attribute may fail</li>
+</ol>
+
+<p><a name="more"></a></p>
+
+<h2>Want to Learn More?</h2>
+<ul>
+ <li><a href="adb-tweaking.html">Tweaking the ADB Code Generator</a>-
+ explains available mechanisms to extend ADB and possibly adopt it to
+ compile schemas to support other languages.</li>
+ <li><a href="adb-codegen-integration.html">ADB and Axis2 Integration</a> -
+ explains how the ADB schema compiler was attached to the Axis2
+ framework</li>
+</ul>
+<hr>
+</body>
+</html>
Added: webservices/axis2/trunk/java/xdocs/latest/adb/adb-tweaking.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/adb/adb-tweaking.html?rev=406543&view=auto
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/adb/adb-tweaking.html (added)
+++ webservices/axis2/trunk/java/xdocs/latest/adb/adb-tweaking.html Sun May 14 22:51:17 2006
@@ -0,0 +1,119 @@
+<html>
+<head>
+ <meta http-equiv="content-type" content="">
+ <title></title>
+</head>
+
+<body lang="en">
+<h1>ADB Tweaking Guide</h1>
+
+<p>This document explains available mechanisms to extend ADB and possibly
+adopt it to compile schemas to support other languages.</p>
+
+<h2>Content</h2>
+<ul>
+ <li><a href="#intro">Introduction</a></li>
+ <li><a href="#config">Know the Configuration</a></li>
+ <li><a href="#first_tweak">The First Tweak - Generate Plain Java
+ Beans</a></li>
+ <li><a href="#advanced_tweak">A More Advanced Tweak - Generate Code for
+ Another Language</a></li>
+</ul>
+<a name="intro"></a>
+
+<h2>Introduction</h2>
+
+<p>ADB is written with future extensions in mind, with a clear and flexible
+way to extend or modify it's functionality. Available mechanisms to extend
+ADB and possibly adopt it to compile schemas to support other languages are
+described below.</p>
+<a name="config"></a>
+
+<h2>Know the Configuration</h2>
+
+<p>The configuration for the ADB framework is in the
+<strong>schema-compile.properties</strong> file found in the
+<strong>org.apache.axis2.databinding.schema</strong> package. This properties
+file has the following important properties</p>
+<ul>
+ <li>schema.bean.writer.class
+ <p>This is the writer class. This is used by the schema compiler to write
+ the beans and should implement the
+ <strong>org.apache.axis2.schema.writer.BeanWriter</strong> interface. The
+ schema compiler delegates the bean writing task to the specified instance
+ of the BeanWriter.</p>
+ </li>
+ <li>schema.bean.writer.template
+ <p>This specifies the template to be used in the BeanWriter. The
+ beanWriter author is free to use any mechanism to write the classes but
+ the default mechanism is to use a xsl template. This property may be left
+ blank if the BeanWriter implementation does not require a template.</p>
+ </li>
+ <li>schema.bean.typemap
+ <p>This is the type map to be used by the schema compiler. it should be
+ an implementation of the <strong>org.apache.axis2.schema.typemap</strong>
+ interface. The default typemap implementation encapsulates a hashmap with
+ type QName to Class name string mapping.</p>
+ </li>
+</ul>
+<a name="first_tweak"></a>
+
+<h2>The First Tweak - Generate Plain Java Beans</h2>
+
+<p>The first, most simple tweak for the code generator could be to switch to
+plain bean generation. The default behavior of the ADB framework is to
+generate ADBBeans, but most users, if they want to use ADB as a standalone
+compiler, would love to have plain java beans. This can in fact be done by
+simply changing the template used.</p>
+
+<p>The template for plain java beans is already available in the
+<strong>org.apache.axis2.schema.template </strong>package. To make this work
+replace the
+<strong>/org/apache/axis2/databinding/schema/template/ADBBeanTemplate.xsl
+</strong>with the
+<strong>/org/apache/axis2/databinding/schema/template/PlainBeanTemplate.xsl
+</strong>in the schema-compile.properties<strong>.</strong></p>
+
+<p>Congratulations! You just tweaked ADB to generate plain java beans.</p>
+
+<p>To generate custom formats, the templates need to be modified. The schema
+for the xml generated by the JavaBeanWriter is available in the source tree
+under the Other directory in the codegen module. Advanced users with
+knowledge of XSLT can easily modify the templates to generate code in their
+own formats.</p>
+<a name="advanced_tweak"></a>
+
+<h2>A More Advanced Tweak - Generate Code for Another Language</h2>
+
+<p>To generate code for another language, there are two main components are
+to be written.</p>
+<ul>
+ <li>The BeanWriter
+ <p>Implement the BeanWriter interface for this class. A nice example is
+ the <strong>org.apache.axis2.schema.writer.JavaBeanWriter</strong> which
+ has a lot of reusable code. In fact if the language is OOP based (such as
+ C# or even C++), one would even be able to extend the JavaBeanWriter
+ itself.</p>
+ </li>
+ <li>The TypeMap
+ <p>Implement the TypeMap interface for this class. The
+ <strong>org.apache.axis2.schema.typemap.JavaTypeMap</strong> class is a
+ simple implementation for the typemap where the QName to class name
+ strings are kept inside a hashmap instance. This technique is fairly
+ sufficient and only the type names would need to change to support
+ another language.</p>
+ </li>
+</ul>
+
+<p>Surprisingly this is enough to have other language support for ADB. Change
+the configuration and you are ready to generate code for other languages!</p>
+
+<p>This tweaking guide is supposed to be a simple guideline for anyone who
+wishes to dig deep into the mechanics of the ADB code generator. Users are
+free experiment with it and modify the schema compiler accordingly to their
+needs. Also note that the intention of this section is <em>not</em> to be a
+step by step guide to custom code generation. Anyone who wish to do so would
+need to dig into the code and get their hands dirty!</p>
+<hr>
+</body>
+</html>
Added: webservices/axis2/trunk/java/xdocs/latest/adb/images/ADB.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/adb/images/ADB.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/adb/images/ADB.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/axis2config.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/axis2config.html?rev=406543&view=auto
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/axis2config.html (added)
+++ webservices/axis2/trunk/java/xdocs/latest/axis2config.html Sun May 14 22:51:17 2006
@@ -0,0 +1,423 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+ <meta http-equiv="content-type" content="">
+ <title>Axis2 Configuration Documents</title>
+</head>
+
+<body lang="en">
+<h1>Axis2 Configuration Guide</h1>
+
+<p>In Axis2 there are three kinds of configuration files to configure the
+system. First one is to configure whole system (global configuration), second
+one is to configure a service (service configuration) and the third one is to
+configure a module (module configuration). This document will explain in
+detail the above configurations.</p>
+
+<h2>Content</h2>
+<ul>
+ <li><a href="#Global_Configuration">Global Configuration
+ (axis2.xml)</a></li>
+ <li><a href="#Service_Configuration">Service Configuration
+ (services.xml)</a></li>
+ <li><a href="#Module_Configuration">Module Configuration
+ (module.xml)</a></li>
+</ul>
+
+<h2><a name="Global_Configuration">Global Configuration</a></h2>
+<ul>
+ <li>Writing axis2.xml</li>
+</ul>
+
+<p>All the configuration that requires starting axis2 is obtained from
+axis2.xml. The way of specifying them is very simple and easy. The document
+is all about the proper way of specifying the configurations in axis2.xml.
+There are six top level elements that can be seen in the configuration file
+and those can be listed as follows;</p>
+<ul>
+ <li>Parameter</li>
+ <li>Transport Receiver</li>
+ <li>Transport Sender</li>
+ <li>Phase Order</li>
+ <li>Module References</li>
+ <li>Listeners (Observers)</li>
+</ul>
+
+<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;</p>
+<source><pre>
+ <parameter name="name of the parameter" >parameter value </parameter></pre>
+</source>
+<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;</p>
+<pre>
+<transportReceiver name="http" class="org.apache.axis2.transport.http.SimpleHTTPServer">
+ <parameter name="port" >6060</parameter>
+ </transportReceiver>
+ </pre>
+</source>The above elements shows the way of defining transport receivers in
+axis2.xml , here name attribute of the 'transportReceiver' element is the
+name of transport it can be http, tcp , smtp , commonshttp stc , and when the
+system starts up or when setting transport at the client side one can use
+these transport names to load the appropriate transport. Class attribute is
+to specify actual java class which implements required interfaces for the
+transport. Any transport can have zero or more parameters, and if there are
+any, then those parameters can be accessed via the corresponding transport
+receiver.
+
+<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:</p>
+
+<p><source></p>
+<pre>
+<transportSender name="http" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
+ <parameter name="PROTOCOL" locked="xsd:false">HTTP/1.0</parameter>
+ </transportSender>
+ </pre>
+</source>name: Name of the transport (it is possible to have http and http1
+as transport name) Class: Implementation class of the corresponding
+transport. As same as transport receivers, transport senders can have zero or
+more parameters, and if there is any then it can be accessed via
+corresponding transport sender.
+
+<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;</p>
+
+<p><source></p>
+<pre><phaseOrder type="inflow">
+ <phase name="TransportIn"/>
+ .
+ .
+</phaseOrder> </pre>
+</source>The most interesting thing is that you can add handlers here as well
+, if you want to add a handler which should go in to that phase you can
+directly do that by adding a handler element into it . In addition to that
+there is no any hard coding stuffs for handler chain in anywhere in Axis2
+(at any Axis*) , so all those configuration are also done here in phase order
+element. The complete configuration will look like as follows; <source>
+<pre><phaseOrder type="inflow">
+ <!-- System pre defined phases -->
+ <phase name="Transport">
+ <handler name="RequestURIBasedDispatcher"
+ class="org.apache.axis2.engine.RequestURIBasedDispatcher">
+ <order phase="Dispatch"/>
+ </handler>
+ <handler name="SOAPActionBasedDispatcher"
+ class="org.apache.axis2.engine.SOAPActionBasedDispatcher">
+ <order phase="Dispatch"/>
+ </handler>
+ </phase>
+ <phase name="Security"/>
+ <phase name="PreDispatch"/>
+ <phase name="Dispatch" class="org.apache.axis2.engine.DispatchPhase">
+ <handler name="AddressingBasedDispatcher"
+ class="org.apache.axis2.engine.AddressingBasedDispatcher">
+ <order phase="Dispatch"/>
+ </handler>
+
+ <handler name="SOAPMessageBodyBasedDispatcher"
+ class="org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher">
+ <order phase="Dispatch"/>
+ </handler>
+ <handler name="InstanceDispatcher"
+ class="org.apache.axis2.engine.InstanceDispatcher">
+ <order phase="PostDispatch"/>
+ </handler>
+ </phase>
+ <!-- System pre defined phases -->
+ <!-- After Postdispatch phase module author or or service author can add any phase he want -->
+ <phase name="OperationInPhase"/>
+ </phaseOrder>
+ <phaseOrder type="outflow">
+ <!-- user can add his own phases to this area -->
+ <phase name="OperationOutPhase"/>
+ <!--system predefined phase-->
+ <!--these phase will run irrespective of the service-->
+ <phase name="PolicyDetermination"/>
+ <phase name="MessageOut"/>
+ </phaseOrder>
+ <phaseOrder type="INfaultflow">
+ <phase name="PreDispatch"/>
+ <phase name="Dispatch" class="org.apache.axis2.engine.DispatchPhase">
+ <handler name="RequestURIBasedDispatcher"
+ class="org.apache.axis2.engine.RequestURIBasedDispatcher">
+ <order phase="Dispatch"/>
+ </handler>
+
+ <handler name="SOAPActionBasedDispatcher"
+ class="org.apache.axis2.engine.SOAPActionBasedDispatcher">
+ <order phase="Dispatch"/>
+ </handler>
+
+ <handler name="AddressingBasedDispatcher"
+ class="org.apache.axis2.engine.AddressingBasedDispatcher">
+ <order phase="Dispatch"/>
+ </handler>
+
+ <handler name="SOAPMessageBodyBasedDispatcher"
+ class="org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher">
+ <order phase="Dispatch"/>
+ </handler>
+ <handler name="InstanceDispatcher"
+ class="org.apache.axis2.engine.InstanceDispatcher">
+ <order phase="PostDispatch"/>
+ </handler>
+ </phase>
+ <!-- user can add his own phases to this area -->
+ <phase name="OperationInFaultPhase"/>
+ </phaseOrder>
+ <phaseOrder type="Outfaultflow">
+ <!-- user can add his own phases to this area -->
+ <phase name="OperationOutFaultPhase"/>
+ <phase name="PolicyDetermination"/>
+ <phase name="MessageOut"/>
+ </phaseOrder></pre>
+</source>
+<p>type: the attribute represent type of the flow and which can only be one
+of the following</p>
+<ul>
+ <li>inflow</li>
+ <li>outflow</li>
+ <li>INfaultflow</li>
+ <li>Outfaultflow</li>
+</ul>
+
+<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;</p>
+
+<p><source></p>
+<pre> <phase name="Transport"/></pre>
+</source>name: Name of the phase. <br>
+There are number of things that one has to keep in mind when changing
+pahseOrder,
+<ul>
+</ul>
+<ol>
+ there are phases called system pre-defined phases in all four flows;</ol>
+<ol>
+ You are not allowed change those , and you can add new phase after system
+ pre-defined phase</ol>
+<ol>
+ If you closely look at the default axis2.xml can clearly identify that.</ol>
+
+<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:</p>
+
+<p><source></p>
+<pre><module ref="addressing"/> </pre>
+</source>ref: the module name which is going to be engage, system wide.
+
+<p><strong>Listeners (Observers)</strong></p>
+
+<p>In Axis2 AxisConfiguration is observable so that one can register
+observers into that, and they will be automatically informed whenever a
+change occurs in AxisConfiuration. In the current implementation the
+observers are informed of the following events</p>
+<ul>
+ <li>Deploying a Service</li>
+ <li>Removing a service</li>
+ <li>Activate/Inactivate Service</li>
+ <li>Module deploy</li>
+ <li>Module remove</li>
+</ul>
+Registering Observers is very useful for additional features such as RSS feed
+generation which will provide service information to subscribers. The correct
+way of registering observers should be like below; <source>
+<pre><listener class="org.apache.axis2.ObserverIMPL">
+ <parameter name="RSS_URL" >http://127.0.0.1/rss</parameter>
+ </listener></pre>
+</source>class: Represent an Implementation class of observer, and it should
+be note that the implementation class should implement AxisObserver
+interface, and the class has to be available in the classpath. <a
+name="Service_Configuration"></a>
+
+<h2><font>Service Configuration</font></h2>
+<ul>
+ <li><font>Writing services.xml</font></li>
+</ul>
+
+<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></p>
+<source><pre><font><service name="name of the service" scope="name of the scope" targetNamespace="target namespase for the service">
+ <description> The description of the service </description>
+
+ <transports>
+ <transport>HTTP</transport>
+ </transports>
+
+ <schema schemaNamespace="schema namespace"/>
+
+ <messageReceivers>
+ <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"
+ class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
+ </messageReceivers>
+
+ <parameter name="ServiceClass" locked="xsd:false">org.apache.axis2.sample.echo.EchoImpl</parameter>
+
+ <operation name="echoString" mep="operation MEP">
+ <actionMapping>Mapping to action</actionMapping>
+ <module ref=" a module name "/>
+ <messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
+ </operation>
+ </service></font></pre>
+</source><font><em><strong>name</strong></em>: the service name will be the
+name of the archive file if the .aar file contains only one service else name
+of the service will be the name given by the name attribute</font>
+
+<p><em><strong>scope</strong></em> : Scope that the service need to be
+deployed and scope can be one of
+"Application","SOAPSession","TransportSession","Request";</p>
+
+<p><em><strong>targetNamespace</strong></em> : Target name space of the
+service , and this value will be used when generation wsdl</p>
+
+<p></p>
+
+<p><font><strong>description</strong>: 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>
+
+<p><strong>transports</strong> : The transports that the service is going to
+be exposed , this is an optional element . If the transports element is not
+present then the service will be exposed in every transports available in the
+system. The transport child element is to specify the transport prefix (the
+name of the transport specified in axis2.xml)</p>
+
+<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 AxisService. 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>Operations</b><br>
+If the service impl class is java then all the public methods in that service
+will be exposed and if user wants to override then he has to add operation
+tag and override that . In the case of Non-Java case or if you does not have
+service class then all the operations user wants to expose by the service has
+to be indicated in the services.xml and the correct way of specifying that
+should be as follows:</p>
+<pre> <operation name="echoString">
+ <module ref=" a module name "/>
+ <messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
+ </operation></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>
+<a name="Module_Configuration"></a>
+
+<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:</p>
+
+<p><source></p>
+<pre><module class="org.apache.module.Module1Impl">
+ <inflow>
+ .
+ .
+ </inflow>
+ <outflow>
+ .
+ .
+ </outflow>
+
+ <Outfaultflow>
+ .
+ .
+ </Outfaultflow>
+
+ <INfaultflow>
+ .
+ .
+ </INfaultflow>
+
+ <operation name="creatSeq" mep="MEP_URI_IN_OUT">
+ <messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
+ <parameter name="para1" locked="xsd:true">10</parameter>
+ </operation>
+</module></pre>
+</source>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 implementation class which implements the
+org.apache.axis2.modules.Module interface where at the deployment time its
+init(); method will be called.
+
+<p><b>parameter:</b> Module can contains any number of parameters and all the
+listed parameters in the module.xml will be transformed into corresponding
+AxisModule of the module.</p>
+
+<p><b>Flow :</b></p>
+
+<p>Defining of handlers in a module has to done inside Flows , and there are
+four types of flows as listed below.</p>
+
+<p>It is possible to add any number of handlers into a flow and those
+handlers will be available in corresponding chains at the runtime when they
+engaged .</p>
+<ul>
+ <li>Inflow</li>
+ <li>outflow</li>
+ <li>INfaultflow</li>
+ <li>Outfaultflow</li>
+</ul>
+
+<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>
+
+<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;</p>
+
+<p><source></p>
+<pre><handler name="handler1" class="handlerClass ">
+ <order phase="userphase1" />
+ </handler></pre>
+</source>
+<p><b><i>Compulsory attributes</i></b> <br>
+name: name of the handler<br>
+class: 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>
+before : the handler should be invoked before the handler specified by before
+handler<br>
+after: the handler should be invoked after the handler specified by after
+handler<br>
+</p>
+
+<p><br>
+</p>
+</body>
+</html>
Added: 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=406543&view=auto
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/http-transport.html (added)
+++ webservices/axis2/trunk/java/xdocs/latest/http-transport.html Sun May 14 22:51:17 2006
@@ -0,0 +1,173 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+ <meta http-equiv="content-type" content="">
+ <title>HTTP transports</title>
+</head>
+
+<body lang="en">
+<h1><a name="configTransport">HTTP Transport</a></h1>
+
+<p>This document is all about HTTP sender and HTTP receiver, and how they
+work in Axis2.</p>
+
+<p><i>Send your feedback or questions to: <a
+href="mailto:axis-dev@ws.apache.org">axis-dev@ws.apache.org</a></i>. Prefix
+subject with [Axis2]. To subscribe to mailing list see <a
+href="http://ws.apache.org/axis2/mail-lists.html">here.</a></p>
+
+<h2>Content</h2>
+<ul>
+ <li><a href="#CommonsHTTPTransportSender">CommonsHTTPTransportSender</a>
+ <ul>
+ <li><a href="#httpsupport">HTTPS support</a></li>
+ </ul>
+ </li>
+ <li><a href="#timeout_config">Timeout Configuration</a></li>
+ <li><a href="#version_config">HTTP Version Configuration</a></li>
+ <li><a href="#auth">Proxy and NTLM Authentication</a></li>
+</ul>
+<a name="CommonsHTTPTransportSender"></a>
+
+<h2>CommonsHTTPTransportSender</h2>
+
+<p>This is the default transport sender that is used in Server API as well as
+Client API. As the name implies it is based on commons-httpclient-3.0-rc3. In
+order to acquire the maximum flexibility, this sender has implemented POST
+interface and GET interface. GET interface is provided to help axis2 support
+REST.</p>
+
+<p>Chunking support and KeepAlive support is also integrated via the
+facilities provided by commons-httpclient along with HTTP 1.1 support.</p>
+
+<p><transportSender/> element is used to define transport senders in
+the axis2.xml as follows:</p>
+<pre><transportSender name="http" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"><br> <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter><br> <parameter name="Transfer-Encoding">chunked</parameter><br></transportSender><br></pre>
+
+<p>Above code snippet shows the complete configuration of the transport
+sender. <parameter/> element introduces the additional parameters that
+should be compliant with the sender. HTTP PROTOCOL version sets as HTTP/1.0
+or HTTP/1.1. Default version is HTTP/1.1. It should be noted that chunking
+support is available only for HTTP/1.1. Thus, the user should be careful in
+setting the "chunked" property and use it only with version 1.1. KeepAlive
+property is default in version 1.1.</p>
+
+<p>These are the only parameters that are available from deployment. Other
+parameters such as character encoding style (UTF-8, UTF-16 etc) etc, are
+provided via MessageContext.</p>
+<a name="httpsupport"></a>
+
+<h3>HTTPS support</h3>
+It should be noted that CommonsHTTPTransportSender can be used to communicate
+over https. <code></code>
+<pre><transportSender name="<b>https</b>" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"><br> <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter><br> <parameter name="Transfer-Encoding">chunked</parameter><br></transportSender><br></pre>
+
+<p>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.</p>
+<a name="timeout_config"></a>
+
+<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
+in run time. In deployment time, user has to add the following lines in
+axis2.xml.</p>
+
+<p>For Socket timeout:</p>
+<pre><parameter name="SO_TIMEOUT" locked="false">some_int_value</parameter></pre>
+
+<p>For Connection timeout:</p>
+<pre> <parameter name="CONNECTION_TIMEOUT" locked="false">some_int_value</parameter></pre>
+<br>
+In runtime it's set as follows in the Stub. <source>
+<pre>...
+Options options = new Options();
+options.setProperty(HTTPConstants.SO_TIMEOUT,new Integer(some_int_value));
+options.setProperty(HTTPConstants.CONNECTION_TIMEOUT,new Integer(some_int_value));
+...</pre>
+</source><a name="version_config"></a>
+
+<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> <parameter name="PROTOCOL" locked="false">HTTP/1.0</parameter></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>
+<a name="auth"></a>
+
+<h2>Proxy and NTLM Authentication</h2>
+
+<p>HttpClient support "Basic, Digest and NTLM" authentication schemes. These
+are used to authenticate with http servers and proxies.</p>
+
+<p>Axis2 uses deployment time and runtime mechanisms to authenticate proxies.
+In deployment time, user has to change the Axis2.xml as follows. This
+authentication will be available in http and https.</p>
+<pre><transportSender name="<b>http</b>" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
+ <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>
+ <parameter name="PROXY" proxy_host="proxy_host_name" proxy_port="proxy_host_port" locked="true>userName:domain:passWord</parameter>
+</transportSender><br></pre>
+
+<p>For a particular proxy, if authentication is not available fill
+"userName:domain:passWord"as "anonymous:anonymous:anonymous".</p>
+
+<p>At runtime user can override the PROXY settings with an Object of
+HttpTransportProperties.ProxyProperties. On the stub initiate an object of
+prior and set it to the MessageContext's property bag via
+HttpConstants.PROXY. On the stub, it depicts as follows,</p>
+<pre>...
+Options options = new Options();
+....
+
+HttpTransportProperties.ProxyProperties proxyProperties = new HttpTransportProperties.new ProxyProperties();
+proxyProperties.setProxyHostName(....);
+proxyProperties.setProxyPort(...);
+...
+options.setProperty(HttpConstants.PROXY, proxyProperties);
+....</pre>
+
+<p>The above code would eventually override the deployment proxy
+configuration settings.</p>
+
+<p>NTLM is the most complex of the authentication protocols supported by
+HttpClient. It requires an instance of NTCredentials be available for the
+domain name of the server or the default credentials. Note that since NTLM
+does not use the notion of realms HttpClient uses the domain name of the
+server as the name of the realm. Also note that the username provided to the
+NTCredentials should not be prefixed with the domain - ie: "axis2" is correct
+whereas "DOMAIN\axis2" is not correct.</p>
+
+<p>There are some significant differences in the way that NTLM works compared
+with basic and digest authentication. These differences are generally handled
+by HttpClient, however having an understanding of these differences can help
+avoid problems when using NTLM authentication.</p>
+<ol>
+ <li>NTLM authentication works almost exactly the same as any other form of
+ authentication in terms of the HttpClient API. The only difference is
+ that you need to supply 'NTCredentials' instead of
+ 'UsernamePasswordCredentials' (NTCredentials actually extends
+ UsernamePasswordCredentials so you can use NTCredentials right throughout
+ your application if need be).</li>
+ <li>The realm for NTLM authentication is the domain name of the computer
+ being connected to, this can be troublesome as servers often have
+ multiple domain names that refer to them. Only the domain name that
+ HttpClient connects to (as specified by the HostConfiguration) is used to
+ look up the credentials. It is generally advised that while initially
+ testing NTLM authentication, you pass the realm in as null which is used
+ as the default.</li>
+ <li>NTLM authenticates a connection and not a request, so you need to
+ authenticate every time a new connection is made and keeping the
+ connection open during authentication is vital. Due to this, NTLM cannot
+ be used to authenticate with both a proxy and the server, nor can NTLM be
+ used with HTTP 1.0 connections or servers that do not support HTTP
+ keep-alives.</li>
+</ol>
+</body>
+</html>
Added: webservices/axis2/trunk/java/xdocs/latest/images/Architecture.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/Architecture.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/Architecture.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/AxisService.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/AxisService.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/AxisService.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/Component.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/Component.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/Component.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/OM001.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/OM001.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/OM001.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/OM002.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/OM002.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/OM002.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/OM003.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/OM003.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/OM003.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/OM004.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/OM004.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/OM004.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/OM005.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/OM005.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/OM005.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/OM006.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/OM006.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/OM006.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/OM007.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/OM007.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/OM007.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/OM008.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/OM008.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/OM008.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/OM1.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/OM1.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/OM1.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/ServerSideFault.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/ServerSideFault.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/ServerSideFault.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/ServiceDesc.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/ServiceDesc.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/ServiceDesc.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/TotalArch.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/TotalArch.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/TotalArch.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/WomBuilder.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/WomBuilder.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/WomBuilder.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/activate.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/activate.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/activate.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/admin.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/admin.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/admin.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/adminlogin.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/adminlogin.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/adminlogin.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/adminmain.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/adminmain.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/adminmain.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/ant.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/ant.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/ant.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/CodegenArchitecture.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/CodegenArchitecture.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/CodegenArchitecture.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/all.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/all.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/all.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/big-picture.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/big-picture.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/big-picture.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/contexts.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/contexts.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/contexts.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/phases.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/phases.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/phases.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/soap-processing.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/soap-processing.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/soap-processing.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/soap.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/soap.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi-guide/soap.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi001.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi001.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi001.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi002.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi002.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi002.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi003.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi003.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi003.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi004.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi004.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi004.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi005.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi005.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi005.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi006.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi006.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi006.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi007.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi007.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi007.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi008.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi008.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi008.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi009.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi009.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi009.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi010.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi010.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi010.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi011.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi011.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi011.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi012.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi012.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi012.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi013.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi013.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi013.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi014.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi014.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi014.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi015.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi015.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi015.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi016.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi016.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi016.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi017.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi017.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi017.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi018.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi018.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi018.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi019.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi019.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi019.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi020.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi020.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi020.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi021.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi021.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi021.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi022.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi022.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi022.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi023.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi023.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi023.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi024.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi024.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi024.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi025.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi025.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi025.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/archi026.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/archi026.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/archi026.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/arrow_left.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/arrow_left.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/arrow_left.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/arrow_right.gif
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/arrow_right.gif?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/arrow_right.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/axis.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/axis.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/axis.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/ayncresult.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/ayncresult.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/ayncresult.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/call.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/call.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/call.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/callback.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/callback.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/callback.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/cases.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/cases.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/cases.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/clientAPi.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/clientAPi.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/clientAPi.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/clientside.png
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/clientside.png?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/clientside.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/clip_image002.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/clip_image002.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/clip_image002.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/clip_image004.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/clip_image004.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/clip_image004.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/clip_image006.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/clip_image006.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/clip_image006.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/clip_image008.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/clip_image008.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/clip_image008.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/clip_image010.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/clip_image010.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/clip_image010.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/clip_image012.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/clip_image012.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/clip_image012.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/clip_image014.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/clip_image014.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis2/trunk/java/xdocs/latest/images/clip_image014.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: webservices/axis2/trunk/java/xdocs/latest/images/clip_image016.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/images/clip_image016.jpg?rev=406543&view=auto
==============================================================================
Binary file - no diff available.