Finish 1.0

[tjarratt]

Migrated from savonrb/savon#473

This ticket continues the Wasabi v4.0 milestone ticket which was driving the development for Savon version 3 up until it became Sekken.

Here is my TODO list for version 1.0:

• Solve performance problems #7.
• Support WSDL imports #1.
• Properly separate operations by service and port.
• Support XML Schema imports.
• Remove the dependency on HTTPI as an HTTP client.
• Parse operation input parameters and generate a map of types for the message body.
• Integrate Wasabi 4.0 with Savon so people can easily test it as soon as possible.
• Add support for message headers defined in the WSDL.
• Finish initial documentation.
• Push to GitHub!
• Add support for attributes.
• Implement Response.header (for #544)
• Change the response Hash format to match the request Hash format.
• Convert Hash values to SOAP values (DateTime, etc) according to the type definition.
• Support WS-Policy/WS-Addressable (see Add "addressable" namespace + Action header support savon#409).
• Store the proper order of parameters so we can get rid of the :order! hack.
• Support for multipart responses using the new Savon::Multipart gem.
• Maybe support relative WSDL/Schema import locations? Can't find the specification for this.
• Switch from symbols to strings (for #485)

Please follow this issue for updates on Sekken.

[tsyber1an]

What does that mean 'Change the response Hash format to match the request Hash format.'?

Can you give some example, please? Maybe its interesting to implement ;)

[tjarratt]

That's a great question. Currently, the response from a SOAP operation will be the response of calling nori.parse(raw_xml_response_body). Conversely, the request hash is just a simple hash that represents the args that the operation needs. You might look at the old docs for an example of what this looks like.

If you poke around in the Gemfile you can find a TODO that says to get rid of Nori. I think that @rubiii was hoping to rewrite parts of Nori that Sekken needs, in order to simplify how responses are returned. In fact, if you look at the Savon3 docs for Responses, there's a note that the current format will change, and that the goal here is to make it easier to use "parts of a response ... for another request".

I think with that part in mind, the goal would be to make the response hash keys match the request hash keys as much as possible... although it's unclear to me (without digging in more) how that might work.

[rubiii]

not much time at the moment, but yes, i think @tjarratt summed it up nicely.
my goal for savon 3 was to get rid of nori/gyoku and find a common hash format for both
requests and responses so you can take parts from a response and use it with the next request.