Documentation Center

Toolkit Sample Web Services Components

Here are the components of the Toolkit Web Services Sample.

  • Custom SDK Application (Toolkit.java).

    This is the starting point. It is a custom running toolkit SDK application that implements all of the methods in the toolkit by adapting the original tools classes.

    This SDK application runs through a complete test scenario that exercises all of the tools (TM/TD kit import, leverage, TM/TD kit export).

    The Java2WSDL generator uses this running SDK application to generate a WSDL description for the Web services. The WSDL2Java generator, in turn, uses the generated WSDL to generate Java Web server and client stubs. Likewise, for the .NET platform the .NET WSDL tool is used to generate .NET Web client stubs.

    The generated toolkit Web clients are completely decoupled from the toolkit Web server, and can be run across the Web on different computers.

    All TM/TD (kit) import/export operations are done by serializing and deserializing streams between the toolkit’s Web client and Web server.

    The Web services are served by the original Toolkit.java file, which contains all of the Web service implementations. Axis directs all Web client requests to this service. The -c option is passed to WSDL2Java to tell it to use the same starting class for the actual Web services implementation.

  • toolkit\sdk-service.wsdl

    Generated WSDL used to generate Web client proxies to bind to Web services. All of the Java and .NET Web client stubs are generated from this WSDL file.

  • Generated Java Web client proxy (ToolkitSampleStub.java)

    These are the toolkit APIs that Java Web-client programs invoke.

  • test/ToolkitTest.java

    Web client Java toolkit test application that runs over the Web with functionality identical to the original SDK toolkit application.

    All TM/TD (kit) import/export operations are done by serializing/deserializing streams between the toolkit’s Web client and Web server. This class uses the generated Web client stub ToolkitSampleStub to access all Web service functionality.

  • .NET Web client support (csharp)

    All corresponding .NET C# Web client tests are in the csharp sub-folder.

  • Generated .NET Web client proxy (ToolkitSampleService.cs)
    This is generated by running the .NET WSDL.exe tool on the previously-generated WSDL.
    toolkit> wsdl.exe /language:cs
    /n:Com.Idiominc.Wssdk.Samples.Component.Webservices.
    Toolkit sdk-service.wsdl
    The build.dotnet.webservice.toolkit ANT target compiles the toolkit client proxy class into a .NET DLL:
    samples/dist/ToolkitWebServiceClient.dll

    These are the toolkit APIs that .NET (C#, VB) Web-client programs invoke.

    The build.dotnet.webservice.toolkit ANT target performs this .NET Web client generation.

  • csharp/Test/ToolkitTest.cs

    Web client .NET toolkit test application that runs over the Web with functionality identical to the original SDK toolkit application.

    The build.dotnet.webservice.toolkit ANT target compiles the toolkit test class into a .NET .exe:
    samples/dist/Toolkit.exe

    You can then immediately run the compiled .exe because the build script copies the required .NET Web client proxy DLLs into the same folder.

    All TM/TD (kit) import/export operations are done by serializing and deserializing streams between the toolkit’s Web client and Web server.

  • samples/docs/api/com/idiominc/wssdk/samples/ webservices/component/toolkit/client

    Generated Javadocs for the toolkit Web client proxy. These are the Web service interfaces against which the client application developer will program.

    The Web client knows nothing about how these are implemented; the developer merely codes against these exposed interfaces.

  • toolkit\deploy.wsdd

    Generated service descriptors for the toolkit Web service; these are used for deploying the toolkit Web service on the application server.

toolkit\deploy.wsdd
Generated service descriptors for the toolkit Web service; these are used for deploying the toolkit Web service on the application server.
So what happens if I have more information I want to add?