Gem Version Build Status Dependency Status Documentation Status Coverage Status Code Climate Repo Size Gem Downloads Analytics


WashOutBuilder is a Soap Service Documentation generator (extends WashOut /)

The way WashOut is used is not modified, it just extends its functionality by generating html documentation to your services that you write

NEW Improvements in version 1.5.1

  • The WashoutBuilder::Engine can now be automatically be mounted in Rails application by using a simple configuration in config/application.rb which allows you to whitelist or blacklist the environment where WashoutBuilder::Engine can be mounted .
  • By default all the options are set to nil, so the engine does not get mounted automatically by default. You need to set them if you want this to work.


# needed in case the gem is not in the default group
if config.respond_to?(:washout_builder)
  # the path where the engine should be mounted on
  config.washout_builder.mounted_path = "/washout"
  # this can either be an array of strings or array of regular expressions or a string.
  # If you specify "*" ,will mean all environments
  # otherwise you can specify "development" or ['development', 'staging'] or nil
  # or you can use regular expressions like /development/ or array of regular expressions
  config.washout_builder.whitelisted_envs = "*"
  # this can either be an array of strings or array of regular expressions or a string.
  # you can specify "production" or ['production', 'test'] or nil
  # or you can use regular expressions like /production/ or array of regular expressions
  config.washout_builder.blacklisted_envs = nil

If you don't set them and they are left with default nil values, you will have to use the old way, by manually mount the engine in the Rails routes configuration file (config/routes.rb) by following examples below.

NEW Improvements in version 1.4.0

  • when displaying all services , the link to documentation is now using the new format /soap_doc for better readability
  • Fixed an issue when generating documentation for a controller that didn't had the namespace set, the WSDL url and endpoint was missing from the generated source because of that. However if you don't set the namespace in controller the links to WSDL and endpoint would throw an error when trying to access them.

NEW Improvements in version 1.3.0

  • link to accessing documentation for a single controller is now easier. You can use the same route as for seeing WSLD, but replacing /wsdl with /soap_doc
  • The old way of acessing documentation is still kept, so if you mounted the engine at /washout, you can still acess the documentation by appending to this url the full name of the controller including the namespace and the engine name(in case the controller is from a engine) as described below.


  • Provides way of seeing the available services with links to documentation, endpoint and namespace
  • Provides a human-readable HTML documentation generated for each service that you write


Click on the Documentation links on that page to see the demo application.

Hope you enjoy it :)

Demo Application Source Code


  1. Ruby 1.9.x or Ruby 2.x
  2. Ruby On Rails
  3. WashOut gem version >= 0.9.1


  • Rails >3.0 only. MRI 1.9, 2.0, .

  • JRuby is not offically supported since 0.15.0.

  • Ruby 1.8 is not officially supported since 0.5.3.

We will accept further compatibilty pull-requests but no upcoming versions will be tested against it.

Rubinius support temporarily dropped since 0.6.2 due to Rails 4 incompatibility.


Type the following from the command line to install:

gem install washout_builder

Add the following to your Gemfile:

gem "washout_builder"

it will automatically install also WashOut gem that is currently used

Or if you want this to be available only in development mode , you can do something like this inside the Gemfile:

gem 'wash_out' # The WashOut gem would be used also in production

group :development, :test do
    gem 'washout_builder' # only available in development mode.

Please read Release Details if you are upgrading. We break backward compatibility between large ticks but you can expect it to be specified at release notes.


The way soap_actions, or reusable types are defined or how the configuration is made using WashOut haven't changed You can still do everything that gem does .

In order to see the documentation you must write something like this in the routes (exactly like you would do when using only WashOut)

In the following file config/routes you can put this configuration

WashOutSample::Application.routes.draw do
    wash_out :rumbas wash_out :my_other_service

    namespace :api do
        wash_out :project_service

    # The verfication "if defined?(WashoutBuilder::Engine)" is needed in case the "washout_builder" gem is not in the default group
    mount WashoutBuilder::Engine => "/washout" if defined?(WashoutBuilder::Engine)

You can access the url /washout and you will see a list with available services ( in our case there are only two : The RumbasController and MyOtherServiceController) with links to their documentation and where you can find the WSDL.

If you want to access directly the hml documentation that was generated for RumbasController you can do that by accessing url like this:

/washout/Rumbas                  # camelcase name
/washout/rumbas                  # without camelcase
/washout/Api::ProjectService     # for namespaced services with camelcase
/washout/api/project_service     # without camelcase

When specifying the soap_service you can also pass a option for description . Here is an example

    namespace: 'http://my.app.com/my_service/wsdl',
    description: 'here goes some description for your service'

When specifying the soap_action you can also pass a option for description, option for arguments description and a list of exceptions(need to be classes) that the method can raise at a certain moment.

Here is an example :

soap_action "find",
    args: { number: :integer },
    args_description: { number: 'some description about this argument' },
    return: :boolean,
    raises: [MyCustomSoapError, MyOtherCustomSoapError ] ,
    description: "some description about this method to show in the documentation"

The exception classes used must inherit from WashOut::Dispatcher::SOAPError, which has by default a error code and a message as attributes .


To test, do the following:

  1. cd to the gem root.
  2. bundle install
  3. bundle exec rake


Please log all feedback/issues via Github Issues. Thanks.

Contributing to washout_builder

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.
  • Fork the project.
  • Start a feature/bugfix branch.
  • Commit and push until you are happy with your contribution.
  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright (c) 2013 bogdanRada. See LICENSE.txt for further details.