You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ch...@apache.org on 2006/09/26 09:21:29 UTC
svn commit: r449935 - /webservices/axis2/trunk/java/xdocs/1_1/migration.html
Author: chatra
Date: Tue Sep 26 00:21:26 2006
New Revision: 449935
URL: http://svn.apache.org/viewvc?view=rev&rev=449935
Log:
Updated migration.html. Thanks Evanthika for Axis2-1197
Modified:
webservices/axis2/trunk/java/xdocs/1_1/migration.html
Modified: webservices/axis2/trunk/java/xdocs/1_1/migration.html
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/xdocs/1_1/migration.html?view=diff&rev=449935&r1=449934&r2=449935
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_1/migration.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_1/migration.html Tue Sep 26 00:21:26 2006
@@ -25,7 +25,7 @@
<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
+subject with [Axis2]. To subscribe to the mailing list see <a
href="http://ws.apache.org/axis2/mail-lists.html">here.</a></p>
<h2>Content</h2>
@@ -135,7 +135,7 @@
was highly cumbersome. Service deployment in Axis2 is straight forward and
dynamic. Dynamic behavior is from the "Administrator" facility given by the
development in the server side. It's just a matter of creating the .aar file,
-and deploying it. More detail regarding this is given in the Axis2 user
+and deploying it. More details regarding this is given in the Axis2 user
guide.</p>
<p>Axis2 is far from the "Handler concept" and is more into the "Module
@@ -259,7 +259,7 @@
<p><b>Then define your phase orders for 'soapmonitorPhase' referenced in the
module.xml :</b></p>
<pre> <phaseOrder type="inflow">
- <!-- System pre defined phases -->
+ <!-- Global Phases -->
<phase name="TransportIn"/>
<phase name="PreDispatch"/>
<phase name="Dispatch" class="org.apache.axis2.engine.DispatchPhase">
@@ -284,34 +284,37 @@
</handler>
<handler name="InstanceDispatcher"
class="org.apache.axis2.engine.InstanceDispatcher">
- <order phase="PostDispatch"/>
+ <order phase="Dispatch"/>
</handler>
</phase>
- <!-- System pre defined phases -->
- <!-- After Postdispatch phase module author or or service author can add any phase he want -->
+ <!-- Global Phases -->
+ <!-- After Dispatch phase module author or service author can add any phase he wants -->
<phase name="userphase1"/>
<phase name="soapmonitorPhase"/>
</phaseOrder>
<phaseOrder type="outflow">
- <!-- user can add his own phases to this area -->
+ <!-- user can add his own phases to this area -->
+ <!-- Global phases -->
+ <!-- these phases will run irrespective of the service -->
+ <phase name="MessageOut"/>
<phase name="userphase1"/>
<phase name="soapmonitorPhase"/>
- <!--system predefined phase-->
- <!--these phase will run irrespective of the service-->
<phase name="PolicyDetermination"/>
- <phase name="MessageOut"/>
+ <!-- Global phases -->
</phaseOrder>
<phaseOrder type="INfaultflow">
- <!-- user can add his own phases to this area -->
<phase name="userphase1"/>
<phase name="soapmonitorPhase"/>
+ <!-- user can add his own phases to this area -->
</phaseOrder>
<phaseOrder type="Outfaultflow">
- <!-- user can add his own phases to this area -->
+ <!-- user can add his own phases to this area -->
+ <!-- Global phases -->
+ <phase name="MessageOut"/>
<phase name="userphase1"/>
<phase name="soapmonitorPhase"/>
<phase name="PolicyDetermination"/>
- <phase name="MessageOut"/>
+ <!-- Global phases -->
</phaseOrder></pre>
<p>See the user guide for more info on axis2 modules.</p>
@@ -343,7 +346,7 @@
Axis2.</p>
<p>First, lets take a look at a simple document / literal style WSDL used in
-an Axis 1.x Web Service. This example assumes the name of simple.wsdl for the
+an Axis 1.x Web Service. This example assumes the name simple.wsdl for the
wsdl below:</p>
<pre><?xml version="1.0" encoding="UTF-8"?>
@@ -401,7 +404,7 @@
<port name="SimpleEndpointPort" binding="tns:SimpleEndpointBinding">
<soap:address location="http://localhost:8080/axis/services/SimpleEndpointPort"/></port></service></definitions></pre>
-<p>The next step is run WSDL2Java on the wsdl. For axis 1.x, this example
+<p>The next step is to run WSDL2Java on the wsdl. For axis 1.x, this example
uses the following ant task:</p>
<pre><target name="wsdl2java" description="axis 1.x">
<delete dir="output" />
@@ -469,16 +472,17 @@
</target></pre>
<p>For an explanation of the Axis2 WSDL2Java ant task and its options, see
-the CodegenToolReference guide.</p>
+the <a href="../tools/1_1/CodegenToolReference.html">CodegenToolReference
+Guide.</a></p>
<p>A feature of xmlbeans is that there is one class file created with
WSDL2java, and a series of xsb files. These must be referenced when
compiling, and as the example shows these files are moved to a build
-directory</p>
+directory.</p>
-<p>The Axis2 WSDL2Java example also takes the simple.wsdl under the directory
-'wsdl' , and from that creates files under the directory 'output'. The
-relevant non-xmlbean files created are shown below:</p>
+<p>The Axis2 WSDL2Java example also takes the simple.wsdl which is under the
+directory 'wsdl' and from that creates files under the directory 'output'.
+The relevant non-xmlbean files created are shown below:</p>
<pre>output/resources/services.xml
output/src/org/simple
output/src/org/simple/endpoint
@@ -497,7 +501,7 @@
<p>The first important distinction is that while the Axis 1.x example
generated deploy.wsdd and undeploy.wsdd, the Axis2 example created a
services.xml. The files deploy.wsdd and services.xml are a breed apart,
-comming from different architectures. There is no direct parallel between
+coming from different architectures. There is no direct parallel between
them. See the Axis2 user guide for an explanation about services.xml</p>
<p>Now we're ready to code. We'll start with Axis 1.x on the service side. To
@@ -666,7 +670,7 @@
<h2>Best Usage</h2>
<p>Axis1.x and Axis2 have different ways of seeing the SOAP stack. So the
-best way to migrate is to follow the User guide and the Architecture guide of
+best way to migrate is to follow the <a href="userguide.html">User's Guide</a> and the <a href="Axis2ArchitectureGuide.html">Architecture Guide</a> of
Axis2 properly. Axis2 is very much straight forward and friendly to use than
it's predecessor.</p>
</body>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-cvs-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-cvs-help@ws.apache.org