WSDL - Tools and Code Generation from WSDL

What is Code Generation from WSDL?

One of the biggest advantages of WSDL is that it acts as a contract between the service provider and consumer.
Because it is machine-readable, many development tools can automatically generate client proxies, server skeletons, and data bindings directly from a WSDL file.

➡️ This means developers don’t have to manually write boilerplate code for sending/receiving SOAP messages — the tools handle it.

Benefits of Code Generation from WSDL

  1. Saves Time – Auto-generates repetitive plumbing code.

  2. Reduces Errors – Prevents mistakes in message formatting or protocol handling.

  3. Ensures Consistency – Generated code always matches the service contract.

  4. Boosts Productivity – Developers focus on business logic, not low-level communication.

  5. Cross-Platform Interoperability – Java, .NET, and other ecosystems can consume the same WSDL and generate working clients.

Popular Tools for WSDL Code Generation

  1. Java (JAX-WS)

    • Tool: wsimport

    • Command:

      wsimport -keep -p com.example.client http://example.com/service?wsdl

    • Generates Java classes for request/response messages and a client stub to invoke the service.

  1. .NET (WCF / .NET Core)

    • Tool: svcutil (Service Model Metadata Utility Tool)

    • Command:

      svcutil http://example.com/service?wsdl

    • Generates C# classes, data contracts, and client proxies for calling the WSDL-defined service.

  1. Apache Axis / CXF (Java)

    • Axis (WSDL2Java) and CXF (wsdl2java) generate Java stubs from WSDL.

    • Example (Axis):

      java org.apache.axis.wsdl.WSDL2Java http://example.com/service?wsdl

  1. SoapUI

    • A testing tool that can import a WSDL, generate requests, and let developers test SOAP services without writing code.

    • Great for debugging and functional testing.

  1. Postman

    • Primarily for REST, but newer versions support WSDL imports to test SOAP services.

    • Parses WSDL to auto-generate SOAP request templates.

How the Workflow Looks

  1. Developer gets the WSDL URL (e.g., http://example.com/service?wsdl).

  2. Runs a tool (e.g., wsimport or svcutil).

  3. Tool generates:

    • Stub classes / proxies (for client apps to call the service).

    • Skeletons (for service providers to implement).

    • Data classes (for messages and types).

  4. Developer writes business logic only, while the tool handles SOAP messaging.

In summary: Tools like wsimport, svcutil, Apache Axis, SoapUI, and Postman make WSDL highly usable by turning abstract service definitions into ready-to-use code, ensuring speed, accuracy, and consistency.