![]() WSDL2Ws |
The tool should be able to generate different types of Wrappers and Skelentons for the server side and clients stubs for the clients Side.WSDL2Ws tool in AxisC++ is written in Java.
The Tool Should starts with a WSDL document and generate following classes.
·
WSDL2WS tool is used for building following C/C++ components
o Server side Skeletons and Wrappers
o Client side Stubs The generated Wrappers perform the following functions. These wrappers act as RPC Providers. o Serialization o Deserialization o Method invocation The tool should able to generate classes for
C++ C 1.1 Types Of Classes
1.2 Programming Languages
The tool should be extensible to support other programming languages if required.
The tool should be support SOAP1.2 encoding style and extensible to support other encoding styles as well.
The tool should able to generate classes for following styles
RPC
Document
Messaging
Tool generate Wrapper for custom types in following conditions
Generate the method signatures of the types (serialize(), desirealize()) so that developer can write serialize desirialize code in most efficient way.
Generate the complete wrapper for WSDL types like struts
Genarate the complete wrappers for Array of any simple or WSDL types like struts
The tool takes a top down approach. It starts with a wsdl document and generates all the classes necessary to deploy the web service. It generates
Skeleton (wrapper class)
Wrapper classes for complex types
Server side and client Side stubs
The tool can be extensible to generate Service classes to be published
For more information about the generated classes please refer to the architecture documentation.
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.
1. ServiceInfo information about service
2. WrapperInfo information about wrapper options
3. TypeMap information about custom types
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.
1.WSDL file and user options are processed by the WSDL2Ws and WSContext object is created.
2. WebServiceGenaratorFactory will create WebServiceGenarator depend on the service style
3. Then the WebServiceGenarator will create right set of Generators to create the set of files
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).