Build Status Code Climate Coverage Status Documentation

WsdlMapper is a ruby gem to communicate with SOAP services. It provides:

  1. A generator to create classes from XSD schema files.
  2. (De)Serializers to parse and write XML files to/from instances of these classes.
  3. A generator to create SOAP clients from WSDL files.

Currently it supports only WSDL 1.1, but with Document or RPC message style and literal or encoded style.


Add this line to your application's Gemfile:

gem 'wsdl-mapper'

And then execute:

$ bundle

Or install it yourself as:

$ gem install wsdl-mapper



$ wsdl-mapper generate all some-schema.xsd --out some-schema --module SomeSchema

Will generate models and (de)serializers for the given XSD schema. The generated classes are all nested within the specified module SomeSchema and are put under ${pwd}/some-schema (pwd == current working directory).

For all available options, see

$ wsdl-mapper help generate


$ wsdl-mapper generate svc some-svc.wsdl --out some-schema --module SomeSchema

Will generate models, (de)serializers and a client for the given WSDL service.


  • loosen the dependency on concurrent-ruby, make the async way optional.
  • loosen the dependency on faraday, make the user choose which http library.
  • refactor code to mitigate the naming mess. (there are so many different domain objects called name or type, which causes a mess in naming variables and methods. probably it makes sense to define acronyms and use them consistently throughout the code.)
  • add more documentation, especially:
    • how-tos / tutorials / walkthroughs
    • inline documentation
    • examples
  • add logging to parsing + generating
  • JRuby compatibility:
    • Refactor serialization tests
    • Analyze and mitigate differences in Nokogiris Java SAX parser implementation
  • WSDL 2.0
  • Server generation


  1. Fork it ( )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request