Direct controller specification among routes. Fixes #48
Version tick
Use namespaced controller name in action route.
Camelize the response message also in WSDL.
Removed namespace from response params as it breaks .NET WCF [Fixes #52]
Remove namespace also from faultcode and faultstring
Merge pull request #53 from ebeigarts/fix-routes

Use namespaced controller name in action route.
Merge pull request #54 from ebeigarts/fix-camelize

Camelize the response message also in WSDL.
Merge pull request #55 from ebeigarts/fix-response-namespace

Removed namespace from response params as it breaks .NET WCF [Fixes #52]
Version tick
Nil values should not be coerced to types (Fixes #50)
Check for structure correctness during mapping (Fixes #49)
1.8.7's unsorted hashes are preventing passing.

This is an easy fix.
Improve message for mismatched type on render

Before, it implicitly tried to convert the hash key into an Integer by
its use as an index on the Array.

This is to work with the type of XML that is fairly common, e.g.:
 <stallions>
   <stallion>a</stallion>
   <stallion>b</stallion>
   <stallion>c</stallion>
 </stallion>

But it is easy to mess up the format in the render :soap.
Improve error messages for programmer mistakes.

1. For when an Array is expected but you pass a Hash

Before, its error message came from implicit conversion of the hash key
into an Integer by its use as an index on the Array.

This is to work with the type of XML that is fairly common, e.g.:
 <stallions>
   <stallion>a</stallion>
   <stallion>b</stallion>
   <stallion>c</stallion>
 </stallion>

But it is easy to mess up the format in the render :soap.

2. For when an Array is expected but you pass a String

This was silently discarding the value. Now it raises an exception.
Merge branch 'programmer-errors'

Conflicts:
	lib/wash_out/dispatcher.rb
	spec/wash_out_spec.rb
Merge pull request #67 from exad/programmer-errors

Improve error messages for programmer mistakes.
Merge pull request #65 from exad/1.8.7-workingtests

1.8.7's unsorted hashes are preventing passing.
Correct arrays comparison for 1.8.7
Add Guard for testing.

Now you can run:

    bundle exec guard

And changes to the spec/* or to the lib/* will trigger re-execution of
the tests.

Also bumped the development dep on `pry` to `pry-de`, which includes a
bunch of plugins to do debugging (stepping), stack exploration
(show-stack, up), and so on. You might not like this, but I definitely
do.  Feel free to take that part of the commit out if you don't want it
but do want the Guard part.