Savon Ruby GEM
https://github.com/rubiii/savon
Heavy metal Ruby SOAP client library
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:languages:ruby:extensions/rubygem-savon && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
rubygem-savon.changes | 0000003134 3.06 KB | |
rubygem-savon.spec | 0000002581 2.52 KB | |
savon-2.2.0.gem | 0000137216 134 KB |
Revision 8 (latest revision is 26)
- updated to version 2.2.0 * Feature: [#416](https://github.com/savonrb/savon/pull/416) The global `namespace_identifier` option can now be set to `nil` to not add a namespace identifier to the message tag. * Feature: [#408](https://github.com/savonrb/savon/pull/408) Added `Savon::Client#service_name` to return the name of the SOAP service. * Improvement: When mistyping an option name, Savon used to raise a simple `NoMethodError`. This is because regardless of whether you're using the Hash or block syntax to pass global or local options, both are just method calls on some options object. ``` NoMethodError: undefined method 'wsdk' for #<Savon::GlobalOptions:0x007fed95a55228> ``` As of this change, Savon now catches those errors and raise a `Savon::UnknownOptionError` with a slightly more helpful error message instead. ``` Savon::UnknownOptionError: Unknown global option: :wsdk ``` * Improvement: [#385](https://github.com/savonrb/savon/issues/385) Instead of raising an `ArgumentError` when Wasabi can't find any operations in the WSDL. Savon now raises a `Savon::UnknownOperationError`. This might happen when Wasabi fails to parse the WSDL because of imports for example. * Fix: [#430](https://github.com/savonrb/savon/pull/430) allows you to rescue and ignore `Savon::Error` errors in production while still having mocks trigger test failures.
Comments 0