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 ro...@apache.org on 2004/08/09 06:45:00 UTC
cvs commit: ws-axis/site/src/documentation/content/xdocs/cpp/arch WSDL2Ws.ihtml
roshan 2004/08/08 21:45:00
Modified: site/src/documentation/content/xdocs/cpp/arch WSDL2Ws.ihtml
Log:
Added Dependencies on Axis Java tool details.Added by Rangika
Revision Changes Path
1.2 +82 -74 ws-axis/site/src/documentation/content/xdocs/cpp/arch/WSDL2Ws.ihtml
Index: WSDL2Ws.ihtml
===================================================================
RCS file: /home/cvs/ws-axis/site/src/documentation/content/xdocs/cpp/arch/WSDL2Ws.ihtml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- WSDL2Ws.ihtml 30 Dec 2003 14:15:15 -0000 1.1
+++ WSDL2Ws.ihtml 9 Aug 2004 04:45:00 -0000 1.2
@@ -1,10 +1,12 @@
<html>
<head>
- <title>WSDL2Ws Tool</title>
+ <title>WSDL2Ws Tool </title>
+
<link href="axis.css" rel=stylesheet type=text/css>
</head>
<body>
+
<table cellspacing=0 width=100% border=0>
<tr>
<td colspan=2>
@@ -12,7 +14,6 @@
</a>
-
<h1>
WSDL2Ws
</h1>
@@ -24,70 +25,63 @@
<strong>
Contents
</strong>
-<ul>
-<li>
-<a href="#intro">1.Fuctionality</a>
-</li>
-<li>
-<a href="#webapp"> 1.1Types Of Classes</a>
-</li>
-<li>
-<a href="#depend"> 1.2Programming Languages</a>
-</li>
-<li>
-<a href="#websvc"> 1.3Encoding Style</a>
-</li>
-<li>
-<a href="#start"> 1.4Style Of the Service</a>
-</li>
-<li>
-<a href="#install-test"> 1.5Supports for Making Simple Custom Types </a>
-</li>
-
-<li>
-<a href="#test">2.Architecture</a>
-</li>
-
-<li>
-<a href="#test1"> 2.1 Out Line</a>
-</li>
-
-<li>
-<a href="#test2"> 2.2 Mediator WsContext</a>
-</li>
-
-
-<li>
-<a href="#test3"> 2.3 Generator</a>
-</li>
-
-
-<li>
-<a href="#test4"> 2.4 Flow Of Execution</a>
-</li>
-
-<li>
-<a href="#test5"> 2.5 Sequence Diagram</a>
-</li>
-</ul>
+<p>
+<a href="#intro">1.Functionality</a>
+</p>
+
+<p><a href="#webapp">1.1Types Of Classes</a>
+</p>
+
+<p><a href="#depend">1.2Programming Languages</a>
+</p>
+
+<p><a href="#websvc">1.3Encoding Style</a>
+</p>
+
+<p><a href="#start">1.4Style Of the Service</a>
+</p>
+
+<p><a href="#install-test">1.5Supports for Making Simple Custom Types </a>
+</p>
+
+<p><a href="#test">2.Architecture</a>
+</p>
+
+<p><a href="#test1">2.1 Out Line</a>
+</p>
+
+<p><a href="#test2">2.2 Mediator WsContext</a>
+</p>
+
+<p><a href="#test3">2.3 Generator</a>
+</p>
+
+<p><a href="#test4">2.4 Flow Of Execution</a>
+</p>
+
+<p><a href="#test5">2.5 Sequence Diagram</a>
+</p>
+
+<p><a href="#test6">3.Dependencies on Axis Java tool</a>
+</p>
<p class="MsoNormal"><span style="font-family:Verdana;color:black">
- <a name="intro"/></a>
+ <a name="intro"></a>
<h1>1. Functionality </h1></P>
<p class="MsoNormal"><span style="font-family:Verdana;color:black">
- <p>The tool should be able to generate different types of Wrappers and Skelentons for the server side and client�s stubs for the client�s Side.WSDL2Ws tool in AxisC++ is written in Java.
+ <p>The tool should be able to generate different types of Wrappers and Skeletons for the server side and client�s stubs for the client�s Side.WSDL2Ws tool in Axis C++ is written in Java.
<a name= "webapp"/></a>
- <h2> 1.1 Types Of Classes</h2>
+ <h2> 1.1 Types Of Classes</h2></p>
- <p>The Tool Should starts with a WSDL document and generate following classes.
+ <p>The tool should start with a WSDL document and generate following classes.</p>
<P class=MsoNormal style="MARGIN-LEFT: 76pt; TEXT-INDENT: -18pt">
@@ -101,11 +95,11 @@
</SPAN></P>
<SPAN
-style="COLOR: black; FONT-FAMILY: Symbol; FONT-SIZE: 10pt"> �<SPAN
-style="FONT: 7pt 'Times New Roman'">
-</SPAN></SPAN><SPAN style="COLOR: black; FONT-FAMILY: Verdana"> <b>WSDL2WS tool</b> that generates wrappers which used to deploy the Service in the AxisC++ engine. (Please refer the Wrapper Specification for more information)
+style="COLOR: black; FONT-FAMILY: Symbol; FONT-SIZE: 10pt"> ><SPAN
+style="FONT: 7pt 'Times New Roman'"> >
+</SPAN></SPAN><SPAN style="COLOR: black; FONT-FAMILY: Verdana"> <b>WSDL2WS tool</b> that generates wrappers which are used to deploy the Service in the Axis C++ engine. (Please refer the Wrapper Specification for more information) </SPAN>
- <p>The generated Wrappers perform the following functions. These wrappers act as RPC Providers. </p>
+ <p>The generated Wrappers perform the following functions. These wrappers act as RPC Providers. </p>
<p>o Serialization</p>
<p>o Deserialization</p>
@@ -120,7 +114,7 @@
<a name="depend"/></a>
<h2> 1.2 Programming Languages </h2>
-<p> The tool should able to generate classes for
+<p> The tool should be able to generate classes for
<p> � C++ </p>
<p> � C </p>
</p>
@@ -133,14 +127,14 @@
<a name="websvc"/></a>
<h2> 1.3 encoding style</h2>
- <p>The tool should be support SOAP1.2 encoding style and extensible to support other encoding styles as well.
+ <p>The tool should be able to support SOAP1.2 encoding style and extensible to support other encoding styles as well.
</p>
<a name="start"/></a>
<h2> 1.4 Style Of the Service</h2>
- <p>The tool should able to generate classes for following styles
+ <p>The tool should be able to generate classes for following styles</p>
<p>� RPC </p>
<p>� Document </p>
<p>� Messaging </P>
@@ -153,12 +147,12 @@
- <p>Tool generate Wrapper for custom types in following conditions
-<p>� Generate the method signatures of the types (serialize(), desirealize()) so that developer can write serialize desirialize code in most efficient way.</P>
-<p>� Generate the complete wrapper for WSDL types like struts
+ <p>Tool generates Wrappers for custom types in following conditions</p>
+<p>� Generates the method signatures of the types (serialize(), deserialize()) so that developer can write serialize desirialize code in most efficient way.</P>
+<p>� Generates the complete wrappers for WSDL types like struts
</p>
-<p>� Genarate the complete wrappers for Array of any simple or WSDL types like struts </p>
+<p>� Generates the complete wrappers for Array of any simple or WSDL types like struts </p>
@@ -191,9 +185,9 @@
-<p>The WSDL file and the user options are processed by the WSDLWs. The WSDL create a class called wsContext(WebServiceContext) which is the runtime representation of the processed data. This wsContext passes to the generators. The generators extract the information form the wsContext create the files.The wsContext act as a mediator and create a loosely coupled system.<p>
+<p>The WSDL file and the user options are processed by the WSDLWs. The WSDL creates a class called wsContext(WebServiceContext) which is the runtime representation of the processed data. This wsContext passes to the generators. The generators extract the information from the wsContext and creates the files.The wsContext acts as a mediator and creates a loosely coupled system.</p>
-<h3>wsContext has following componets</h3>
+<h3>wsContext has following components</h3>
<p>1. ServiceInfo � information about service </p>
<p>2. WrapperInfo � information about wrapper options</p>
@@ -205,20 +199,17 @@
<h2> 2.2 Genarator
</h2>
-<p>Generator generate a class depend on the options, It contains a class called SourceWriter and the concrete implementation of the SourceWriter decides what will Genarator generate. The SourceWriter factory create a correct type of generator depend on the options.</p>
+<p>Generator generates a class which depends on the options, It contains a class called SourceWriter and the concrete implementation of the SourceWriter decides what the Genarator generates. The SourceWriter factory creates a correct type of generator which depends on the options.</p>
<a name="test4"/></a>
<h2> 2.4 flow of execution
</h2>
<p>1.WSDL file and user options are processed by the WSDL2Ws and WSContext object is created.</p>
-<p>2. WebServiceGenaratorFactory will create WebServiceGenarator depend on the service style </p>
-<p>3. Then the WebServiceGenarator will create right set of Generators to create the set of files</p>
-<p>4.Each generator will invoke SourceWriter capable of writing each type of file.
-Rest of the logic is developer to decide (He have all needed info as WsContext).
-
-
-
+<p>2. WebServiceGenaratorFactory will create WebServiceGenarator which depends on the service style </p>
+<p>3. Then the WebServiceGenarator will create a right set of Generators to create the set of files</p>
+<p>4.Each generator will invoke SourceWriter which is capable of writing each type of file.
+Rest of the logic is upto the developer to decide (He has all the needed info as WsContext).
</p>
@@ -231,8 +222,25 @@
<img SRC="../images/c/ag/sequence.jpg" ></center></p>
+<a name="test6"></a>
+<h1>Dependencies on Axis Java tool</h1>
-<hr size=1 noshade= />
+<p>The document below describes the areas where Apache Axis C++ is dependant upon the Axis Java tool. </p>
+<p>The Axis jars given below are used as they are in the Axis Java tool:</p>
+<br>
+<p>     axis.jar <br>
+    commons-discovery.jar <br>
+    commons-logging.jar <br>
+    jaxrpc.jar <br>
+    saaj.jar <br>
+    wsdl4j.jar <br>
+    xml-apis.jar <br> </p>
+<p>"SchemaUtils.java" and "ElementDecl.java" files have been overridden and their original implementations are no longer used even though they exist in the above mentioned jars.</p>
+
+<p>No classes have been extended at the present time.</p>
+<p>Except for "SchemaUtils.java" and "ElementDecl.java" the rest of the code has been developed for the Axis C++ tool and is not present in the current Axis Java tool.</p>
+
+<hr size=1 noshade= />
</body>
</html>