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/01/20 08:10:13 UTC
svn commit: r370748 [3/3] - in /webservices/axis2/trunk/java/xdocs/0_94:
installationguide.html userguide.html userguide1.html userguide2.html
userguide3.html userguide4.html userguide5.html
Modified: webservices/axis2/trunk/java/xdocs/0_94/userguide1.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/userguide1.html?rev=370748&r1=370747&r2=370748&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/userguide1.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/userguide1.html Thu Jan 19 23:10:02 2006
@@ -6,8 +6,7 @@
</head>
<body lang="en-US" dir="ltr">
-<a name="Axis2_User's_Guide"/>
-<h4>Axis2 User's Guide</h4>
+<h4><a name="Axis2_User's_Guide">Axis2 User's Guide</a></h4>
<p><i>Version 0.94</i></p>
<i>User Feedback: <a
@@ -19,15 +18,13 @@
href="userguide4.html" target="_blank">4</a>, <a href="userguide5.html"
target="_blank">5</a></p>
-<a name="Introduction"/>
-<h2>Introduction</h2>
+<h2><a name="Introduction">Introduction</a></h2>
<p>Welcome to Axis2, the next generation of Apache Axis!!! This User's Guide
will help you to understand what Axis2 has to offer and how to get started
with it. We hope you will benefit from the power of Axis2.</p>
-<a name="Attention"/>
-<h3>Attention</h3>
+<h3><a name="Attention">Attention</a></h3>
<ul>
<li><p style="margin-bottom: 0in">This User's Guide is written based on
Axis2 standard binary distribution. (The standard binary distribution can
@@ -42,8 +39,7 @@
</li>
</ul>
-<a name="What_is_Axis2_"/>
-<h3>What is Axis2?</h3>
+<h3><a name="What_is_Axis2_">What is Axis2?</a></h3>
<p>Axis2 is the next generation of Apache Axis. In late August 2004, during
the Axis2 Summit held in Colombo, Sri Lanka, a new architecture for Axis was
@@ -55,75 +51,74 @@
<p>After months of continued discussion and coding in this direction, Axis2
now delivers the following key features:</p>
<ul>
- <li><strong>Speed</strong> - Axis2 uses its
+ <li><p style="margin-bottom: 0in"><strong>Speed</strong> - Axis2 uses its
own object model and StAX (Streaming API for XML) parsing to achieve
- significantly greater speed than earlier versions of Apache Axis.
+ significantly greater speed than earlier versions of Apache Axis.</p>
</li>
- <li><strong>Low memory foot print</strong>-
- Axis2 was designed ground-up keeping low memory foot print in mind.
+ <li><p style="margin-bottom: 0in"><strong>Low memory foot print</strong>-
+ Axis2 was designed ground-up keeping low memory foot print in mind.</p>
</li>
- <li><strong>AXIOM</strong> - Axis2 comes with
+ <li><p style="margin-bottom: 0in"><strong>AXIOM</strong> - Axis2 comes with
its own light-weight object model, AXIOM, for message processing which is
- extensible, high performance and developer convenient
+ extensible, high performance and developer convenient</p>
</li>
- <a name="Hot_Deployment"/>
- <li><strong>Hot
- Deployment</strong> - Axis2 is equipped with the capability of
+ <li><p style="margin-bottom: 0in"><strong><a name="Hot_Deployment">Hot
+ Deployment</a></strong> - Axis2 is equipped with the capability of
deploying web service & handlers while system is up and running. In
other words, new services can be added to the system without having to
shut down server.Drop the required Web service archive into the services
directory in the repository and deployment model will automatically
- deploy the service and make it available for use.
+ deploy the service and make it available for use.</p>
</li>
- <li><strong>Asynchronous Web
+ <li><p style="margin-bottom: 0in"><strong>Asynchronous Web
Services</strong> - Axis2 now supports asynchronous web services &
asynchronous web services invocation using non-blocking clients and
- transports .
+ transports .</p>
</li>
- <li><strong>MEP Support</strong> - Axis2 now
+ <li><p style="margin-bottom: 0in"><strong>MEP Support</strong> - Axis2 now
comes handy with the flexibility to support Message Exchange Patterns
- (MEPs) with in-built support for basic MEPs defined in WSDL 2.0.
+ (MEPs) with in-built support for basic MEPs defined in WSDL 2.0.</p>
</li>
- <li><strong>Flexibility</strong> - The Axis2
+ <li><p style="margin-bottom: 0in"><strong>Flexibility</strong> - The Axis2
architecture gives the developer complete freedom to insert extensions
into the engine for custom header processing, system management, or
- <em>anything else you can imagine</em>.
+ <em>anything else you can imagine</em>.</p>
</li>
- <li><strong>Stability</strong> - Axis2
+ <li><p style="margin-bottom: 0in"><strong>Stability</strong> - Axis2
defines a set of published interfaces which change relatively slowly
- compared to the rest of Axis.
+ compared to the rest of Axis.</p>
</li>
- <li><strong>Component-oriented
+ <li><p style="margin-bottom: 0in"><strong>Component-oriented
Deployment</strong> - You can easily define reusable networks of Handlers
to implement common patterns of processing for your applications, or to
- distribute to partners.
+ distribute to partners.</p>
</li>
- <li><strong>Transport Framework</strong> - We
+ <li><p style="margin-bottom: 0in"><strong>Transport Framework</strong> - We
have a clean and simple abstraction for integrating and using Transports
(i.e., senders and listeners for SOAP over various protocols such as
SMTP, FTP, message-oriented middleware, etc), and the core of the engine
- is completely transport-independent.
+ is completely transport-independent.</p>
</li>
- <li><strong>WSDL support</strong> - Axis2
+ <li><p style="margin-bottom: 0in"><strong>WSDL support</strong> - Axis2
supports the <a href="http://www.w3.org/TR/wsdl" target="_blank">Web Service Description
Language</a>, version 1.1 and 2.0, which allows you to easily build stubs
to access remote services, and also to automatically export
- machine-readable descriptions of your deployed services from Axis2.
+ machine-readable descriptions of your deployed services from Axis2.</p>
</li>
- <li><strong>Add-ons</strong> Several web
+ <li><p style="margin-bottom: 0in"><strong>Add-ons</strong> Several web
services specifications have been incorporated including <a
href="http://ws.apache.org/wss4j/" target="_blank">WSS4J</a> for security, <a
href="http://ws.apache.org/sandesha/" target="_blank">Sandesha</a> for reliable
messaging, <a href="http://ws.apache.org/kandula/" target="_blank">Kandula</a> which is
an encapsulation of WS-Coordination, WS-AtomicTransaction and
- WS-BusinessActivity.
+ WS-BusinessActivity.</p>
</li>
- <li><strong>Composition and
+ <li><p style="margin-bottom: 0in"><strong>Composition and
Extensibility</strong> - modules and phases improve support for
composability and extensibility. Modules supports composability and is
able to add support for new WS-* specifications in a simple and clean
manner. They are however not <a href="#Hot_Deployment">hot deployable</a>
- as they change the overall behavior of the system.
+ as they change the overall behavior of the system.</p>
</li>
</ul>
@@ -138,9 +133,8 @@
href="mailto:axis-user@ws.apache.org">axis-user@ws.apache.org</a>" and make
sure to prefix the subject of the mail with [Axis2].</p>
-<a name="Axis2_Complete_Features_List"/>
-<h3>Axis2 Complete Features
-List</h3>
+<h3><a name="Axis2_Complete_Features_List">Axis2 Complete Features
+List</a></h3>
<ol type="1">
<li>AXIOM, an XML object model working on StAX (Streaming API for XML)
parsing optimized for SOAP 1.1/1.2 Messages. This has complete XML
@@ -169,8 +163,8 @@
<li>Axis Data Binding - ADB (Framework and Schema Compiler)</li>
<li>Numerous bug fixes since last release</li>
</ol>
-<a name="Experimental_Features_List"/>
-<h4>Experimental Features List</h4>
+
+<h4><a name="Experimental_Features_List">Experimental Features List</a></h4>
<ol type="1">
<li>Sessions scoping for Application, SOAP, Transport and Request
levels</li>
@@ -181,9 +175,9 @@
<li>Generating ServiceClient for a given WSDL and invoke the corresponding
service using generated client.</li>
</ol>
-<a name="Major_Changes_Since_Last_Release"/>
-<h4>Major Changes Since Last
-Release</h4>
+
+<h4><a name="Major_Changes_Since_Last_Release">Major Changes Since Last
+Release</a></h4>
<ol type="1">
<li>Fixing of memory leaks</li>
<li>Client API changes , Introducing ServiceClient instead of MEPClient,
@@ -194,9 +188,9 @@
<li>Code generator improved to process multi-port WSDL's properly</li>
<li>Packing and unpacking options for the code generated classes</li>
</ol>
-<a name="Tools_included_in this_Release"/>
-<h3>Tools Included In This
-Release</h3>
+
+<h3><a name="Tools_included_in this_Release">Tools Included In This
+Release</a></h3>
<ol type="1">
<li>Axis2 Web Application (Web App)</li>
<li>WSDL2WS- <a href="CodegenTools-EclipsePlugin.html" target="_blank">Eclipse
@@ -210,8 +204,8 @@
IDEA plugin</a></li>
</ol>
<a href="http://ws.apache.org/axis2/download.cgi" target="_blank">Download</a> above plugins
-<a name="What's_still_to_do_"/>
-<h3>What's Still To Do?</h3>
+
+<h3><a name="What's_still_to_do_">What's Still To Do?</a></h3>
<p>See list of what we think needs to be done, and consider helping out if
you're interested & able!</p>
Modified: webservices/axis2/trunk/java/xdocs/0_94/userguide2.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/userguide2.html?rev=370748&r1=370747&r2=370748&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/userguide2.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/userguide2.html Thu Jan 19 23:10:02 2006
@@ -8,8 +8,7 @@
</head>
<body lang="en-US" dir="ltr">
-<a name="Axis2_User's_Guide"/>
-<h4>Axis2 User's Guide</h4>
+<h4><a name="Axis2_User's_Guide">Axis2 User's Guide</a></h4>
<p><i>Version 0.94</i></p>
<i>User Feedback: <a
@@ -25,13 +24,13 @@
guide we will look at how to write and deploy Web Services using Axis2. All
the user's guide samples are located in the <b>"samples/userguide/src"</b>
directory of the binary distribution.
-<a name="Web_Services_Using_Axis2"/>
-<h2>Web Services Using Axis2</h2>
+
+<h2><a name="Web_Services_Using_Axis2">Web Services Using Axis2</a></h2>
<p>Before starting, please check whether you have deployed the "axis2.war" in
your servlet container and it is working properly. (See <a
href="installationguide.html" target="_blank">Installation Guide</a>). User
-can select any of the following two ways of writing web services using
+can select any of the following two ways of writing web services using
Axis2. </p>
<ol>
<li><a href="#Writing_Web_Services_Using Axis2's_Primary_APIs">Use Axis2's primary interfaces (APIs) and implement
@@ -41,13 +40,11 @@
</li>
</ol>
- <a name="Writing_Web_Services_Using Axis2's_Primary_APIs"/>
-<h3>Writing Web
-Services Using Axis2's Primary APIs</h3>
-
- <a name="Creating_Web_Service__MyService_"/>
-<h4>Creating Web Service
-(MyService)</h4>
+<h3><a name="Writing_Web_Services_Using Axis2's_Primary_APIs">Writing Web
+Services Using Axis2's Primary APIs</a></h3>
+
+<h4><a name="Creating_Web_Service__MyService_">Creating Web Service
+(MyService)</a></h4>
<p>First let's see how we can write a simple Web Service (MyService) using
Axis2's primary interfaces and deploy it. For this purpose we will create a
@@ -61,26 +58,25 @@
package. As you can see, the two operations are very simple and need no
explanations on what they do. Now let's see how we can write the deployment
descriptors for the service and deploy it.</p>
-<a name="How_to_write_the_Web_Service_"/>
-<h4>How to write the Web
-Service?</h4>
+
+<h4><a name="How_to_write_the_Web_Service_">How to write the Web
+Service?</a></h4>
Writing a new Web Service with Axis2 involve four steps:
<ol>
- <li>Write the Implementation Class
+ <li><p style="margin-bottom: 0in">Write the Implementation Class</p>
</li>
- <li>Write a services.xml file to explain the
- Web Service
+ <li><p style="margin-bottom: 0in">Write a services.xml file to explain the
+ Web Service</p>
</li>
- <li>create a *.aar archive (Axis Archive) for
- the Web Service
+ <li><p style="margin-bottom: 0in">create a *.aar archive (Axis Archive) for
+ the Web Service</p>
</li>
- <li>Deploy the Web Service
+ <li><p>Deploy the Web Service</p>
</li>
</ol>
- <a name="Step1_:Write_the_Implementation_Class"/>
-<h4>Step1 :Write the
-Implementation Class</h4>
+<h4><a name="Step1_:Write_the_Implementation_Class">Step1 :Write the
+Implementation Class</a></h4>
<p>Provides a implementation class that provide the business logic for the
Web Service, it should have methods that match the operations in the Web
@@ -95,9 +91,8 @@
}
}</pre>
- <a name="Step2_:Write_the_services_xml_file"/>
-<h4>Step2 :Write the
-services.xml file</h4>
+<h4><a name="Step2_:Write_the_services_xml_file">Step2 :Write the
+services.xml file</a></h4>
<p>Axis2 uses "services.xml" to keep configurations for a Web Service. Each
Web Service deployed in Axis2 needs a "services.xml" containing the
@@ -147,15 +142,14 @@
<p>Note : name of the service is a compulsory attribute</p>
- <a name="Step3_:Create_the_Web_Service_Archive"/>
-<h4>Step3 :Create the Web
-Service Archive</h4>
+<h4><a name="Step3_:Create_the_Web_Service_Archive">Step3 :Create the Web
+Service Archive</a></h4>
<p>Axis2 use ".aar" (Axis Archive) file as the deployment package for Web
Services. Therefore, for MyService we will use "MyService.aar" with the
"services.xml" packaged in the META-INF as shown in the following picture.</p>
-<p><img src="images/userguide/ServiceItems.jpg" name="Graphic1" alt=""
+<p><img src="images/userguide/ServiceItems.jpg" name="Graphic1"
align="bottom" width="176" height="91" border="0"></p>
<p>To create "MyService.aar" user can first create a jar file containing all
@@ -163,11 +157,10 @@
that Axis2 understands it as a service archive. This has already been created
in the "Axis2Home/samples/userguide" directory. Now let's use it...</p>
- <a name="Step4_:Deploy_the_Web_Service"/>
-<h4>Step4 :Deploy the Web
-Service</h4>
+<h4><a name="Step4_:Deploy_the_Web_Service">Step4 :Deploy the Web
+Service</a></h4>
-<p>Deploying the service is just a matter of dropping the ".aar" in to
+<p>Deploying the service is just a matter of dropping the ".aar" in to
"services" directory that can be found in the "\webapps\axis2\WEB-INF" of
your servlet container, hence copy the "MyService.aar" into the
"<b>services</b>" directory. Once these steps are completed, start the
@@ -178,7 +171,7 @@
deployed properly. If you can see the following output then you have
successfully deployed MyService on Axis2.</p>
-<p align="center"><img src="images/userguide/MyServiceDeployed.jpg" alt=""
+<p align="center"><img src="images/userguide/MyServiceDeployed.jpg"
name="Graphic2" align="bottom" width="734" height="766" border="0"></p>
<p>Note: Axis2 provides an easy way to deploy Web Services using the "Upload
@@ -186,17 +179,15 @@
href="webadminguide.html" target="_blank">Web Administration Guide</a> for
more information on this)</p>
- <a name="Writing_Web_Services_by_Code_Generating_Skeleton"/>
-<h3>Writing Web
-Services by Code Generating Skeleton</h3>
+<h3><a name="Writing_Web_Services_by_Code_Generating_Skeleton">Writing Web
+Services by Code Generating Skeleton</a></h3>
<p>This is the second method of writing Web Services using Axis2. Let's see
how we can generate the skeleton from a given WSDL and implement the business
logic using Axis2. For this we use Axis2SampleDocLit.wsdl that can be found
in the <b>wsdl</b> directory under samples.</p>
- <a name="WSDL2Java_Tool"/>
-<h4>WSDL2Java Tool</h4>
+<h4><a name="WSDL2Java_Tool">WSDL2Java Tool</a></h4>
<p>To generate the skeleton and the required classes you can use the
WSDL2Java tool provided in Axis2. This tool is located in the bin directory
@@ -217,44 +208,50 @@
skeleton and the other required classes.</p>
<p>Windows users can use the following command in the console:</p>
-<pre style="margin-bottom: 0.2in">WSDL2Java -uri ..\samples\wsdl\Axis2SampleDocLit.wsdl -d xmlbeans -ss -sd -o ..\samples -p org.apache.axis2.userguide</pre>
+<pre style="margin-bottom: 0.2in">WSDL2Java -uri ..\samples\wsdl\Axis2SampleDocLit.wsdl -ss -sd -o ..\samples -p org.apache.axis2.userguide</pre>
<p>Linux users should switch the file separator:</p>
-<pre style="margin-bottom: 0.2in">WSDL2Java -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -d xmlbeans -ss -sd -o ../samples -p org.apache.axis2.userguide</pre>
+<pre style="margin-bottom: 0.2in">WSDL2Java -uri ../samples/wsdl/Axis2SampleDocLit.wsdl -ss -sd -o ../samples -p org.apache.axis2.userguide</pre>
<p>This will generate the required classes in the <b>src</b> directory inside
samples, and the schema classes in <strong>schema</strong> directory also
inside samples. Note that these are not source files and should be availed in
the class path in order to compile the generated classes</p>
- <a name="Implement_the_Business_Logic"/>
-<h4>Implement the Business Logic</h4>
+<h4><a name="Implement_the_Business_Logic">Implement the Business Logic</a></h4>
<p>Locate the skeleton class that can be found under src/userguide directory
with the name "Axis2SampleDocLitPortTypeSkeleton.java". This is the skeleton
for our web service and we can now easily implement the business logic. The
-WSDL we have used has three operations:<!--<li>echoVoid - Operation that does not
-accept any input parameters and also provide no out put parameters. Just
+WSDL we have used has three operations:<!--<li><p style="margin-bottom: 0in">echoVoid - Operation that does not
+accept any input parameters and also provide no out put parameters. Just
perform some task </p>
</li>-->
</p>
<ul>
- <li>echoString - Operation that echoes a
- String value
+ <li><p style="margin-bottom: 0in">echoString - Operation that echoes a
+ String value </p>
</li>
- <li>echoStringArray - Operation that accept
- string array as the input and echoes them back
+ <li><p style="margin-bottom: 0in">echoStringArray - Operation that accept
+ string array as the input and echoes them back</p>
</li>
- <li>echoStruct - Operation that accept a Struct as the input and echoes
- them back.
+ <li><p>echoStruct - Operation that accept a Struct as the input and echoes
+ them back.</p>
</li>
</ul>
+<!--<h4>echoVoid </h4>
- <a name="echoString"/>
-<h4>echoString</h4>
+<p>Locate the following code segment in the
+"Axis2SampleDocLitPortTypeSkeleton.java" and fill the business logic. For
+the explanation purpose we do not need anything to be implemented here.</p>
+<pre>public void echoVoid(){
+//Todo fill this with the necessary business logic
+}</pre> -->
-<p>Locate the following code segment in the
-"Axis2SampleDocLitPortTypeSkeleton.java" and fill the business logic as
+<h4><a name="echoString">echoString</a></h4>
+
+<p>Locate the following code segment in the
+"Axis2SampleDocLitPortTypeSkeleton.java" and fill the business logic as
shown below.</p>
<pre> public org.soapinterop.xsd.EchoStringArrayReturnDocument
echoStringArray(org.soapinterop.xsd.EchoStringArrayParamDocument param2){
@@ -276,8 +273,7 @@
<p>Similarly following code fragments shows how you can fill the business
logic for our first web service.</p>
- <a name="echoStringArray"/>
-<h4>echoStringArray</h4>
+<h4><a name="echoStringArray">echoStringArray</a></h4>
<pre>public org.soapinterop.xsd.EchoStringArrayReturnDocument
echoStringArray(org.soapinterop.xsd.EchoStringArrayParamDocument param2) {
@@ -297,8 +293,7 @@
return retDoc;
}</pre>
- <a name="echoStruct"/>
-<h4>echoStruct</h4>
+<h4><a name="echoStruct">echoStruct</a></h4>
<pre>public org.soapinterop.xsd.EchoStructReturnDocument
echoStruct(org.soapinterop.xsd.EchoStructParamDocument param4) {
@@ -320,10 +315,10 @@
return retDoc;
}</pre>
- <a name="services_xml"/>
-<h4>services.xml</h4>
-<p>Axis2 uses "services.xml" to hold the configurations for a particular web
+<h4><a name="services_xml">services.xml</a></h4>
+
+<p> Axis2 uses "services.xml" to hold the configurations for a particular web
service deployed in the Axis2 engine. When we generate the skeleton using the
WSDL2Java tool, it will also generate the required services.xml for this web
service as well. This can be found in the same directory as the skeleton. The
@@ -350,8 +345,7 @@
description and the service class. The next xml tags describe the operations
that are available in this service with respective message receivers.</p>
- <a name="Packaging"/>
-<h4>Packaging</h4>
+<h4><a name="Packaging">Packaging</a></h4>
<p>Next step in the process is to package the classes in a .aar (axis2
archive) and deploy it in Axis2. When the WSDL2Java tool generate the
@@ -362,7 +356,7 @@
following directory structure with the required files and then simply use jar
command to package it.</p>
-<p><img src="images/userguide/DirectoryStructure.JPG" align="bottom" alt=""
+<p><img src="images/userguide/DirectoryStructure.JPG" align="bottom"
width="164" height="142" border="0"></p>
<p>Go to the top level directory where you can find the class files for the
@@ -370,7 +364,7 @@
then type the following command in a command line.</p>
<pre style="margin-bottom: 0.2in">jar -cf Axis2SampleDocLitPortType.aar .</pre>
-<p>Deploying the service is just a matter of dropping the ".aar" in to
+<p>Deploying the service is just a matter of dropping the ".aar" in to
"services" directory that can be found in the "\webapps\axis2\WEB-INF" of
your servlet container, hence copy the "echo.aar" into the "<b>services</b>"
directory. Once these steps are completed, please start the servlet container
@@ -381,7 +375,7 @@
the following output then you have successfully deployed
Axis2SampleDocLitPortType on Axis2.</p>
-<p align="center"><img src="images/userguide/ServiceDeployed.JPG" alt=""
+<p align="center"><img src="images/userguide/ServiceDeployed.JPG"
name="Graphic4" align="bottom" width="734" height="764" border="0"></p>
<p>Note: Axis2 provides an easy way to deploy Web Services using the "Upload
@@ -391,7 +385,7 @@
<p align="right"><a href="userguide1.html" target="_blank"><img
src="images/arrow_left.gif"> Previous</a> | <a href="userguide3.html"
-target="_blank">Next <img src="images/arrow_right.gif" alt=""></a></p>
+target="_blank">Next <img src="images/arrow_right.gif"></a></p>
<p>Pages: <a href="userguide.html" target="_blank">Content</a>, <a
href="userguide1.html" target="_blank">1</a>, <b>2</b>, <a
Modified: webservices/axis2/trunk/java/xdocs/0_94/userguide3.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/userguide3.html?rev=370748&r1=370747&r2=370748&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/userguide3.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/userguide3.html Thu Jan 19 23:10:02 2006
@@ -8,8 +8,7 @@
</head>
<body lang="en-US" dir="ltr">
-<a name="Axis2_User's_Guide"/>
-<h4>Axis2 User's Guide</h4>
+<h4><a name="Axis2_User's_Guide">Axis2 User's Guide</a></h4>
<p><i>Version 0.94</i></p>
<i>User Feedback: <a
@@ -26,22 +25,22 @@
user's guide samples are located at the <b><font
color="#000000">"samples/userguide/src"</font></b> directory of the binary
distribution. So... let's explore the samples.</p>
-<a name="Web_Service_Clients_Using_Axis2"/>
-<h2>Web Service Clients Using Axis2</h2>
+
+<h2><a name="Web_Service_Clients_Using_Axis2">Web Service Clients Using Axis2</a></h2>
<p>Now let's see how we can write a Web Service Client to use this Web
Service.</p>
<p>Web services can be used to provide wide range of functionality to the
-users ranging from simple, less time consuming operations such as
-"getStockQuote" to time consuming business services. When we utilize (invoke
+users ranging from simple, less time consuming operations such as
+"getStockQuote" to time consuming business services. When we utilize (invoke
using client applications) these Web Service we cannot use some simple
generic invocation paradigm that suites all the timing complexities involved
in the service operations. For example, if we use a single transport channel
(such as HTTP) to invoke a Web Service with and IN-OUT operation that take
long time to complete, then most of the time we may end up with "connection
time outs". On the other hand, if there are simultaneous service invocations
-that we need to perform from a single client application, then the use of a
+that we need to perform from a single client application, then the use of a
"blocking" client API will degrade the performance of the client application.
Similarly there are various other consequences such as One-Way transports
that come in to play when we need them. Let's try to analyze some common
@@ -50,22 +49,22 @@
<p>Many web service engines provide the users with a Blocking and
Non-Blocking client APIs.</p>
<ul>
- <li><b>Blocking API</b> -Once the service
+ <li><p style="margin-bottom: 0in"><b>Blocking API</b> -Once the service
invocation is called, the client application hangs and only gets control
back when the operation completes, after which client receives a response
or a fault. This is the simplest way of invoking Web Services and it also
- suites many business situations.
+ suites many business situations.</p>
</li>
- <li><b>Non-Blocking API </b>- This is a callback or polling based API,
+ <li><p><b>Non-Blocking API </b>- This is a callback or polling based API,
hence once a service invocation is called, the client application
immediately gets the control back and the response is retrieved using the
callback object provided. This approach provides the flexibility to the
client application to invoke several Web Services simultaneously without
- blocking the operation already invoked.
+ blocking the operation already invoked.</p>
</li>
</ul>
-<p>Both these mechanisms work in the API level. Let's name the asynchronous
+<p>Both these mechanisms work in the API level. Let's name the asynchronous
behavior that we can get using the <strong>Non-Blocking API</strong> as
<b>API Level Asynchrony.</b></p>
@@ -90,7 +89,7 @@
<td width="33%" height="19"><p><strong>API
(Blocking/Non-Blocking)</strong></p>
</td>
- <td width="33%"><p><strong>Dual Transports (Yes/No)</strong></p>
+ <td width="33%"><p><strong> Dual Transports (Yes/No)</strong></p>
</td>
<td width="33%"><p><strong>Description</strong></p>
</td>
@@ -145,11 +144,11 @@
client applications</p>
</li>
</ol>
-<a name="Writing_Web_Service_Clients_using_Axis2's_Primary_APIs"/>
-<h3>Writing
-Web Service Clients Using Axis2's Primary APIs</h3>
-<a name="EchoBlockingClient"/>
-<h4>EchoBlockingClient</h4>
+
+<h3><a name="Writing_Web_Service_Clients_using_Axis2's_Primary_APIs">Writing
+Web Service Clients Using Axis2's Primary APIs</a></h3>
+
+<h4><a name="EchoBlockingClient">EchoBlockingClient</a></h4>
<p>Axis2 provides the user with several invocation patterns for Web Services,
ranging from pure blocking single channel invocations to a non-blocking dual
@@ -186,13 +185,13 @@
that needs to be sent and display the response OMElement. To test this
client, use the provided ant build file that can be found in the
"Axis2Home/samples" directory. Run the "testEchoBlockingClient" target . If
-you can see the response OMElement printed in your command line, then you
+you can see the response OMElement printed in your command line, then you
have successfully tested the client. </p>
-<a name="PingClient"/>
-<h4>PingClient</h4>
+
+<h4><a name="PingClient">PingClient</a></h4>
<p>In the Web Service "MyService" we had a IN-ONLY operation with the name
-"ping" (see <a href="userguide2.html#Web_Services_Using_Axis2" target="_blank">Web Services Using
+"ping" (see <a href="userguide2.html#Web_Services_Using_Axis2" tareget="_blank">Web Services Using
Axis2</a>). Let's write a client to invoke this operation. The client code is
as follows:</p>
<pre> try {
@@ -217,8 +216,8 @@
<p>We have invoked the two operations in our service. Are we done? No! There
are lot more to explore. Let's see some other ways to invoke the same
operations...</p>
- <a name="EchoNonBlockingClient"/>
-<h4>EchoNonBlockingClient</h4>
+
+<h4><a name="EchoNonBlockingClient">EchoNonBlockingClient</a></h4>
<p>In the EchoBlockingClient once the "serviceCleint.sendReceive(payload);"
is called, the client is blocked till the operation is completed. This
@@ -250,11 +249,11 @@
<p>To run the sample client ( EchoNonBlockingClient) you can simply use the
"testEchoNonBlockingClient" target of the ant file found at the
"Axis2Home/samples" directory.</p>
- <a name="EchoNonBlockingDualClient"/>
-<h4>EchoNonBlockingDualClient</h4>
+
+<h4><a name="EchoNonBlockingDualClient">EchoNonBlockingDualClient</a></h4>
<p>The solution provided by the Non-Blocking API has one limitation when it
-comes to Web Service invocations which takes long time to complete. The
+comes to Web Service invocations which takes long time to complete. The
limitation is due to the use of single transport connection to invoke the Web
Service and to retrieve the response. In other words, client API provides a
non blocking invocation mechanism for the users, but the request and the
@@ -269,7 +268,7 @@
<a href="http://www.w3.org/Submission/ws-addressing/"
target="_blank">WS-Addressing</a> provides a neat solution to this using
<wsa:MessageID> and <wsa:RelatesTo> headers. Axis2 provides
-support for addressing based correlation mechanism and a complying Client
+support for addressing based correlation mechanism and a complying Client
API to invoke Web Services with two transport connections. (Core of Axis2
does not depend on WS-Addressing, but contains a set of parameters like in
addressing that can be populated in any means. WS-Addressing is one of the
@@ -343,7 +342,7 @@
the Axis2 architecture, addressing module is deployed in the
"<strong>pre-dispatch</strong>" phase (See <a
href="Axis2ArchitectureGuide.html" target="_blank">Architecture Guide</a> for
-more details about phases) and hence "engaging" means simply adding module
+more details about phases) and hence "engaging" means simply adding module
reference in the "axis2.xml" (NOT the "services.xml"). Now add the following
line to the "axis2.xml" that you can find in the "/webapps/axis2/WEB-INF"
directory in the servlet container. </p>
@@ -358,8 +357,8 @@
response OMElement printed in the client side, then you have successfully
tested the Non Blocking API with two transport channels at the client
side.</p>
- <a name="EchoBlockingDualClient"/>
-<h4>EchoBlockingDualClient</h4>
+
+<h4><a name="EchoBlockingDualClient">EchoBlockingDualClient</a></h4>
<p>This is again a Two-Way transport request/response client, but this time,
we use a Blocking API in the client code. Sample code for this can be found
@@ -375,10 +374,10 @@
<p>See <a href="http-transport.html" target="_blank">Configuring
Transports</a> for use different transports.</p>
-<a
-name="Writing_Web_Service_Clients_using_Code_Generation_with_Data_Binding_Support"/>
-<h3>Writing
-Web Service Clients using Code Generation with Data Binding Support</h3>
+
+<h3><a
+name="Writing_Web_Service_Clients_using_Code_Generation_with_Data_Binding_Support">Writing
+Web Service Clients using Code Generation with Data Binding Support</a></h3>
<p>Axis2 provides the data binding support for Web Service client as well.
The user can generate the required stubs from a given WSDL with the other
@@ -393,9 +392,9 @@
see how we can use this stub to write Web Service clients to utilize the Web
Service Axis2SampleDocLitPortType (the service that we have already
deployed).</p>
- <a name="Client_for_echoVoid_Operation"/>
-<h4>Client for echoVoid
-Operation</h4>
+
+<h4><a name="Client_for_echoVoid_Operation">Client for echoVoid
+Operation</a></h4>
<p>Following code fragment shows the necessary code for utilizing the
echoVoid operation of the Axis2SampleDocLitPortType that we have already
@@ -411,9 +410,9 @@
} catch (Exception e) {
e.printStackTrace();
}</pre>
- <a name="Client_for_echoString_Operation"/>
-<h4>Client for echoString
-Operation</h4>
+
+<h4><a name="Client_for_echoString_Operation">Client for echoString
+Operation</a></h4>
<p>Following code fragment shows the necessary code for utilizing the
echoString operation of the Axis2SampleDocLitPortType that we have already
@@ -437,9 +436,9 @@
<p>Similarly following code fragments show client side code for
echoStringArray operation and echoStruct operation respectively.</p>
- <a name="Client_for_echoStringArray_Operation"/>
-<h4>Client for echoStringArray
-Operation</h4>
+
+<h4><a name="Client_for_echoStringArray_Operation">Client for echoStringArray
+Operation</a></h4>
<pre>try {
//Create the stub by passing the AXIS_HOME and target EPR.
//We pass null to the AXIS_HOME and hence the stub will use the current directory as the AXIS_HOME
@@ -465,9 +464,9 @@
} catch (Exception e) {
e.printStackTrace();
}</pre>
- <a name="Client_for_echoStruct_Operation"/>
-<h4>Client for echoStruct
-Operation</h4>
+
+<h4><a name="Client_for_echoStruct_Operation">Client for echoStruct
+Operation</a></h4>
<pre>try {
//Create the stub by passing the AXIS_HOME and target EPR.
//We pass null to the AXIS_HOME and hence the stub will use the current directory as the AXIS_HOME
@@ -499,7 +498,7 @@
<p align="right"><a href="userguide2.html" target="_blank"><img
src="images/arrow_left.gif"> Previous</a> | <a href="userguide4.html"
-target="_blank">Next <img src="images/arrow_right.gif" alt=""></a></p>
+target="_blank">Next <img src="images/arrow_right.gif"></a></p>
<p>Pages: <a href="userguide.html" target="_blank">Content</a>, <a
href="userguide1.html" target="_blank">1</a>, <a href="userguide2.html"
Modified: webservices/axis2/trunk/java/xdocs/0_94/userguide4.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/userguide4.html?rev=370748&r1=370747&r2=370748&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/userguide4.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/userguide4.html Thu Jan 19 23:10:02 2006
@@ -8,8 +8,7 @@
</head>
<body lang="en-US" dir="ltr">
-<a name="Axis2_User's_Guide"/>
-<h4>Axis2 User's Guide</h4>
+<h4><a name="Axis2_User's_Guide">Axis2 User's Guide</a></h4>
<p><i>Version 0.94</i></p>
<i>User Feedback: <a
@@ -23,8 +22,8 @@
<b><font size="4">Note (on samples):</font></b>All the user's guide samples
are located in the <b>"samples/userguide/src"</b> directory of the binary
distribution.
-<a name="Modules"/>
-<h2>Modules</h2>
+
+<h2><a name="Modules"></a>Modules</h2>
<p>Axis2 provides an extended support for modules (See <a
href="Axis2ArchitectureGuide.html" target="_blank">Architecture Guide</a> for more details
@@ -32,26 +31,26 @@
MyService which we created earlier. Following steps shows the actions that
need to be performed to deploy a custom module for a given Web Service:</p>
<ol>
- <li>Create the Module Implementation
+ <li><p style="margin-bottom: 0in">Create the Module Implementation</p>
</li>
- <li>Create the Handlers
+ <li><p style="margin-bottom: 0in">Create the Handlers</p>
</li>
- <li>Create the module.xml
+ <li><p style="margin-bottom: 0in">Create the module.xml</p>
</li>
- <li>Modify the "axis2.xml" (if you need
- custom phases)
+ <li><p style="margin-bottom: 0in">Modify the "axis2.xml" (if you need
+ custom phases)</p>
</li>
- <li>Modify the "services.xml" to engage
- modules at the deployment time.
+ <li><p style="margin-bottom: 0in">Modify the "services.xml" to engage
+ modules at the deployment time.</p>
</li>
- <li>Package in a ".mar" (Module Archive)
+ <li><p style="margin-bottom: 0in">Package in a ".mar" (Module Archive)</p>
</li>
- <li>Deploy the module in Axis2
+ <li><p>Deploy the module in Axis2</p>
</li>
</ol>
-<a name="MyService_with_a_Logging_Module"/>
-<h3>MyService with a Logging
-Module</h3>
+
+<h3><a name="MyService_with_a_Logging_Module">MyService with a Logging
+Module</a></h3>
<p>Let's write a simple logging module for our sample. This module contains
one handler that just logs the message that is passed through it. Axis2 uses
@@ -61,8 +60,8 @@
<p><img src="images/userguide/ModuleView.jpg" name="Graphic5" align="bottom"
width="185" height="120" border="0"></p>
- <a name="Step1_:_LoggingModule_Class"/>
-<h4>Step1 : LoggingModule Class</h4>
+
+<h4><a name="Step1_:_LoggingModule_Class">Step1 : LoggingModule Class</a></h4>
<p>LoggingModule is the implementation class of the Axis2 module. Axis2
modules should implement the "org.apache.axis2.modules.Module" interface with
@@ -75,8 +74,8 @@
the complete configuration hierarchy. This can be used to fine-tune the
module behavior using the module writers. For the simple logging service we
can keep these methods blank in our implementation class.</p>
- <a name="Step2_:_LogHandler"/>
-<h4>Step2 : LogHandler</h4>
+
+<h4><a name="Step2_:_LogHandler">Step2 : LogHandler</a></h4>
<p>A module in Axis2 can contain, one or more handlers that perform various
SOAP header processing at different phases. (See<a
@@ -106,8 +105,8 @@
this.name = name;
}
}</pre>
- <a name="Step3_:_module_xml"/>
-<h4>Step3 : module.xml</h4>
+
+<h4><a name="Step3_:_module_xml">Step3 : module.xml</a></h4>
<p>"module.xml" contains the deployment configurations for a particular
module. It contains details such as Implementation class of the module (in
@@ -142,17 +141,17 @@
<p>As it can be seen there are four phases defined in this "module.xml"</p>
<ol>
- <li>inflow - Represents the handler chain that will run when
+ <li>inflow - Represents the handler chain that will run when
a message is coming in. </li>
- <li>outflow - Represents the
- handler chain that will run when the message is going out.
+ <li><p style="margin-bottom: 0in">outflow - Represents the
+ handler chain that will run when the message is going out. </p>
</li>
- <li>Outfaultflow - Represents the
+ <li><p style="margin-bottom: 0in">Outfaultflow - Represents the
handler chain that will run when there is a fault and the fault is going
- out
+ out </p>
</li>
- <li>INfaultflow - Represents the handler chain that will run when
- there is a fault and the fault is coming in
+ <li><p>INfaultflow - Represents the handler chain that will run when
+ there is a fault and the fault is coming in </p>
</li>
</ol>
@@ -171,9 +170,9 @@
<p>To learn more on Phase rules, click on <a
href="http://www.developer.com/java/web/article.php/3529321"
target="_blank">here</a></p>
- <a name="Step_4:_Modify_the_"axis2_xml""/>
-<h4>Step 4: Modify the
-"axis2.xml"</h4>
+
+<h4><a name="Step_4:_Modify_the_"axis2_xml"">Step 4: Modify the
+"axis2.xml"</a></h4>
<p>In this handler the phase "loggingPhase" is defined by the module writer.
It is not a pre-defined handler phase, hence the module writer should
@@ -247,9 +246,9 @@
flows, hence that phase will be called in all the message flows in the
engine. Since our module is associated with this phase, the LogHandler inside
the module now will be executed in this phase.</p>
- <a name="Step5_:_Modify_the_"services_xml""/>
-<h4>Step5 : Modify the
-"services.xml"</h4>
+
+<h4><a name="Step5_:_Modify_the_"services_xml"">Step5 : Modify the
+"services.xml"</a></h4>
<p>Up to this point we have created the required classes and configuration
descriptions for the logging module and by changing the "axis2.xml" we have
@@ -283,16 +282,16 @@
the module "logging" should be engaged for this service. The handler inside
the module will be executed in their respective phases as described by the
"module.xml".</p>
- <a name="Step6_:_Packaging"/>
-<p><b>Step6 : Packaging</b></p>
+
+<p><b><a name="Step6_:_Packaging">Step6 : Packaging</a></b></p>
<p>Before deploying the module we need to create the ".mar" file for this
module. This can be done, using the "jar" command and then renaming the
created jar file. Or you can find the "Logging.mar" that is already created
for you in the "Axis2Home/samples/userguide" directory.</p>
- <a name="Step7_:_Deploy_the_Module_in_Axis2"/>
-<h4>Step7 : Deploy the Module in
-Axis2</h4>
+
+<h4><a name="Step7_:_Deploy_the_Module_in_Axis2">Step7 : Deploy the Module in
+Axis2</a></h4>
<p>Deploying a module in Axis2 require the user to create a directory with
the name "modules" in the "webapps/axis2/WEB-INF" directory of their servlet
@@ -302,9 +301,8 @@
<p>Although the required changes to the "services.xml" is very little, we
have created a separate service archive (MyServiceWithModule.aar) for users
-to deploy and see. Deploy this service using the
- <a href="userguide2.html#Step4_:Deploy_the_Web_Service">
- same steps that you used to deploy "MyService"</a> and copy the "LoggingModule.mar" file
+to deploy and see. Deploy this service using the <a href="userguide2.html#Step4_:Deploy_the_Web_Service"">same steps
+that you used to deploy "MyService"</a> and copy the "LoggingModule.mar" file
to the "modules" directory. Then run using the
"TestWebServiceWithModuleClient.bat" or "TestWebServiceWithModuleClient.sh"
in the "Axis2Home/samples/userguide/src/userguide/clients/bin" directory.</p>
@@ -314,9 +312,9 @@
your servlet container. Change the line "log4j.rootCategory= ERROR, LOGFILE"
to "log4j.rootCategory=INFO, ERROR, LOGFILE".</p>
-<p align="right"><a href="userguide3.html" target="_blank"><img alt=""
+<p align="right"><a href="userguide3.html" target="_blank"><img
src="images/arrow_left.gif"> Previous</a> | <a href="userguide5.html"
-target="_blank">Next <img src="images/arrow_right.gif" alt=""></a></p>
+target="_blank">Next <img src="images/arrow_right.gif"></a></p>
<p>Pages: <a href="userguide.html" target="_blank">Content</a>, <a
href="userguide1.html" target="_blank">1</a>, <a href="userguide2.html"
Modified: webservices/axis2/trunk/java/xdocs/0_94/userguide5.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/0_94/userguide5.html?rev=370748&r1=370747&r2=370748&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/0_94/userguide5.html (original)
+++ webservices/axis2/trunk/java/xdocs/0_94/userguide5.html Thu Jan 19 23:10:02 2006
@@ -8,8 +8,7 @@
</head>
<body lang="en-US" dir="ltr">
-<a name="Axis2_User's_Guide"/>
-<h4>Axis2 User's Guide</h4>
+<h4><a name="Axis2_User's_Guide">Axis2 User's Guide</a></h4>
<p><i>Version 0.94</i></p>
<i>User Feedback: <a
@@ -18,14 +17,13 @@
<p align="right">Pages: <a href="userguide.html"
target="_blank">Content</a>, <a href="userguide1.html" target="_blank">1</a>,
<a href="userguide2.html" target="_blank">2</a>, <a href="userguide3.html"
-target="_blank">3</a>, <a href="userguide4.html">4</a>, <b>5</b></p>
+target="_blank">3</a>, <a href="userguide4.html target=">4</a>, <b>5</b></p>
<p><font size="4"><b>Note (on samples):</b></font>All the user's guide
samples are located in the <b>"samples/userguide/src"</b> directory of the
binary distribution.</p>
-<a name="Other_Samples"/>
-<h2>Other Samples</h2>
+<h2><a name="Other_Samples">Other Samples</a></h2>
<p>To show the power of usage of Axis2, three standard samples are shipped
with the binary distribution. These are meant to interact with outside web
@@ -33,15 +31,15 @@
<p>The included samples are</p>
<ul>
- <li>Google spell checker sample</li>
- <li>Google search sample
+ <li><style="margin-bottom: 0in">Google spell checker sample</li>
+ <li><p style="margin-bottom: 0in">Google search sample</p>
</li>
- <li>Amazon queuing sample
+ <li><p style="margin-bottom: 0in">Amazon queuing sample</p>
</li>
</ul>
<p>A simple introduction to each of the above samples are given below. Each
-sample contains it's own help document that speaks about the usage and the
+sample contains it's own help document that speaks about the usage and the
advanced operations of that particular sample.</p>
<p>The most obvious place to look for the samples are the binary
@@ -56,31 +54,28 @@
shell scripts (or the batch files) then the AXIS_HOME environment need to be
set.( the "guessed" AXIS_HOME would not be correct in this case)</p>
- <a name="Google_Spell_Checker_Sample"/>
-<h3>Google Spell Checker Sample</h3>
+<h3><a name="Google_Spell_Checker_Sample">Google Spell Checker Sample</a></h3>
<p>This includes a spell checker program that uses the Google spell checking
service. It demonstrates the blocking and non-blocking modes of calling the
service. This sample can be found at the samples\googleSpellcheck directory
and can be easily started using either the batch file or the shell script.</p>
- <a name="Google_Search_Sample"/>
-<h3>Google Search Sample</h3>
+<h3><a name="Google_Search_Sample">Google Search Sample</a></h3>
<p>This includes a search program that uses the familiar Google search over
the SOAP API. It utilizes the non-blocking mode of the client API. This
sample can be found at the samples\googleSearch directory and can be easily
started using either the batch file or the shell script.</p>
- <a name="Amazon_Queuing_Service"/>
-<h3>Amazon Queuing Service</h3>
+<h3><a name="Amazon_Queuing_Service">Amazon Queuing Service</a></h3>
<p>Amazon queuing service sample shows how to use the Amazon queuing service.
It has two user interfaces , one to enqueue and the other dequeue. This
sample is included in the samples\amazonQS directory and also contains the
batch/shell scripts required to run sample.</p>
-<p align="right"><a href="userguide4.html" target="_blank"><img alt=""
+<p align="right"><a href="userguide4.html" target="_blank"><img
src="images/arrow_left.gif"> Previous Page</a></p>
<p>Pages: <a href="userguide.html" target="_blank">Content</a>, <a
Re: svn commit: r370748 [3/3] - in /webservices/axis2/trunk/java/xdocs/0_94: installationguide.html userguide.html userguide1.html userguide2.html userguide3.html userguide4.html userguide5.html
Posted by Davanum Srinivas <da...@gmail.com>.
Sanjiva,
there is a latest directory....
-- dims
On 1/20/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> On Fri, 2006-01-20 at 07:10 +0000, chinthaka@apache.org wrote:
> > Modified: webservices/axis2/trunk/java/xdocs/0_94/userguide1.html
>
> Hmm. Should we be modifying 0.94 docs?? IMO we should modify the docs in
> a new dir called 0_95 .. or maybe "current" and then use the 0_xx thing
> to hold the snapshot of docs for that version.
>
> Or else, we can just not have the version numbered hierarchy for docs in
> SVN and just do that on the Web site etc.. Hmm maybe that makes more
> sense!
>
> Sanjiva.
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: svn commit: r370748 [3/3] - in /webservices/axis2/trunk/java/xdocs/0_94: installationguide.html userguide.html userguide1.html userguide2.html userguide3.html userguide4.html userguide5.html
Posted by Davanum Srinivas <da...@gmail.com>.
Sanjiva,
there is a latest directory....
-- dims
On 1/20/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> On Fri, 2006-01-20 at 07:10 +0000, chinthaka@apache.org wrote:
> > Modified: webservices/axis2/trunk/java/xdocs/0_94/userguide1.html
>
> Hmm. Should we be modifying 0.94 docs?? IMO we should modify the docs in
> a new dir called 0_95 .. or maybe "current" and then use the 0_xx thing
> to hold the snapshot of docs for that version.
>
> Or else, we can just not have the version numbered hierarchy for docs in
> SVN and just do that on the Web site etc.. Hmm maybe that makes more
> sense!
>
> Sanjiva.
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: svn commit: r370748 [3/3] - in
/webservices/axis2/trunk/java/xdocs/0_94: installationguide.html
userguide.html userguide1.html userguide2.html userguide3.html
userguide4.html userguide5.html
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Fri, 2006-01-20 at 07:10 +0000, chinthaka@apache.org wrote:
> Modified: webservices/axis2/trunk/java/xdocs/0_94/userguide1.html
Hmm. Should we be modifying 0.94 docs?? IMO we should modify the docs in
a new dir called 0_95 .. or maybe "current" and then use the 0_xx thing
to hold the snapshot of docs for that version.
Or else, we can just not have the version numbered hierarchy for docs in
SVN and just do that on the Web site etc.. Hmm maybe that makes more
sense!
Sanjiva.
Re: svn commit: r370748 [3/3] - in
/webservices/axis2/trunk/java/xdocs/0_94: installationguide.html
userguide.html userguide1.html userguide2.html userguide3.html
userguide4.html userguide5.html
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Fri, 2006-01-20 at 07:10 +0000, chinthaka@apache.org wrote:
> Modified: webservices/axis2/trunk/java/xdocs/0_94/userguide1.html
Hmm. Should we be modifying 0.94 docs?? IMO we should modify the docs in
a new dir called 0_95 .. or maybe "current" and then use the 0_xx thing
to hold the snapshot of docs for that version.
Or else, we can just not have the version numbered hierarchy for docs in
SVN and just do that on the Web site etc.. Hmm maybe that makes more
sense!
Sanjiva.