roshan 2004/08/08 21:47:01
Modified: targets/axis/cpp/arch WSDL2Ws.pdf WSDL2Ws.html
Log:
Added Dependencies on Axis Java tool details to Wsdl2ws.html .Added by Rangika
Revision Changes Path
1.3 +174 -141 ws-site/targets/axis/cpp/arch/WSDL2Ws.pdf
<<Binary file>>
1.5 +29 -17 ws-site/targets/axis/cpp/arch/WSDL2Ws.html
Index: WSDL2Ws.html
===================================================================
RCS file: /home/cvs/ws-site/targets/axis/cpp/arch/WSDL2Ws.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- WSDL2Ws.html 13 Jul 2004 09:57:50 -0000 1.4
+++ WSDL2Ws.html 9 Aug 2004 04:47:01 -0000 1.5
@@ -281,23 +281,25 @@
<br>
<br>
<p></p>
-<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>
+<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. </p>
<div class="h4">
<h4> 1.1 Types Of Classes</h4>
</div>
-<p>The Tool Should starts with a WSDL document and generate following classes.</p>
+<br>
+<br>
+<p>The tool should start with a WSDL document and generate following classes.</p>
<p>· ·
WSDL2WS tool is used for building following C/C++ componentsWSDL2WS tool is used for
building following C/C++ components</p>
<p>
o Server side – Skeletons and Wrappers</p>
<p>
o Client side – Stubs</p>
<br>
-<br> · · <strong>WSDL2WS
tool</strong> that generates wrappers which used to deploy the Service in the AxisC++
engine. (Please refer the Wrapper Specification for more information)<strong>WSDL2WS
tool</strong> that generates wrappers which used to deploy the Service in the AxisC++
engine. (Please refer the Wrapper Specification for more information)<p>The generated
Wrappers perform the following functions. These wrappers act as RPC Providers.</p>
+<br> > > > > > ><strong>WSDL2WS
tool</strong> that generates wrappers which are used to deploy the Service in the
Axis C++ engine. (Please refer the Wrapper Specification for more
information)<strong>WSDL2WS tool</strong> that generates wrappers which are used to
deploy the Service in the Axis C++ engine. (Please refer the Wrapper Specification for
more information)<p>The generated Wrappers perform the following functions. These
wrappers act as RPC Providers.</p>
<p>o Serialization</p>
<p>o Deserialization</p>
<p>o Method invocation</p>
<div class="h4">
<h4> 1.2 Programming Languages</h4>
</div>
-<p>The tool should able to generate classes for</p>
+<p>The tool should be able to generate classes for</p>
<p> • C++</p>
<p> • C</p>
<br>
@@ -308,21 +310,21 @@
<div class="h4">
<h4> 1.3 encoding style</h4>
</div>
-<p>The tool should be support SOAP1.2 encoding style and extensible to support
other encoding styles as well.</p>
+<p>The tool should be able to support SOAP1.2 encoding style and extensible to
support other encoding styles as well.</p>
<div class="h4">
<h4> 1.4 Style Of the Service</h4>
</div>
-<p>The tool should able to generate classes for following styles</p>
+<p>The tool should be able to generate classes for following styles</p>
<p>• RPC</p>
<p>• Document</p>
<p>• Messaging</p>
<div class="h4">
<h4> 1.5 Supports for making simple custom
types</h4>
</div>
-<p>Tool generate Wrapper for custom types in following conditions</p>
-<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>
-<p>• Genarate the complete wrappers for Array of any simple or WSDL types like
struts</p>
+<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>• Generates the complete wrappers for Array of any simple or WSDL types
like struts</p>
<div class="h3">
<h3>2.Architecture</h3>
</div>
@@ -340,10 +342,9 @@
<div class="h4">
<h4> 2.1 Mediator WsContext</h4>
</div>
-<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></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>
<div class="h2">
-<h2>wsContext has following componets</h2>
+<h2>wsContext has following components</h2>
</div>
<p>1. ServiceInfo – information about service</p>
<p>2. WrapperInfo – information about wrapper options</p>
@@ -351,14 +352,14 @@
<div class="h4">
<h4> 2.2 Genarator</h4>
</div>
-<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>
<div class="h4">
<h4> 2.4 flow of execution</h4>
</div>
<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>
+<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>
<div class="h4">
<h4> 2.5 Sequence Diagram</h4>
</div>
@@ -366,6 +367,17 @@
<img alt="" src="../images/c/ag/sequence.jpg"></p>
<br>
<br>
+<div class="h3">
+<h3>Dependencies on Axis Java tool</h3>
+</div>
+<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 noshade="noshade" size="1">
<div id="pdf" align="right">
<a href="WSDL2Ws.pdf"><img alt="PDF" src="../../skin/images/pdfdoc.gif"
class="skin"><br>
